Bug 76338

Summary: Can not boot the system when there is no drive in /dev/hda.
Product: [Retired] Red Hat Linux Reporter: Ivo Sarak <ivo>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0   
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: 2004-09-30 15:40:06 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 Ivo Sarak 2002-10-20 09:12:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
It is not possible to boot from partitions on /dev/hdX (X>a) when there is no
drive in /dev/hda.

Version-Release number of selected component (if applicable):
This problem has been on every RedHat Linux I ever tried.

How reproducible:
Always

Steps to Reproduce:
0.Install a drive to /dev/hda and install a RedHat Linux to it;
1.Move drive form /dev/hda to /dev/hdb;
2.Change the appropriate /etc/fstab, /boot/grub/grub.conf and /etc/lilo.conf
settings from /dev/hda to /dev/hdb;
3.Set the BIOS to boot from IDE1 or "other devices";
4.Try to boot the system;
	

Actual Results:  RedHat Linux is unable to start.

Expected Results:  System up and running as in case of drive being at /dev/hda.

Additional info:

Result is the same even if to try install RedHat Linux directly to /dev/hdb from
scratch.

Also, if to boot up the system from floppy and drive being at /dev/hdb, the df
will report the partitions as /dev/hda.

Comment 1 Bugzilla owner 2004-09-30 15:40:06 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/