Red Hat Bugzilla – Bug 126065
Dell PowerEdge 750 panic on mount root (sata)
Last modified: 2013-07-02 22:20:29 EDT
Description of problem:
Dell PowerEdge 750 fails to mount /, and panics during boot.
Version-Release number of selected component (if applicable):
does not occur with kernel-2.4.21-4.EL
tail of console log:
SCSI subsystem driver Revision: 1.00
ata_piix: combined mode detected
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xFEA0 irq 14
ata1: port disabled. ignoring.
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFEA8 irq 15
ata2: port disabled. ignoring.
scsi0 : ata_piix
scsi1 : ata_piix
Journalled Block Device driver loaded
VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
this system also triggers bug #125994
Created attachment 101153 [details]
full console log of 2.4.21-15.EL boot on Dell PowerEdge 750
panic at end of log.
Created attachment 101155 [details]
output from `lspci -v` under 2.4.21-4.EL
/me wonders if jgarzik should be the assignee for this bug.
bah... mayhap /me should learn to read everything prior to commenting!
Okay... just to be clear for all involved. RHEL3-U2 is required for
the class that the equipment in question is being built for. So... if
this means we have to take and respin a network install point with a
modded kernel so be it!
Whatever we're going to do we need to do it quickly as the class start
date of July 12 is rapidly approaching and with 40 uninstallable boxen
it's going to be tough to test anything or even conduct the class if
this bug is not fixed prior to the start date.
After some fussing around I took the patch that jgarzik gave me and
applied it to the U2 kernel. Built it and installed it to a vanilla
RHEL3 install on one of the new PE750's and it worked... network, SATA
all function just fine.
Since we cannot wait for U3 I am updating this box to U2 and then I
will respin a network install point on this box with the new kernel so
we can proceed with the project.
A fix for this problem has just been committed to the RHEL3 U3
patch pool this evening (in kernel version 2.4.21-15.16.EL).
Has anyone verified this fix?
what's the name of the patch?
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.