Bug 79896 - grubby --bootloader-probe fails to find lilo with software raid
grubby --bootloader-probe fails to find lilo with software raid
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd (Show other bugs)
8.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Erik Troan
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-17 16:31 EST by Philip Ross
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-14 17:19:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
My /etc/raidtab (891 bytes, text/plain)
2003-01-14 16:55 EST, Philip Ross
no flags Details

  None (edit)
Description Philip Ross 2002-12-17 16:31:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
Versions 21.4.3 and up of lilo have support for automatically working out where
to install the bootloader in RAID 1 setups. This allows you to set boot=/dev/mdX
(where mdX is the /boot partition) and have lilo automatically install the
bootloader to the boot sectors of the drives making up the RAID array. See
http://www.elliott-turbo.com/lilo/.

When lilo.conf includes the line boot=/dev/mdX, 'grubby --bootloader-probe' will
fail to return 'lilo' as expected since the bootloader has been installed to
/dev/hdX instead of /dev/mdX. If the lilo.conf file is changed so boot=/dev/hdX,
'grubby --bootloader-probe' works as expected (returning 'lilo').

This problem prevents kernel and other upgrades from reinstalling lilo when
required.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install Red Hat with a RAID 1 mirrored /boot partition.
2. Setup lilo using boot=/dev/mdX and install.
3. Run grubby --bootloader-probe which will not return anything.
4. Setup lilo using boot=/dev/hdX and reinstall.
5. Run grubby --bootloader-probe. This will now return 'lilo'.
    

Actual Results:  Step 3:

#grubby --bootloader-probe

<returns nothing>

Expected Results:  Step 3:

#grubby --bootloader-probe
lilo


Additional info:
Comment 1 Philip Ross 2002-12-17 17:23:35 EST
I've just done a little investigation into the source for grubby and the problem
is that bootSect is read from the first 512 bytes of /dev/mdX, whereas lilo
actually installs itself to the boot sectors of the drives making up /dev/mdX
(e.g. /dev/hda and /dev/hdb). When boot is set to /dev/hda in lilo.conf, grubby
works correctly as bootSect is read from the first 512 bytes of /dev/hda.
Comment 2 Erik Troan 2003-01-14 16:36:16 EST
do you have a correct /etc/raidtab sitting around?
Comment 3 Philip Ross 2003-01-14 16:55:05 EST
Created attachment 89363 [details]
My /etc/raidtab

I've attached my current /etc/raidtab. With this RAID 1 setup 'grubby
--bootloader-probe' fails.
Comment 4 Erik Troan 2003-01-14 17:19:33 EST
this should be fixed in mkinitrd > 3.4.43 -- want me to send you an rpm to test?
Comment 5 Philip Ross 2003-01-14 17:39:56 EST
Yes please.
Comment 6 Jeremy Katz 2003-01-14 17:48:32 EST
http://people.redhat.com/~katzj/mkinitrd/ has the newer package.
Comment 7 Philip Ross 2003-01-14 18:04:13 EST
Thanks. The new version returns the correct result on my RAID 1 setup using lilo.

Will this fix be made available as an errata package for Redhat 8.0?

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