Mon 11 Oct 2004 11:52:43 AM UTC, comment #5:
I may have a similar experience (using grub 0.95)
IDE1: master = Western Digital disk, slave = DVD-rom
IDE2: master = DVD-RW, slave = Maxtor ATA 80Mb
hda (=hd0) contains windows, hdd (=hd1) contains Linux (ext2)
when running grub from linux, I cannot detect any error
I can setup stage1 to the MBR of hd0, remaining files to (hd1,0)
If stage1.5 is on (hd1,0) I get Read-error from stage1
If stage1.5 is installed on (hd0,5), I get error 16 from stage 1.5
If stage2 is installed on (hd0,5), I get 'inconsistent file structure' when trying to read menu.lst
If menu.lst is moved to (hd0,5), I get 'inconsistent file structure' when trying to read the kernel (I do get the information about the kernel printed out though).
If the kernel is moved to (hd0,5), the system boots, and no problem can be detected with the disk.
My current wild guess is that for some reason while grub is running under linux, (hd1) refers to /dev/hdd (as reported by the kernel), but that when booting (hd1) refers to hdb (due to the unusual master/slave assignments?.
|
Thu 05 Sep 2002 03:00:00 AM UTC, comment #4:
I had a bug that I think is related to this. I am trying to use the oskit example kernels. In vmware I have (hd0) has my main linux install, with (hd1) being my testing drive because of the size of the images.
To setup grub initially it was easy...
root (hd1)
setup (hd1,0)
I copied my vmlinuz from (hd0,0)/boot to (hd1,0)/boot and it worked as
root (hd1,0)
kernel /boot/vmlinuz root=/dev/hda1
But when I tried the 'hello' example kernel:
kernel (hd1,0)/boot/hello
It would complain of afile not found. I was about to seek help on irc, when I decided just for the heck of it...
kernel (hd1,0)/boot/hello
and it worked.
So what I think is happening: For Linux it is finding the file on hd1 fine, but the others it is remapping it to hd0 instead of hd1.
I am using the newest cvs (Sept 4, 2002) and gcc 3.2 on rootlinux. Feel free to contact me -unavailable-
|
Tue 30 Jul 2002 01:45:48 PM UTC, comment #3:
I had a similar problem using grub to boot FreeBSD which was on the secondary IDE controller. After booting Linux, grub was able to see that HDD and even find the /boot/loader file, but grub was unable to find the drive during initial bootup.
The problem was a config issue in the BIOS; the first entry for the secondary IDE controller was set to NONE. After I changed it to "User HDD" and rebooted, grub was able to see the drive to boot FreeBSD.
|