Bug 50591 - Grub fail to boot(or install) when 2nd cciss controller used as a boot controller
Grub fail to boot(or install) when 2nd cciss controller used as a boot contro...
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
:
: 53585 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-01 09:37 EDT by Bryan Leopard
Modified: 2005-10-31 17:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-12 16:13:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bryan Leopard 2001-08-01 09:37:28 EDT
Grub fail to boot(or install) when 2nd cciss controller used as a boot 
controller.

System: DL380 G2 - I experienced the same problem on ML530.
Controller: SA5i(Embedded), SA532(Boot controller)

Steps to reproduce:
1. Configure SA532 as a boot controller
2. Begin installation
3. Select grub as a bootloader and choose to install to /dev/cciss/c1d0p1
4. Finish install
  - right after a postinstall, text console message shows following 
message.
   "/boot/grub/device.map:3:error:Bad device number"
5. Make rescue floppy and reboot - it will fail to boot 
6. Insert 1st CD again and try to reboot from it
7. Switch to console terminal at first GUI screen
8. Mount /dev/cciss/c1d0p2( / ) and /dev/cciss/c1d0p1(/boot).
9. chroot to /dev/cciss/c1d0p2
10. cd /boot/grub
11. "/sbin/grub-install /dev/cciss/c1d0p1" will generate following message.
  - " /dev/cciss/c1d0p1 does not have any corresponding BIOS drive"
12. "more device.map" in /boot/grub
  - (fd0)	/dev/fd0
    (hd2)    /dev/cciss/c1d0
13. Reboot the system again, and try to boot from rescue floppy.
14. Rescue boot also failed and generating;
  > mount : error 19 mounting ext3
  > pivot root : pivot_root(/sysroot,/sysroot/initrd) failed : 2
  > Freeing unused kernel memory: 232k freed
  > Kernel panic: No init found. Try passing int=option to kernel.
Comment 1 Glen Foster 2001-08-01 16:24:05 EDT
This defect is considered SHOULD-FIX for Fairfax.
Comment 2 Jeremy Katz 2001-08-08 02:20:08 EDT
Just out of curiosity, does LILO actually work in this configuration without any
tweaks to /etc/lilo.conf?  Also, what drives actually exist in the system?
Comment 3 Bryan Leopard 2001-08-09 10:32:08 EDT
"LILO works perfectly without any problem.
On SA532 controller, I have one RAID 5 logical volume configured which consist 
of 3 Compaq 18G ultra 3 scsi drives in the storage box."
Comment 4 Jeremy Katz 2001-08-09 23:55:34 EDT
And there are no other hard drives in the system other than the ones in the RAID
controller?  What does `/usr/sbin/kudzu -p -c HD` show?
Comment 5 Glen Foster 2001-08-23 17:47:53 EDT
This defect is *now* considered MUST-FIX for Fairfax.
Comment 6 prago 2001-08-27 09:59:29 EDT
Per Compaq:

And there are no other hard drives in the system other than the ones in the RAID
controller?  
Answer:
I have 2 Compaq RAID controllers in the system with following config:

SA5i - Embedded controller.  2 logical volumes configured
        /dev/cciss/c0d0
        /dev/cciss/c0d1

SA532 - BOOT CONTROLLER - 1 logical volume configured
        /dev/cciss/c1d0 
                /dev/cciss/c1d0p1 - /boot
                /dev/cciss/c1d0p2 - /
                /dev/cciss/c1d0p3 - swap
 
What does `/usr/sbin/kudzu -p -c HD` show?
There's nothing returned from executing the command.

Comment 7 Jeremy Katz 2001-09-04 10:51:38 EDT
I really don't know that there's a way to do this unless there's something
better exported to user space about BIOS ordering of drives.  Other
possibilities are having the driver order the drives correctly.

If lilo works with the stock configuration file generated with anaconda, could
you give the output of
/sbin/lilo -v -v -v
?
Comment 8 Jeremy Katz 2001-09-12 16:05:04 EDT
Didn't make it for Enigma.  For the next release, I'm looking at redoing the
boot loader screen with a way to give advanced information such as this.
Comment 9 Jeremy Katz 2001-10-12 16:13:52 EDT
*** Bug 53585 has been marked as a duplicate of this bug. ***
Comment 10 Jeremy Katz 2002-01-21 20:09:15 EST
You'll be able to manually change the detected drive order for Hampton

Note You need to log in before you can comment on or make changes to this bug.