qadri 0 Posted March 27, 2005 Hi, I would be very greatful if someone helps me out.I am having dual operating system i.e. Linux and Windows XP ,while trying to boot XP it is giving me rootnoverify(hd0,0) chainloader+1 n it is stopping there. if i boot linux there is no problem.I am very new to linux n donno wat to do,I was just reading the post in this forum. i have a file in my /boot/grub as grub.conf n it contains the following. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,5) # kernel /vmlinuz-version ro root=/dev/hda7 # initrd /initrd-version.img #boot=/dev/hda default=1 timeout=10 splashimage=(hd0,5)/grub/splash.xpm.gz password --md5 $1$34ddYNVG$/jyBxa/zvg08mOeCxowoA. title Red Hat Linux (2.4.20-8) root (hd0,5) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img title DOS rootnoverify (hd0,0) chainloader +1 n i donno wat to change in this. plz help me out.I would be very greatful . thanks. Share this post Link to post
iamroot 0 Posted March 28, 2005 Just enter this command at the terminal. sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda Had this problem a while ago when running a FC2, Win XP config. It's a GRUB problem. Share this post Link to post
qadri 0 Posted March 28, 2005 Originally posted by iamroot: Quote: Just enter this command at the terminal. sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda Had this problem a while ago when running a FC2, Win XP config. It's a GRUB problem. hi thanks for this but it didnt work .On giving this on the command line i am getting this. Disk /dev/hda: 4870 cylinders, 255 heads, 63 sectors/track Old situation: Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 * 0+ 1217 1218- 9783553+ 7 HPFS/NTFS /dev/hda2 1218 4869 3652 29334690 f Win95 Ext'd (LBA) /dev/hda3 0 - 0 0 0 Empty /dev/hda4 0 - 0 0 0 Empty /dev/hda5 1218+ 2435 1218- 9783553+ 7 HPFS/NTFS /dev/hda6 2436+ 2448 13- 104391 83 Linux /dev/hda7 2449+ 4837 2389- 19189611 83 Linux /dev/hda8 4838+ 4869 32- 257008+ 82 Linux swap New situation: Units = sectors of 512 bytes, counting from 0 Device Boot Start End #sectors Id System /dev/hda1 * 63 19567169 19567107 7 HPFS/NTFS /dev/hda2 19567170 78236549 58669380 f Win95 Ext'd (LBA) /dev/hda3 0 - 0 0 Empty /dev/hda4 0 - 0 0 Empty /dev/hda5 19567233 39134339 19567107 7 HPFS/NTFS /dev/hda6 39134403 39343184 208782 83 Linux /dev/hda7 39343248 77722469 38379222 83 Linux /dev/hda8 77722533 78236549 514017 82 Linux swap Successfully wrote the new partition table Re-reading the partition table ... BLKRRPART: Device or resource busy The command to re-read the partition table failed Reboot your system now, before using mkfs If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) when i reboot my system again n try to go XP it is giving me the samething i.e. rootnoverify(hd0,0) chainloader+1 i would be happy if anyone can get me out of this. thaks once again Share this post Link to post
danleff 0 Posted March 28, 2005 Originally posted by iamroot: Quote: Just enter this command at the terminal. sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda Had this problem a while ago when running a FC2, Win XP config. It's a GRUB problem. This fix is for Fedora Core 2 only. It does not apply to a ReHat 9 installation. See a full explanation at this article. It is also not a grub problem, but how the Fedora disk partitioner alters the geometry, an error using the 2.6 series kernel in Fedora Core 2 and the partitioning utility in Fedora. This is not the problem in RedHat. qadri, this is a RedHat 9 install? The unforunate thing is that sfdisk re-wrote the partition table. I have to think about this. While I do, perhaps someone may have the answer right off. Do you have the Windows install cd for this system? Did you make a boot floppy for RedHat during the install? If not, you have the RedHat install disks handy? What system/motherboard is this? And, this is an IDE drive, not a sata drive in the system? Let's try one thing first. Get into the bios and the section that has settings for the hard drive, see if detection is set to "auto" or "LBA." If set to "auto" change the setting to "LBA" and save the changes, then reboot. See if you can get into Windows and RedHat via grub. If this works, great! If not set the detection to "auto" again and save the changes, then reboot. Post back what you find. Share this post Link to post
iamroot 0 Posted March 28, 2005 Does this problem exist with RH9? Didnt know that. Share this post Link to post
danleff 0 Posted March 28, 2005 When distros started to be released with the 2.6 series of kernels, and the folks used the partitioning utility to set up their Linux install partitions in Fedora Core 1 or 2, or Mandrake 10.0, there was a flurry of activity about the problem. It seems to have been solved in Mandrake 10.1 and Fedora Core 3. If a user used PartitionMagic, or other partitioning utility to make their ext3 or reiserfs partiton ahead of time, there was no issue with the geometry problem. So, any previous distro, like RedHat 9 which used the 2.4 series kernel (pre 2.6 kernel) the geometry issue was not a problem. Share this post Link to post