Indeed I did - and that was the problem. Thanks - for others who may have rushed headlong into upgrading into devfs, what I did to fix it was to boot to a rescue disk, type "linux root=/dev/hda4" (insert your / partition there), and edit /etc/fstab to use the devfs style devices (e.g., /dev/discs/disc0/part4).
ap ---------------------------------------------------------------------- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu On Tue, 6 Jan 2004, Philip Stubbs wrote: > * Andrew Perrin ([EMAIL PROTECTED]) wrote: > > This morning I upgraded the kernel on my Sony Vaio PCG-Z505HS from 2.4.20 > > to 2.4.22. Everything went very smoothly, until I rebooted the machine -- > > at which point it seemed to begin fine, then tried the fsck on /dev/hda4 > > which holds / . fsck says "bad superblock" and drops into single-user > > mode with an instruction to fix the problem manually and reboot. Oddly > > enough, though, even fdisk /dev/hda says "Unable to open /dev/hda" -- so > > the block device itself isn't visible, even though that's the device that > > was booted from. > > > > My top candidate right now is that the driver for the disk (IDE, I > > assume) was accidentally left out of the new kernel, or was loaded as a > > model. Any other suggestions for what the problem might be are welcome. > > Finally, short of reloading the OS from scratch, any advice on how I might > > rescue it? > > Have you enabled Devfs in the new kernel? I did this, and I had to > reboot with an old kernel, and recompile, with devfs turned off. > > -- > ,''`. Philip Stubbs > : :' ; > `. `' > `- >
