[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: corrupt root fs



hiya,

On Mon, Nov 11, 2002 at 05:19:23PM -0800, madmac madmac wrote:
> I get timeouts from the Adaptec's SCSI adapters BIOS
> routine where it polls it's devices.

ack... well it could be faulty hardware, in which case i'd see
if i could try different disks on the same adaptor, and the same
disks on a different adaptor...

> Then it appears to boot until I get:
> 
> cramfs: wrong magic
> attempt to access beyond end of device
> 08:01: rw=0, wnat=2, limit=1
> EXT3-fs: unable to read superblock
> attempt to access beyond end of device
> 08:01: rw=0, wnat=2, limit=1
> EXT2-fs: unable to read superblock
> Kernel Panic: VFS: Unable to mount root fs on 08:01

this suggests to me your hardware is fine, because it found the kernel
image, which means it can read from the disk at least to a certain point.
if your hardware's fine, and if your kernel is configured to boot from
an initrd, maybe it's not finding the initrd?

when you boot up, before lilo loads your kernel try mashing
down shift to get a prompt, then hit tab to see if you have a
Linux.old or something like that.  iirc installing one kernel
package over another will do this for you automagically, in the 
case something goes wrong :)  if your hw is ok, then you should
be able to boot up into your old 2.2 system

> So I don't mind rebuilding from scratch if I have to. 
> Apt-get install is fun  

i couldn't even imagine the amount of time apt's saved me after mis-typed
calls to dd :)

> But is there a way (rescue floppy (I have a set) or
> the CD) to mount and fsck the / and /boot partitions? 
> I could also use a look at /etc/fstab just to refresh
> my memory (there were 8 partitions on that disk) of
> what went where.

yeah, rescue floppy/cd should do it, but try the above first.
either way, mount / and /boot (assuming you can get to them
from rescue or lilo prompt) into /target, edit /target/lilo.conf
to address the issue (maybe missing entry for initrd?), then run

# lilo -r /target

to fix your new kernel.  also, hopefully you'll be able to look at
fstab, and have access to fsck, mount, etc in the case of a boot floppy
without.  

hth, 
sean

Attachment: pgp6zxyg2qJPh.pgp
Description: PGP signature


Reply to: