[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: corrupted root partition
well, aparently it was just a bad super block.
e2fsck -b 8193
was suffice.
thanks,
remo
>> for reason i don't really know (i suspect it was because the FS was
>> full)
>> i can't access my root partition.
>> on boot i get a messae "Kernel panic, can't mount root partition" or smt
>> of that sort.
>> when booting to floppy (installation boot-root disks) i could mount
>> other partitions (/usr /home ) can be mounted ok, but root not. it gives
>> "wrong FS type or bad super block" message.
>>
>> so,
>> how can i deal with it (with means lesser than reinstalling the system)
>> ?
>> is there some handy precompiled (i can't compile this state either..)
>> linux-ndd ?
>>
>> thanks
>> remo
>>
>
>It is not because of its being full. You have a corrupted superblock.
>Probably virus (perhaps large virus hangover: L95 reinstall ?):
>
>Try to use the utility ext2fsck from the root/boot diskettes on the
>partition. This is a command like:
>
>e2fsck -cfpttv /dev/hd?? 2>&1 | more
>
>and be sure to give it the right root partition. If it says 'try another
>superblock', try again and give it -b 8193. Examine the generated listing
>from this command for hints about bad tracks and other clues.
>
>If even this does not help, run:
>
>mke2fs -S /dev/hd??
>
>and then, immediately afterwards, e2fsck as above. Be warned, that this is
>a last resort. After this, if it does not work, all you can do is
>reinstall the root partition.
>
>OTOH, how come you can boot the hdd ?! vmlinuz is on / and it can be read,
>else LILO can't find it ! Maybe you have added/changed partitions and the
>/ has moved in the list ?
>
>Peter
>
>
>
>