Bug 49299
Summary: | grub cannot see second disk | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Gene Czarcinski <gczarcinski> |
Component: | grub | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WORKSFORME | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-09-04 20:56:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gene Czarcinski
2001-07-17 18:55:06 UTC
This defect should be fixed before next release. This only occurs for me on one (Dell Optiplex) system. Is there any info that might help? What does the /boot/grub/device.map look like? 1. The /boot/grub/device.map on hda1 which I am trying to use as may master boot "director" has: (fd0) /dev/fd0 (hd0) /dev/hda I tried adding the line: (hd1) /dev/hdb but this had no effect. 2. I cannot use grub to chainloader boot from /dev/hdb1 (does not see the disk) nor can I use "grub on a floppy" to see /dev/hdb1. However, Once I boot up the minimal system on /dev/hda1, I can run grub and it will recognize (see) the ext2 file system on (hd1,0). 3. I have other systems with two ide drives and can use such a "master director" to boot linux partitions from with the hda or the hdb disks. Have you tried re-running `/sbin/grub-install /dev/hda` after adding the (hd1) /dev/hdb to /boot/grub/device.map? Sorry that followup took so long but I forgot about this one. I tried changing device.map and doing grub-install /dev/hda and it makes no difference. For some reason, grub on /dev/hda (or a floppy) do not like /dev/hdb. Whereas, running grub under a copy of roswell installed on hda can access /dev/hdb just fine. Well, in an installed system, the accessing of devices doesn't actually use the BIOS routines, so it's a bit different. Maybe try updating the BIOS? This still happens on RC1 and I have no idea how to get around it. This does NOT happen on any other system I have run tests on. Do you have the newest BIOS available installed on the machine? This box is a commercial Dell Optiplex purchased about too years ago plus an extra (IBM) 45MB ide drive. You have a good question but it will take me a few days (a week?) to check this out. I will also try another more or less identical box to see if it acts the same. Any information on updated BIOS ? Closing due to the lack of activity. |