>We have had an identical kernel panic message 4 times:
> Kernel panic: EXT2-fs panic (device 3/3): ext2_write_inode: unable
> to read i-node block - inode=57233, block=229424
> I am not sure if I can give you an adequate resolution to your problem.
> The error message means, in English: "I can not read a block on the hard
> Perhaps you have a problem with a currupted hard disk?
> In my personal experience with Linux, this particular message occurs when
> I have a hard disk with a bad partition table. In other words, if I mess
> with fdisk, and mess up the partition tabel, the next time I try to access
> the partition, the kernel panics.
I have encountered this problem on disks which fscked perfectly (at least
before the resulting crash :-). Once the system got a bit active, the
panic arose. We finally found that a SCSI hard drive had an internal
terminator, but that this fact had not been marked, so we had too much
termination on the bus. We suspected termination after reformatting the
drive did not make the problems go away. Get the SCSI Faq for the whole