fsck.ext3 exited with signal 11

pljvaldez · 06-13-2006, 01:30 PM

I think I just hosed my debian sarge laptop. I was fiddling around with iptables and forgot to flush them before I rebooted the machine. Well, to make a long story short, on reboot the machine is having problems with the root filesystem and fsck keeps exiting with signal 11.

It seems like fsck fails at the same inode 692228 each time. Does this imply that maybe my drive is failing and the iptables thing was just a coincidence? Should I just keep running fsck until I'm blue in the face? Try a reinstall? I tried running fsck off of a Knoppix CD and seem to be running into the same issues.

pljvaldez · 06-13-2006, 03:24 PM

Well, I've run fsck a bunch of times now and there's only 4 errors left, all on inode 692253:

Code:

i_file_acl for inode 692253 (...) is 774636129, should be zero.
Clear<y>? yes

i_faddr for inode 692253 (...) is 2151310708, should be zero.
Clear<y>? yes

i_frag for inode 692253 (...) is 16, should be zero.
Clear<y>? yes

i_fsize for inode 692253 (...) is 99, should be zero.
Clear<y>? yes

Segmentation fault

I've been reading up on debugfs, but I'm not very confident in running that command manually to reset these values. Any ideas???

pljvaldez · 06-13-2006, 06:29 PM

Well, I spent an hour manually clearing the inodes with debugfs with no end in site. It seems to be working, but it's not worth the time. So I'm just going to reinstall...