Bug 50309 – error displays wrong hd device

Bug 50309 - error displays wrong hd device

Summary:	error displays wrong hd device

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-07-30 06:14 EDT by Need Real Name
Modified:	2007-04-18 12:35 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-07-30 19:32:09 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2001-07-30 06:14:34 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 95; DigExt)

Description of problem:
In an upgrade from 7.0 to 7.1, I inadvertantly chose my / partition 
as /dev/hda5 when it is in fact /dev/hda6.  The error message told me it 
could not find a Red Hat installation on /dev/hdd5 instead of saying hdda5.

(I have gone back and selected the correct partition.  I do not need 
assistance, just wanted to report the bug.)

How reproducible:
Didn't try


Additional info:

Comment 1 Brent Fox 2001-07-30 11:15:32 EDT

Weird.  Is there even a /dev/hdd device in the machine?

Comment 2 Need Real Name 2001-07-30 19:32:05 EDT

No, but it just ocurred to me - hda5 used to be a root partition before a prior 
install.  At one point I chose new install instead of upgrade and saved my old 
partition.  Could it have read the etc/fstab from there which 
contains /dev/hdd5 as / (I had a drive on hdd while copying to my new harddrive 
a couple years ago).  If so, I guess the error makes sense.

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