Re: "Can't read superblock" booting 2.4.anything" **Fixed**
----- Original Message -----
From: "Colin Walters" <email@example.com>
Sent: Wednesday, July 11, 2001 4:35 PM
Subject: Re: "Can't read superblock" booting 2.4.anything"
> "John Andersen" <firstname.lastname@example.org> writes:
> > For some reason, any 2.4 kernel I try and boot (I've compiled two
> > from Benh's tree, and got 1 deb from walters and 1 deb from Jonas) I
> > get the same error:
> > it tells me it can't read the superblock, make sure I have a valid
> > etc and throughs me into single user mode. If I try and fsck it tells
> > the file or directory doesn't exist, yet I can mount it and see
> > e.g.:
> Duh! I should have realized this earlier. The problem is devfs,
> which both benh and I have enabled by default, and apparently Jonas
> does as well.
> You have three choices. Add 'devfs=nomount' to the append= options
> for these kernels, or rebuild without devfs support, or do 'apt-get
> install devfsd' (assuming you're running testing/sid).
Thanks Colin, 'apt-get install devfsd' did the trick. I feel stupid for not
seeing that before, of course. 20/20 hind sight.
Thanks to Colin, Peter, Chad and Ethan for their timely help in resolving