tucansam Posted November 14, 2022 Share Posted November 14, 2022 This is what I get when I try to mount a disk I need to get some info off of: -- Nov 13 18:34:09 ffs1 kernel: ata2: SATA max UDMA/133 abar m2048@0xf7d36000 port 0xf7d36180 irq 27 Nov 13 18:34:09 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:34:09 ffs1 kernel: ata2.00: NCQ Send/Recv Log not supported Nov 13 18:34:09 ffs1 kernel: ata2.00: ATA-9: ST3000VN000-1HJ166, W6A0TZ31, SC60, max UDMA/133 Nov 13 18:34:09 ffs1 kernel: ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Nov 13 18:34:09 ffs1 kernel: ata2.00: NCQ Send/Recv Log not supported Nov 13 18:34:09 ffs1 kernel: ata2.00: configured for UDMA/133 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] 4096-byte physical blocks Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Write Protect is off Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 13 18:34:09 ffs1 kernel: sdb: sdb1 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk Nov 13 18:34:38 ffs1 emhttpd: ST3000VN000-1HJ166_W6A0TZ31 (sdb) 512 5860533168 Nov 13 18:34:38 ffs1 emhttpd: read SMART /dev/sdb Nov 13 18:36:41 ffs1 unassigned.devices: Disk with ID 'ST3000VN000-1HJ166_W6A0TZ31 (sdb)' is not set to auto mount. Nov 13 18:36:50 ffs1 emhttpd: shcmd (154): /usr/sbin/cryptsetup luksOpen /dev/sdb1 W6A0TZ31 Nov 13 18:37:19 ffs1 kernel: ata2.00: READ LOG DMA EXT failed, trying PIO Nov 13 18:37:19 ffs1 kernel: ata2: failed to read log page 10h (errno=-5) Nov 13 18:37:19 ffs1 kernel: ata2.00: exception Emask 0x1 SAct 0xf SErr 0x0 action 0x0 Nov 13 18:37:19 ffs1 kernel: ata2.00: irq_stat 0x40000001 Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/02:00:41:80:00/00:00:00:00:00/40 tag 0 ncq dma 1024 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:08:48:80:00/00:00:00:00:00/40 tag 1 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:10:c0:40:51/00:00:22:00:00/40 tag 2 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:18:60:2a:6b/00:00:22:00:00/40 tag 3 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:19 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:19 ffs1 kernel: ata2: hard resetting link Nov 13 18:37:25 ffs1 kernel: ata2: link is slow to respond, please be patient (ready=0) Nov 13 18:37:27 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:37:27 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:27 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:32 ffs1 kernel: ata2: hard resetting link Nov 13 18:37:38 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:37:38 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:38 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:38 ffs1 kernel: ata2.00: disabled Nov 13 18:37:38 ffs1 kernel: ata2: EH complete Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#15 CDB: opcode=0x8a 8a 00 00 00 00 00 22 6b 2a 60 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 577448544 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#16 CDB: opcode=0x8a 8a 00 00 00 00 00 22 51 40 c0 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 575750336 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#17 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 80 48 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 32840 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#18 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 80 41 00 00 00 02 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 32833 op 0x1:(WRITE) flags 0x1000 phys_seg 2 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#19 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#20 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#21 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#22 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#23 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 50 00 00 00 08 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 80 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#24 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 50 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 80 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 18, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 19, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 20, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 21, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 22, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 23, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read -- syslog shows this at the end of the attempt: -- Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 20, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 21, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 22, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 23, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read Nov 13 18:37:38 ffs1 unassigned.devices: Mount of 'W6A0TZ31' failed: 'mount: /mnt/disks/W6A0TZ31: can't read superblock on /dev/mapper/W6A0TZ31. ' Nov 13 18:37:38 ffs1 unassigned.devices: Partition 'W6A0TZ31' cannot be mounted. -- I've read about ddrescue, but am uncertain how to proceed. This is a member disk out of an encrypted btrfs array. Can ddrescue still be used to make an attempt at recovery? Thanks. Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 Disk dropped offline, it it keeps doing that ddrescue also won't work, but you can try, and yes it works with any filesystem, encrypted or not. Quote Link to comment
tucansam Posted November 14, 2022 Author Share Posted November 14, 2022 Thank you Jorge. I realize this is purely speculative, but would it be worth a try to buy an exact same disk and use the logic board from it on the old disk, to see if that keeps it up long enough to recover data? ddrescue has run all night and is showing that its about 75% complete, and it claims it has recovered some data. I guess we'll see when it finishes. A four-hour ETA for finishing turned into almost 12, and it still not done. Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 28 minutes ago, tucansam said: I realize this is purely speculative, but would it be worth a try to buy an exact same disk and use the logic board from it on the old disk, to see if that keeps it up long enough to recover data? You can just by the board, usually also need to swap a chip from the old one. Quote Link to comment
tucansam Posted November 14, 2022 Author Share Posted November 14, 2022 First I'd be trying anything like this. Any chance there are guides online? Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 For example: https://www.datarecoveryunion.com/hard-drive-rom-chip-swapreplacement/ Quote Link to comment
tucansam Posted November 14, 2022 Author Share Posted November 14, 2022 ddrescue worked! I was able to decrypt, and then mount, the resulting image file. looks like more than 99% of my data is in tact. Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 In my experience it often can recover 99.99% Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.