Re: e2fsck trashed system; chroot now failing
hi ya
On Fri, 8 Aug 2003, nori heikkinen wrote:
> i booted up my laptop to check my email this evening, and e2fsck
> declares it's been 22 mounts or more and starts chugging away. it
> dies, so i knoppix-boot and manually e2fsck -y the thing so i don't
> have to sit there and babysit it. it finishes, so i reboot and take
> the knoppix CD out.
i'v always claimed, "e2fsck -y" is very very very bad ...
as you dont know what its gonna fix or try to fix or what it fixed
-- if i see toomany sequential blocks being fixed, i abort
and let it boot normally ... a few times and let the os
reboots attempt to fix itself ....
- am also wondering if the partition was mounted when you told it to
run e2fsck manually ...
e2fsck should abort unconditionally or at least read but NOT
fix anything on mounted fs
- before running e2fsck ..
- make sure your backups works
- make sure you have another compatible boot media
( maybe knoppix didnt fix it the way it should have
( based on your partitions ?? ( just guessing
manually fixing inodes is too much of pain ... best to reinstall
and restore from backups and do not run "e2fsck -y" again from
an incompatible/untested media
c ya
alvin
> but it kernel-panics -- "no init found." so i knoppix back in, mount
> my root partition, and lo an behold, my system's trashed. instead of
> bin/ dev/ etc/ et cetera, i see lines upon lines of:
>
> #1030177 #163 #196286 #210 #354 #376679 #387 #886
> #1046529 #164 #196287 #212577 #355 #376680 #388 #887
> #1062892 #165 #196288 #212578 #356 #376681 #389 #888
> #107 #166 #196292 #212588 #357 #376682 #390 #889
> #108 #1667909 #196294 #224 #358 #376683 #391 #890
> ...
>
Reply to: