rogerh Posted November 15, 2008 Author Report Share Posted November 15, 2008 Here is the listing.... Disk /dev/hda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x7bac7bac Device Boot Start End Blocks Id System /dev/hda1 * 1 764 6136798+ 83 Linux /dev/hda2 765 19457 150151522+ 5 Extended /dev/hda5 765 904 1124518+ 82 Linux swap / Solaris /dev/hda6 905 19457 149026941 83 Linux Disk /dev/hdb: 10.2 GB, 10262568960 bytes 255 heads, 63 sectors/track, 1247 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xa83953aa Device Boot Start End Blocks Id System /dev/hdb1 * 1 1246 10008463+ 7 HPFS/NTFS Disk /dev/sda: 256 MB, 256901120 bytes 16 heads, 32 sectors/track, 980 cylinders Units = cylinders of 512 * 512 = 262144 bytes Disk identifier: 0x4e2e1869 Device Boot Start End Blocks Id System /dev/sda1 * 1 980 250864 e W95 FAT16 (LBA) Hopefully this points out what is wrong. My preference would be to keep my windows drive as is, since when my linux disk crashed last month I did have access to a backup (yup, probably would be ok even if grub was on the front end.....). Thanks for the persistent help!! Regards -- Roger Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 15, 2008 Report Share Posted November 15, 2008 OK, so you can see both your disks no problem. I think your grub config is in the wrong order though for Windows. Put it like this: map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd0,0) makeactive chainloader +1 and see if it boots now. Quote Link to comment Share on other sites More sharing options...
rogerh Posted November 15, 2008 Author Report Share Posted November 15, 2008 Hello, Made that change, and now on boot I get 'Error 13 : invalid or unsupported executable format' This is the relevant chunk of script in menu.lst title windows map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd0,0) makeactive chainloader +1 Regards -- Roger Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 15, 2008 Report Share Posted November 15, 2008 OK, try changing the rootnoverify line like this, and see what happens: rootnoverify (hd1,0) and try again. Quote Link to comment Share on other sites More sharing options...
rogerh Posted November 15, 2008 Author Report Share Posted November 15, 2008 Hello, Now I get an 'Error 21 : selected disk does not exist' What should I change now?? This seems to be a bit of an elusive guy!! Thanks for your persistence.... Regards -- Roger Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 16, 2008 Report Share Posted November 16, 2008 I'm unsure, when I googled all that stuff, I got the suggestions I made and unfortunately, it didn't seem to work as it did for all the others who asked the same question for the error posted. Quote Link to comment Share on other sites More sharing options...
rogerh Posted November 17, 2008 Author Report Share Posted November 17, 2008 I was wondering if there is a difference between the hd0 / hd1 and hda / hdb designation?? The disk listing I pasted above uses the hda/hdb designations, while the grub commands use hd0 and hd1. Not sure if that makes any difference?? Any other resources I can poke at to try and get this resolved?? I have started to look at the on-line grub documentation, but I think it may be beyond me at the moment.. Regards -- Roger Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.