This mail is an automated notification from the bugs tracker
of the project: GNU GRUB.
/**************************************************************************/
[bugs #722] Latest Modifications:
Changes by: Anonymous user
Date:
Mon 10/11/2004 at 07:52
------------------ Additional Follow-up Comments ----------------------------
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?.
/**************************************************************************/
[bugs #722] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=722>
Project: GNU GRUB
Submitted by: Damien Burns
On: Thu 06/20/2002 at 19:44
Category: Disk & Partition
Severity: Major
Priority: 5 - Normal
Item Group: Non-software Error
Resolution: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Status: Open
Release:
Reproducibility: Every Time
Planned Release:
Summary: Can not find second hard drive on PCI IDE Controller
Original Submission: Bizare error here, installed red hat 7.2 on a secondary hard
disk, windows 98 is on the first drive. Both drives are attached to a Maxtor ATA100
PCI IDE controller, on the primary channel. Grub will boot but would not be able to
find the secondary drive, error 21. Could however boot into linux with disk, then
running grub from the terminal I could see the windows drive as (hd0,0) and linux as
(hd1,0) in linux they are hde1 & hdf1 respectively. I moved the grub folder to the
windows drive c:bootgrub and then loaded grub in the MBR to load from there, worked
fine, can boot windows, but when booting linux it says can not find drive. Have tried
root(hdx) up to unfesable numbers, seems its not even showing up. I can move the
drives to the primary onboard and this problem is resolved... however it is a serious
down grade in speed. I have seen no documentation so far on this type of problem, have
I just stumbled upon another sucky IDE controller?
Also for info the drives are both Maxtor's, one 40 GB, one 30 GB, both ATA100s. The
card is labeled Maxtor but has a Promise chipset!
Follow-up Comments
------------------
-------------------------------------------------------
Date: Mon 10/11/2004 at 07:52 By: 0 <None>
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?.
-------------------------------------------------------
Date: Wed 09/04/2002 at 23:00 By: Jeffrey Drake <jdrake>
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 [EMAIL PROTECTED]
-------------------------------------------------------
Date: Tue 07/30/2002 at 09:45 By: 0 <None>
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.
-------------------------------------------------------
Date: Tue 06/25/2002 at 09:47 By: 0 <None>
That is what the device.map shows.
-------------------------------------------------------
Date: Tue 06/25/2002 at 09:46 By: 0 <None>
That is what the device.map shows.
-------------------------------------------------------
Date: Thu 06/20/2002 at 20:13 By: Jeremy Katz <katzj>
What are the contents of your /boot/grub/device.map file? It should look something
like
(fd0) /dev/fd0
(hd0) /dev/hde
(hd1) /dev/hdf
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=722>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-grub
