Help request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have what to my suprise appears to be an uncommon situation and must humbly ask assistance. I say uncommon because it's not covered by the faq and web search hasn't turned up any results. The issue is I have an ext4 partition on a LUKS encrypted drive and the computer it's mounted on restarted without cleanly unmounting and closing the drive. Now if I try to mount the drive bash hangs for several minutes and then claims that it's not a valid LUKS device. Pulling dmesg shows a number of I/O errors. Here's a sample:

[  643.631782] print_req_error: critical target error, dev sdi, sector 11721044993
[  643.631789] Buffer I/O error on dev sdi, logical block 11721044993, async page read
[  649.107468] sd 8:0:0:0: [sdi] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  649.107473] sd 8:0:0:0: [sdi] tag#24 Sense Key : Hardware Error [current]
[  649.107479] sd 8:0:0:0: [sdi] tag#24 ASC=0x44 <<vendor>>ASCQ=0x81
[  649.107484] sd 8:0:0:0: [sdi] tag#24 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 02 00 00 00 01 00 00
[  649.107487] print_req_error: critical target error, dev sdi, sector 11721044994
[  649.107496] Buffer I/O error on dev sdi, logical block 11721044994, async page read
[  654.583148] sd 8:0:0:0: [sdi] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  654.583152] sd 8:0:0:0: [sdi] tag#25 Sense Key : Hardware Error [current]
[  654.583157] sd 8:0:0:0: [sdi] tag#25 ASC=0x44 <<vendor>>ASCQ=0x81
[  654.583160] sd 8:0:0:0: [sdi] tag#25 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 03 00 00 00 01 00 00
[  654.583163] print_req_error: critical target error, dev sdi, sector 11721044995
[  654.586033] Buffer I/O error on dev sdi, logical block 11721044995, async page read
[  660.058859] sd 8:0:0:0: [sdi] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  660.058863] sd 8:0:0:0: [sdi] tag#26 Sense Key : Hardware Error [current]
[  660.058869] sd 8:0:0:0: [sdi] tag#26 ASC=0x44 <<vendor>>ASCQ=0x81
[  660.058874] sd 8:0:0:0: [sdi] tag#26 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 04 00 00 00 01 00 00
[  660.058877] print_req_error: critical target error, dev sdi, sector 11721044996
[  660.062377] Buffer I/O error on dev sdi, logical block 11721044996, async page read
[  662.783221] sd 8:0:0:0: [sdi] tag#28 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
[  662.783227] sd 8:0:0:0: [sdi] tag#28 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 06 00 00 00 01 00 00
[  662.783327] sd 8:0:0:0: [sdi] tag#27 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
[  662.783332] sd 8:0:0:0: [sdi] tag#27 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 05 00 00 00 01 00 00
[  662.783428] sd 8:0:0:0: [sdi] tag#0 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN
[  662.783434] sd 8:0:0:0: [sdi] tag#0 CDB: Read(16) 88 00 00 00 00 02 ba a0 f4 07 00 00 00 01 00 00

I don't think it's a drive failure because it's only a few months old and I haven't got any SMART warnings, so that leaves software. Is it worth making any attempt at trying to recover the drive and if so is there any documentation that explains what to do? I don't have a backup of the LUKS header, if that's the problem.
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
https://www.saout.de/mailman/listinfo/dm-crypt

[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux