Bug 216367

Summary:	Update to RHEL 4.4 breaks lilo-21 for Linux software RAID
Product:	Red Hat Enterprise Linux 4	Reporter:	Dave Miller <dave>
Component:	lilo	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4
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:	2012-06-20 16:17:22 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 Dave Miller 2006-11-20 00:04:39 UTC

Description of problem: Upgrade to RHWEL 4.4 breaks lilo-21.  Attempting to run
lilo after the upgrade results in:

"/dev/dis: no such device"

on systems using Linux software RAID.

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

lilo-21.4.4-26.1 with RHEL 4.4

How reproducible:

100%

Steps to Reproduce:
1. Upgarde via yum t RHEL 4.4
2. Attempt to run lilo to pick up a new kernel.
  
Actual results:

See problem description

Expected results:

lilo runs with no problems.

Additional info:

This appears to be fixed as of lilo-22.  There is some conversion of lilo.conf
required.  There are several ways this can be accomplished but the easiest is
probably to include the following line:

raid-extra-boot=/dev/hde,/dev/hdg

in the common section of lilo.conf.  In this case, the "boot drive" consists of
the mirror pair /dev/hde and /dev/hdg.

Comment 1 Jiri Pallich 2012-06-20 16:17:22 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.