begin quote On Sun, 14 Sep 2003 14:03:45 +0400 Dmitry Suzdalev <[EMAIL PROTECTED]> wrote:
> > * Filesystem couldn't be fixed [!!] > <SNIP> > Upon the next reboot, all goes okay, e2fsck says that FS is clean. > Same result > if I issue "e2fsck /dev/hda4" command manually. > How can I catch this nasty error now? <SNIP> > Anyone had something like this? Yep, I had a case of bad RAM that caused strange segfaults and errors (attempt to read past end of device style errors ) which forced me to do some scrunity on all hardware. As I use encrypted disks the livecd's won't do it (normally thats a great recovery though) so instead i choose to edit the bootcommand in grub and add: init=/bin/sash this will give you a ReadOnly mounted / , and nothing started. at this time do fsck -f /dev/hda3 (assuming hda3 is your root partition) And wait. wait wait and wait ;) Then, go through each partition in turn and fsck them (fsck is a wrapper that does automatic fs determination before calling fsck.ext3 fsck.jfs or others) //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end
pgp00000.pgp
Description: PGP signature
