severity 496956 normal
thanks
Sounds like your kernel is crashing when a certain part of the disk is
being accessed. If a userspace program can cause a system crash, by
definition that's a kernel bug, not a userspace bug. The fact that
the system is crashing on you any way if you abort e2fsck with ctrl-c,
drop into maintenance mode, and then type ctrl-d to continue rebooting
without checking the filesystem shows this isn't an e2fsprogs problem.
If it's not crashing when you boot a Knoppix CD, yes, it could be
because you're using a much older version of e2fsprogs --- but
remember, the Knoppix CD is also using a significantly older kernel,
too.
I don't know if this is caused by some kind of hardware fault which
the kernel isn't handling properly, or this is a kernel bug which was
introduced when you upgraded to a newer kernel, but that is what I
would suspect.
1) What kernel version are you running?
2) What kind of disk drive are you using for your filesystem? What kind
of disk controller are you using? Is it SCSI, IDE, SATA, etc.?
3) What happens if you run this command from maintenance mode:
dd if=/dev/hda5 of=/dev/null bs=32k
> In case 3), e2fsck start showing triplets of data
> (using -C 1 option) starting from 1 1 734 and it always reboots shortly
> after the triplet 1 64 734 as showed below:
The fact that it always reboots around the time when e2fsck is
checking block group #64 (out of the 734 block groups on that
filesystem) strongly suggests some kind of hardware fault. The
hardware is returning some kind of error, which the kernel can't
handle and it is causing it to panic and reboot.
That's why I suggested the dd command above; it would demontrate the
problem without any use of e2fsprogs.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
