135 GB ext3 on broken drive -- other possibilities than "e2fsck -y"?
lists at mjh.name
Sat Jan 8 15:51:41 UTC 2005
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, 08 Jan 2005 02:45:27 +0100
Christian <evilninja at gmx.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Milan Holzäpfel schrieb:
> >>>And after my second fsck attempt, every further fsck does this:
> >>>| linux root # fsck.ext3 /dev/hdc8 -y
> >>>| e2fsck 1.35 (28-Feb-2004)
> >>>| /dev/hdc8 contains a file system with errors, check forced.
> >>>| Pass 1: Checking inodes, blocks, and sizes
> so, you did "fsck -y" and after this the fs still had unfixable errors?
> is there anything useful in the kernel logs, maybe hardware errors? (disk,
> cables, controller, memory, power)
IIRC yes. These fscks were run on a drive which seems to be still ok,
and I think that there was nothing in the kernel logs about this drive
or anything else which would be unusual, but I'm not completely sure. I
guess I'll check one more time.
thanks for your answer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Ext3-users