Ext3 users - Aug 2004 - e2fsck hangs while recovering journal

Hi,

It seems one of my computers died last night and it looks like hard disk
trouble. I took the disk out and attached to another system and tried to
mount the partition, but the mount doesn't complete and just hangs
(process is also unkillable - I had to reboot).

So, I tried to run "fsck -fccp /dev/sda2" but the command just hangs
after printing "/dev/sda2: recovering journal". Now I'm pretty
sure this
is because there's bad blocks on the disk, as dmesg shows some disk
errors (see attached file). Google tells me status 0x59 means a bad
block.

I tried to remove the journal to see if the fsck could get any further
by using "tune2fs -f -O^has_journal /dev/sda2", but it just told me to
recover the journal first (despite using -f).

Anyway, I'm kind of stuck. Can anyone give me any clues as to how I can
get this filesystem mounted for long enough to try and recover some
data?

Thanks,
Kevin.

-------------- next part --------------
scsi1: ERROR on channel 0, id 0, lun 0, CDB: 0x28 00 00 03 2a 3c 00 00 08 00 
Current sda: sense = 70  3
ASC=11 ASCQ= 4
Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x11
0x04
end_request: I/O error, dev sda, sector 207420
scsi1: ERROR on channel 0, id 0, lun 0, CDB: 0x28 00 00 03 2a 3d 00 00 07 00 
Current sda: sense = 70  3
ASC=11 ASCQ= 4
Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x11
0x04
end_request: I/O error, dev sda, sector 207421
Buffer I/O error on device sda2, logical block 7320
ata2: DMA timeout, stat 0x1
ATA: abnormal status 0x59 on port 0xB807
scsi1: ERROR on channel 0, id 0, lun 0, CDB: 0x28 00 00 03 2a 3e 00 00 06 00 
Current sda: sense = 70  3
ASC=11 ASCQ= 4
Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x11
0x04
end_request: I/O error, dev sda, sector 207422
ATA: abnormal status 0x59 on port 0xB807
ATA: abnormal status 0x59 on port 0xB807
ATA: abnormal status 0x59 on port 0xB807

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Shanahan wrote:
> Anyway, I'm kind of stuck. Can anyone give me any clues as to how I can
> get this filesystem mounted for long enough to try and recover some
> data?
as always: try to bypass the fs first and get the data to working disk.
"dd" or even better "dd_rescue" seem to be the tools of
choice here.
then, after copying the data to file, you can try "fsck" on this file
and see, what it gives. this way you don't have to deal with hardware
errors while recovering.

Christian.
- --
BOFH excuse #449:

greenpeace free'd the mallocs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBH0C+C/PVm5+NVoYRAu42AJ9dG2SqqgOKFiho164f9Y6BZ//eQQCfYb7R
aQr+izRGzz57yiY6w5x9IqI=4vYE
-----END PGP SIGNATURE-----