Bug 9059 – Selecting 'rescue' at image: prompt for CDROM causes VFS hang

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 9059 - Selecting 'rescue' at image: prompt for CDROM causes VFS hang

Summary:	Selecting 'rescue' at image: prompt for CDROM causes VFS hang

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-02-01 23:51 EST by Chris Cogdon
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-03 11:23:41 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Cogdon 2000-02-01 23:56:59 EST

(okay... lets actually add some comments, now ;)

I boot from CDROM and type 'rescue' at the prompt. The kernel boots
successfully, but hangs with the following errors:

VFS: Cannot open root device 08:32
Kernel panic: VFS: Unable to mount root fs on 08:32

I know that 08:32 is /dev/sdc. I have a aic7xxx-style controller installed but
the ROM writer at /dev/sdc is turned /off/.

However... if I use 'linux resuce' instead of 'rescue' it boots okay. (Apart
from the fact that the rescue facilities presented are very poor... perhaps if
'rescue' worked properly then there wouldnt be a problem ??)

Comment 1 Michael Fulbright 2000-02-03 11:23:59 EST

The rescue image is an important area we are currently examining...

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