Robert P. J. Day 写道:
(NOTE: please ignore my earlier and utterly misinformed plea for
help. turns out that, in attempting to mount /dev/sda1 as the alleged
root filesystem, the new 2.6 kernel was finding the external backup
hard drive at /dev/sda1. no surprise that that wasn't bootable.
ack.)
so now i'm getting what appears to be another common diagnostic as
seen in the subject line. i can see that a common reason is the
remapping of device names from hda -> sda. however, even under the
old 2.4 kernel on this upgraded etch system, the devices were accessed
via sda (megaraid raid controller). so the advice to rename from hda
to sda isn't relevant. (but is there something else about the
megaraid controller that might be relevant? i've opened up the
relevant initrd image and it does in fact contain megaraid modules.)
thoughts? the last few lines of boot diagnostics are:
Done.
Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system ...
then ... hang. it's pretty clearly a problem in just
seeing/accessing the sole hard drive in the system. i just can't see
what it is.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
How about dig into your system with a live CD to see the device mapping
in your system?
And by the way, have you ever upgraded a sarge system with 2.4 kernel to
a 2.6 lenny system?
Will changing from hda to sda be sufficient?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
