Re: "Waiting for root file system" problem

[This message has also been posted to linux.debian.user.]
This is becoming a FAQ. There is a problem with udev.
Before udev, there was a strong association between
device names and devices. With udev, that association
is much weaker.
There's new randomness in how partitions are named
during boot.
Debian and other installers have not
yet worked around this relatively new problem.

What you're seeing is an effect of that.
The udeb installer kernel got a different set of
device names than the installed kernel did, and the
root file system never appears where the installed
kernel has been told it would.

The workaround is to use file system labels or UUIDs
not device names in /etc/fstab and /boot/grub/menu.lst.
But the Debian 4.0 installer doesn't know that.

Please read the discussion at
http://www.debianhelp.org/node/11653


In article <9H9Ej-5g8-29@xxxxxxxxxxxxxxxx>, dave N wrote:

I've installed Etch r1 and the only real thing I've done to the
system is updated the system, though during the update it updated the
kernel to the same kernel that was installed during the installation
(used the medium to try and get more control over Grub install).


During boot the system appears to find all the drives OK when I am
reading as fast as I can, but then I get the following (from a photo of
the screen messages)

Begin: Mounting root file system... ...
Begin: running /scripts/local-top ...
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
ide1: I/O resource 0x170-0x177 not free.
ide1: ports already in use, skipping probe
Done.
Begin: Waiting for root file system... ...

And it stops right there. 0's above may be 8's, can't tell from the picture.

I booted with Knoppix live and there is nothing in /var/log/messages,
none of the logs appear to have changed since I last booted 2 days ago.
I have not run fsck or anything else on this yet.

Apparently Knoppix doesn't use udev.


Cameron


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Hardware hassles: Linux vs. Windows
    ... > Alvin Oga wrote: ... > up to the quality of the distro's installer. ... > the udev rules manually to assign it a filename that's based on the ... All of which are, guess what, based on Debian. ...
    (Debian-User)
  • Re: "Waiting for root file system" problem
    ... There is a problem with udev. ... during boot. ... but when booted Debian showed me the partition as /dev/sdc5! ... But the Debian 4.0 installer doesn't know that. ...
    (Debian-User)
  • Re: Anyone have the Nvidia driver working in 2.6.11-1.14_FC3?
    ... >>I have the current udev installed so it should be ok, ... >Since you previously had the nVidia driver working, ... Can you run X with the nVidia driver right after ... >using the nVidia installer? ...
    (Fedora)
  • Re: [GIT PATCH] Remove devfs from 2.6.13
    ... >> their installer floppies and such migrated to udev. ... > ndevfs is not devfs compatible in any way, ... The debian installer has devfs paths coded into it, ok, sure. ...
    (Linux-Kernel)
  • Re: gcc updates
    ... This breaks all of the C code I have written for the final phases of the processing chain. ... I assume a similar scheme would allow me to upgrade from F8 to F9. ... It then downloads the anaconda installer, and places an entry in grub that allows selection of an upgrade fedora item. ... This work is quite disk and processor intensive, yet I never saw any kernel or other issues during about two months, and in trimming 100GB of mpeg data. ...
    (Fedora)