Hard drive dying !? Help to rescue data

MrNice · February 13, 2024, 12:44pm

Hello there,
Bad time, my HD is bad. This is a internat HD connected to a switch. Now when I start it, it mount fine then after half a minute it remount as read only.
dmesg says

[    5.771779] usb 1-7.2: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
[    5.771783] usb 1-7.2: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/4096/1
[    5.879961] usbcore: registered new interface driver snd-usb-audio
[    5.915826] bpfilter: Loaded bpfilter_umh pid 1121
[    5.916017] Started bpfilter
[    5.976475] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[    6.178336] r8169 0000:03:00.0 eth0: Link is Down
[    6.656249] Bluetooth: hci0: RTL: fw version 0x75b8f098
[    6.805302] Bluetooth: MGMT ver 1.22
[    6.810334] NET: Registered PF_ALG protocol family
[    8.393862] Bluetooth: RFCOMM TTY layer initialized
[    8.393869] Bluetooth: RFCOMM socket layer initialized
[    8.393874] Bluetooth: RFCOMM ver 1.11
[    9.102833] r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[    9.102855] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    9.139518] NET: Registered PF_PACKET protocol family
[    9.539804] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[   32.375895] EXT4-fs warning (device sda): ext4_clear_journal_err:5759: Filesystem error recorded from previous mount: IO failure
[   32.375904] EXT4-fs warning (device sda): ext4_clear_journal_err:5760: Marking fs in need of filesystem check.
[   32.414036] EXT4-fs (sda): warning: mounting fs with errors, running e2fsck is recommended
[   32.454432] EXT4-fs (sda): recovery complete
[   32.475807] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[   49.339027] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x0
[   49.339047] ata5.00: irq_stat 0x40000008
[   49.339059] ata5.00: failed command: READ FPDMA QUEUED
[   49.339069] ata5.00: cmd 60/08:78:e0:01:40/00:00:58:01:00/40 tag 15 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[   49.339097] ata5.00: status: { DRDY ERR }
[   49.339106] ata5.00: error: { UNC }
[   49.340180] ata5.00: configured for UDMA/133
[   49.340199] sd 4:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[   49.340206] sd 4:0:0:0: [sda] tag#15 Sense Key : Medium Error [current] 
[   49.340212] sd 4:0:0:0: [sda] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
[   49.340218] sd 4:0:0:0: [sda] tag#15 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[   49.340221] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[   49.340253] ata5: EH complete
[   49.340251] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[   49.340277] Aborting journal on device sda-8.
[   49.556688] EXT4-fs (sda): Remounting filesystem read-only
[   74.220174] ata5.00: exception Emask 0x0 SAct 0x3000 SErr 0x0 action 0x0
[   74.220194] ata5.00: irq_stat 0x40000008
[   74.220206] ata5.00: failed command: READ FPDMA QUEUED
[   74.220215] ata5.00: cmd 60/00:60:00:c8:8d/04:00:c3:00:00/40 tag 12 ncq dma 524288 in
                        res 41/40:00:40:c8:8d/00:00:c3:00:00/40 Emask 0x409 (media error) <F>
[   74.220244] ata5.00: status: { DRDY ERR }
[   74.220253] ata5.00: error: { UNC }
[   74.221317] ata5.00: configured for UDMA/133
[   74.221336] sd 4:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=8s
[   74.221343] sd 4:0:0:0: [sda] tag#12 Sense Key : Medium Error [current] 
[   74.221348] sd 4:0:0:0: [sda] tag#12 Add. Sense: Unrecovered read error - auto reallocate failed
[   74.221354] sd 4:0:0:0: [sda] tag#12 CDB: Read(16) 88 00 00 00 00 00 c3 8d c8 00 00 00 04 00 00 00
[   74.221358] I/O error, dev sda, sector 3280848960 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0
[   74.221405] ata5: EH complete
[   82.134141] ata5.00: exception Emask 0x0 SAct 0x44000 SErr 0x0 action 0x0
[   82.134160] ata5.00: irq_stat 0x40000008
[   82.134172] ata5.00: failed command: READ FPDMA QUEUED
[   82.134181] ata5.00: cmd 60/00:90:00:cc:8d/08:00:c3:00:00/40 tag 18 ncq dma 1048576 in
                        res 41/40:00:97:d2:8d/00:00:c3:00:00/40 Emask 0x409 (media error) <F>
[   82.134212] ata5.00: status: { DRDY ERR }
[   82.134222] ata5.00: error: { UNC }
[   82.135280] ata5.00: configured for UDMA/133
[   82.135318] sd 4:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=15s
[   82.135326] sd 4:0:0:0: [sda] tag#18 Sense Key : Medium Error [current] 
[   82.135331] sd 4:0:0:0: [sda] tag#18 Add. Sense: Unrecovered read error - auto reallocate failed
[   82.135337] sd 4:0:0:0: [sda] tag#18 CDB: Read(16) 88 00 00 00 00 00 c3 8d cc 00 00 00 08 00 00 00
[   82.135341] I/O error, dev sda, sector 3280851607 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[   82.135378] ata5: EH complete
[  133.544132] ata5.00: exception Emask 0x0 SAct 0x180 SErr 0x0 action 0x0
[  133.544155] ata5.00: irq_stat 0x40000008
[  133.544168] ata5.00: failed command: READ FPDMA QUEUED
[  133.544179] ata5.00: cmd 60/00:38:00:dc:8d/08:00:c3:00:00/40 tag 7 ncq dma 1048576 in
                        res 41/40:00:f7:dc:8d/00:00:c3:00:00/40 Emask 0x409 (media error) <F>
[  133.544209] ata5.00: status: { DRDY ERR }
[  133.544220] ata5.00: error: { UNC }
[  133.545281] ata5.00: configured for UDMA/133
[  133.545301] sd 4:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=7s
[  133.545309] sd 4:0:0:0: [sda] tag#7 Sense Key : Medium Error [current] 
[  133.545315] sd 4:0:0:0: [sda] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
[  133.545321] sd 4:0:0:0: [sda] tag#7 CDB: Read(16) 88 00 00 00 00 00 c3 8d dc 00 00 00 08 00 00 00
[  133.545324] I/O error, dev sda, sector 3280854263 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 0
[  133.545392] ata5: EH complete
[  140.576143] ata5.00: exception Emask 0x0 SAct 0x6 SErr 0x0 action 0x0
[  140.576163] ata5.00: irq_stat 0x40000008
[  140.576176] ata5.00: failed command: READ FPDMA QUEUED
[  140.576186] ata5.00: cmd 60/00:08:00:e4:8d/04:00:c3:00:00/40 tag 1 ncq dma 524288 in
                        res 41/40:00:00:e7:8d/00:00:c3:00:00/40 Emask 0x409 (media error) <F>
[  140.576216] ata5.00: status: { DRDY ERR }
[  140.576227] ata5.00: error: { UNC }
[  140.577289] ata5.00: configured for UDMA/133
[  140.577306] sd 4:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=14s
[  140.577314] sd 4:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] 
[  140.577319] sd 4:0:0:0: [sda] tag#1 Add. Sense: Unrecovered read error - auto reallocate failed
[  140.577325] sd 4:0:0:0: [sda] tag#1 CDB: Read(16) 88 00 00 00 00 00 c3 8d e4 00 00 00 04 00 00 00
[  140.577328] I/O error, dev sda, sector 3280856832 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[  140.577374] ata5: EH complete
[  218.236458] ata5.00: exception Emask 0x0 SAct 0x801000 SErr 0x0 action 0x0
[  218.236481] ata5.00: irq_stat 0x40000008
[  218.236494] ata5.00: failed command: READ FPDMA QUEUED
[  218.236505] ata5.00: cmd 60/00:60:00:e8:8d/04:00:c3:00:00/40 tag 12 ncq dma 524288 in
                        res 41/40:00:40:e8:8d/00:00:c3:00:00/40 Emask 0x409 (media error) <F>
[  218.236535] ata5.00: status: { DRDY ERR }
[  218.236545] ata5.00: error: { UNC }
[  218.237653] ata5.00: configured for UDMA/133
[  218.237677] sd 4:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=7s
[  218.237684] sd 4:0:0:0: [sda] tag#12 Sense Key : Medium Error [current] 
[  218.237690] sd 4:0:0:0: [sda] tag#12 Add. Sense: Unrecovered read error - auto reallocate failed
[  218.237696] sd 4:0:0:0: [sda] tag#12 CDB: Read(16) 88 00 00 00 00 00 c3 8d e8 00 00 00 04 00 00 00
[  218.237699] I/O error, dev sda, sector 3280857152 op 0x0:(READ) flags 0x80700 phys_seg 118 prio class 0
[  218.237749] ata5: EH complete
[  246.572851] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x0
[  246.572874] ata5.00: irq_stat 0x40000008
[  246.572887] ata5.00: failed command: READ FPDMA QUEUED
[  246.572898] ata5.00: cmd 60/08:78:e0:01:40/00:00:58:01:00/40 tag 15 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  246.572928] ata5.00: status: { DRDY ERR }
[  246.572938] ata5.00: error: { UNC }
[  246.574011] ata5.00: configured for UDMA/133
[  246.574029] sd 4:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  246.574036] sd 4:0:0:0: [sda] tag#15 Sense Key : Medium Error [current] 
[  246.574042] sd 4:0:0:0: [sda] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
[  246.574048] sd 4:0:0:0: [sda] tag#15 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  246.574051] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  246.574085] ata5: EH complete
[  246.574082] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  311.945446] ata5.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
[  311.945465] ata5.00: irq_stat 0x40000008
[  311.945475] ata5.00: failed command: READ FPDMA QUEUED
[  311.945485] ata5.00: cmd 60/08:48:e0:01:40/00:00:58:01:00/40 tag 9 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  311.945510] ata5.00: status: { DRDY ERR }
[  311.945518] ata5.00: error: { UNC }
[  311.946566] ata5.00: configured for UDMA/133
[  311.946581] sd 4:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  311.946588] sd 4:0:0:0: [sda] tag#9 Sense Key : Medium Error [current] 
[  311.946592] sd 4:0:0:0: [sda] tag#9 Add. Sense: Unrecovered read error - auto reallocate failed
[  311.946597] sd 4:0:0:0: [sda] tag#9 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  311.946600] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  311.946627] ata5: EH complete
[  311.946623] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  372.175728] EXT4-fs warning (device sda): ext4_clear_journal_err:5759: Filesystem error recorded from previous mount: IO failure
[  372.175736] EXT4-fs warning (device sda): ext4_clear_journal_err:5760: Marking fs in need of filesystem check.
[  375.864654] EXT4-fs (sda): warning: mounting fs with errors, running e2fsck is recommended
[  377.699209] EXT4-fs (sda): recovery complete
[  379.526238] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none.
[  505.777772] ata5.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x0
[  505.777805] ata5.00: irq_stat 0x40000008
[  505.777816] ata5.00: failed command: READ FPDMA QUEUED
[  505.777825] ata5.00: cmd 60/08:38:e0:01:40/00:00:58:01:00/40 tag 7 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  505.777850] ata5.00: status: { DRDY ERR }
[  505.777859] ata5.00: error: { UNC }
[  505.778919] ata5.00: configured for UDMA/133
[  505.778934] sd 4:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  505.778941] sd 4:0:0:0: [sda] tag#7 Sense Key : Medium Error [current] 
[  505.778945] sd 4:0:0:0: [sda] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
[  505.778950] sd 4:0:0:0: [sda] tag#7 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  505.778953] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  505.778981] ata5: EH complete
[  505.778982] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  505.779010] Aborting journal on device sda-8.
[  505.852672] EXT4-fs (sda): Remounting filesystem read-only
[  509.438055] ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
[  509.438074] ata5.00: irq_stat 0x40000008
[  509.438085] ata5.00: failed command: READ FPDMA QUEUED
[  509.438094] ata5.00: cmd 60/08:a0:e0:01:40/00:00:58:01:00/40 tag 20 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  509.438119] ata5.00: status: { DRDY ERR }
[  509.438128] ata5.00: error: { UNC }
[  509.439207] ata5.00: configured for UDMA/133
[  509.439225] sd 4:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  509.439231] sd 4:0:0:0: [sda] tag#20 Sense Key : Medium Error [current] 
[  509.439236] sd 4:0:0:0: [sda] tag#20 Add. Sense: Unrecovered read error - auto reallocate failed
[  509.439241] sd 4:0:0:0: [sda] tag#20 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  509.439244] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  509.439278] ata5: EH complete
[  509.439277] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  513.102049] ata5.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
[  513.102069] ata5.00: irq_stat 0x40000008
[  513.102080] ata5.00: failed command: READ FPDMA QUEUED
[  513.102089] ata5.00: cmd 60/08:28:e0:01:40/00:00:58:01:00/40 tag 5 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  513.102114] ata5.00: status: { DRDY ERR }
[  513.102123] ata5.00: error: { UNC }
[  513.103179] ata5.00: configured for UDMA/133
[  513.103195] sd 4:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  513.103201] sd 4:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] 
[  513.103206] sd 4:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
[  513.103211] sd 4:0:0:0: [sda] tag#5 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  513.103214] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  513.103244] ata5: EH complete
[  513.103244] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  692.550096] EXT4-fs (sda): error count since last fsck: 101
[  692.550112] EXT4-fs (sda): initial error at time 1707475604: __ext4_get_inode_loc_noinmem:4505: inode 705474: block 721944636
[  692.550133] EXT4-fs (sda): last error at time 1707821995: __ext4_get_inode_loc_noinmem:4505: inode 705474: block 721944636
[  866.494640] ata5.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
[  866.494661] ata5.00: irq_stat 0x40000008
[  866.494674] ata5.00: failed command: READ FPDMA QUEUED
[  866.494685] ata5.00: cmd 60/08:10:e0:01:40/00:00:58:01:00/40 tag 2 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[  866.494715] ata5.00: status: { DRDY ERR }
[  866.494725] ata5.00: error: { UNC }
[  866.495838] ata5.00: configured for UDMA/133
[  866.495855] sd 4:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  866.495863] sd 4:0:0:0: [sda] tag#2 Sense Key : Medium Error [current] 
[  866.495868] sd 4:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error - auto reallocate failed
[  866.495874] sd 4:0:0:0: [sda] tag#2 CDB: Read(16) 88 00 00 00 00 01 58 40 01 e0 00 00 00 08 00 00
[  866.495877] I/O error, dev sda, sector 5775557088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  866.495909] EXT4-fs error (device sda): __ext4_get_inode_loc_noinmem:4505: inode #705474: block 721944636: comm pool-caja: unable to read itable block
[  866.495913] ata5: EH complete
[ 1049.519919] ata5.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
[ 1049.519941] ata5.00: irq_stat 0x40000008
[ 1049.519955] ata5.00: failed command: READ FPDMA QUEUED
[ 1049.519966] ata5.00: cmd 60/08:80:e0:01:40/00:00:58:01:00/40 tag 16 ncq dma 4096 in
                        res 41/40:00:e0:01:40/00:00:58:01:00/40 Emask 0x409 (media error) <F>
[ 1049.519996] ata5.00: status: { DRDY ERR }
[ 1049.520006] ata5.00: error: { UNC }
[ 1049.521075] ata5.00: configured for UDMA/133

sudo smartctl -a /dev/sda
[sudo] password for root: 
smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150500.55.44-default] (SUSE RPM)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WCC4N4HUCR4F
LU WWN Device Id: 5 0014ee 2b6684d8b
Firmware Version: 82.00A82
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Feb 13 13:42:24 2024 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 247)	Self-test routine in progress...
					70% of test remaining.
Total time to complete Offline 
data collection: 		(39540) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 397) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   199   199   051    Pre-fail  Always       -       12163
  3 Spin_Up_Time            0x0027   209   171   021    Pre-fail  Always       -       4525
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2725
  5 Reallocated_Sector_Ct   0x0033   181   181   140    Pre-fail  Always       -       567
  7 Seek_Error_Rate         0x002e   200   196   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       13872
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1967
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       101
193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       8400
194 Temperature_Celsius     0x0022   118   108   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   186   186   000    Old_age   Always       -       14
197 Current_Pending_Sector  0x0032   067   066   000    Old_age   Always       -       65131
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   195   000    Old_age   Always       -       57
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       1

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13780         -
# 2  Short offline       Completed without error       00%     13725         -
# 3  Short offline       Completed without error       00%     13722         -
# 4  Short offline       Completed without error       00%     13697         -
# 5  Short offline       Completed without error       00%     13685         -
# 6  Extended captive    Interrupted (host reset)      90%     13626         -
# 7  Extended captive    Interrupted (host reset)      90%     13626         -
# 8  Extended captive    Interrupted (host reset)      90%     13625         -
# 9  Extended captive    Interrupted (host reset)      90%     13625         -
#10  Short offline       Completed without error       00%     13620         -
#11  Short offline       Completed without error       00%     13619         -
#12  Extended offline    Aborted by host               10%     13619         -
#13  Extended offline    Interrupted (host reset)      90%     13600         -
#14  Extended offline    Aborted by host               90%     13593         -
#15  Conveyance offline  Interrupted (host reset)      10%     13589         -
#16  Conveyance offline  Interrupted (host reset)      10%     13589         -
#17  Conveyance offline  Completed without error       00%     13581         -
#18  Extended offline    Completed: read failure       90%     13535         4046770880
#19  Extended offline    Completed: read failure       90%     13534         4046770880
#20  Extended offline    Completed: read failure       90%     13534         4046770880
#21  Short offline       Completed: read failure       90%     13472         4046770880

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I started to backup some directories but now I can go through the dir tree with caja but can’t transfer, even with CLI rsync.

Thanks for your help

MrNice · February 13, 2024, 1:02pm

More

I tried to e2fsck the disk but it starts and fall in sleeping status. Seen with

ps -ef | grep e2fsck
pidof -x e2fsck
top -p7360

arvidjaar · February 13, 2024, 1:23pm

If you need to salvage data from this disk, use something ike dd_rescue to create disk image (which will miss bad sectors) and either try mounting this image or use some data rescue programs (like photorec).

MrNice · February 13, 2024, 1:34pm

Thanks hcvv for your tips.
This is a home computer with low budget. If I had a backup I wouldn’t be here asking for help.

Thankfully, arvidjaar has a good idea. I didn’t know that dd-rescure will miss the bad sectors. I’ll try it.

As I still see the dirs and files and can go through, I am wondering what could make the reading errors.

MrNice · February 13, 2024, 2:10pm

I found in Yast Software Management ddrescueview and gnu_ddrescue.
Do you know the both ? Which one I should use in my case ?
Thanks

nrickert · February 13, 2024, 2:25pm

Here, I have “dd_rescue” installed, though I have not needed to do any rescuing.

pavinjoseph · February 13, 2024, 3:56pm

Hope you take this as a lesson learned the hard way and test your backup/restore strategy. Have it written down somewhere!

mendres82 · February 14, 2024, 11:17pm

I don’t know why @hcvv’s post got hidden, but I guess some people don’t like the fact that if there’s no backup, things were not important.

Having said that, first rule is: don’t do anything to recover data directly on that drive. Don’t try to install something on it, don’t try to read out files, but create an image of the disk as suggested by @arvidjaar. Every attempt to access files on the drive could be the last one. So you definitely want to perform your rescue attempts on the copied image file, nothing else.

MrNice · February 15, 2024, 5:12pm

So, I installed and ran gnu_ddrescue.
After about 29% recover with only one error I got stuck.
I stopped the process, restarted the HD but now I get an error in my command.
I took the example in the doc here
See example3
My mapfile1

# Mapfile. Created by GNU ddrescue version 1.23
# Command line: ddrescue -f -n /dev/sda /dev/sdb mapfile1
# Start time:   2024-02-15 17:50:06
# Current time: 2024-02-15 17:53:50
# Copying non-tried blocks... Pass 1 (forwards)
# current_pos  current_status  current_pass
0xF01AC50000     ?               1
#      pos        size  status
0x00000000  0xC8AC870000  +
0xC8AC870000  0x00010000  *
0xC8AC880000  0x01CA0000  ?
0xC8AE520000  0x276C730000  +
0xF01AC50000  0x1CA86826000  ?

My command and error

sudo ddrescue -f -n -i F01AC55000 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
ddrescue: Bad or missing numerical argument.
Try 'ddrescue --help' for more information.

I incremented a bit the -i value

Just before posting, I found why this error. The documentation has and error, the value has to be as 0xF01AC55000.
Could help others.

hui · February 15, 2024, 5:36pm

Where do you see the error in the documentation?
It states clearly:

Example 3: While rescuing the whole drive /dev/sda to /dev/sdb, /dev/sda freezes up at position 12345678.
     ddrescue -f /dev/sda /dev/sdb mapfile         # /dev/sda freezes here
       (restart /dev/sda or reboot computer)
       (restart copy at a safe distance from the troubled sector)
     ddrescue -f -i 12350000 /dev/sda /dev/sdb mapfile
       (then copy backwards down to the troubled sector)
     ddrescue -f -R /dev/sda /dev/sdb mapfile

position 12345678 is bad
new start from 12350000

12345678 and 12350000 are only examples which need to be replaced with the real values. It is only used to demonstrate the needed distance between sectors.

MrNice · February 15, 2024, 7:05pm

I understand that. What I mean is, this command line return an error

sudo ddrescue -f -n -i F01AC55000 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
ddrescue: Bad or missing numerical argument.
Try 'ddrescue --help' for more information.

This command line works

sudo ddrescue -f -n -i 0xF01AC55000 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
....

Do you see the difference (0x)?

hui · February 15, 2024, 7:14pm

You didn’t pay attention to the sector stated in your mapfile. It states 0xF01AC50000 as bad sector. But you tried to use an invalid sector F01AC55000 by ommitting the 0x which is part of the sector number. Hence the response for a bad numerical argument…
So no issue in the documentation.

MrNice · February 16, 2024, 9:56am

Thank you hui for your answer and sorry for my ignorance.
Could you teach me?
For a valid sector, what command should I write, with 0x or without 0x before the hex value?

This is the first time I use gnu ddrescue. I don’t fully understand and don’t know how to calculate the next valid sector. Could you explain?

This is what I did so far by reading the documentation
sda was NOT mounted, sdb was mounted

sudo ddrescue -f -n /dev/sda /dev/sdb mapfile1

After 29%, the rescue was too slow and I stopped it. Then I started again with the same command, then same issue, too slow.
I restated with the following

sudo ddrescue -f -n -i 0xF01AC55000 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
(sizes limited to domain 1031241289728 B to 3000592982016 B of 3000592982016 B)
rescued: 0 B, tried: 0 B, bad-sector: 0 B, bad areas: 0

Current status
     ipos:    1031 GB, non-trimmed:   90660 kB,  current rate:       0 B/s
     opos:    1031 GB, non-scraped:        0 B,  average rate:   30826 B/s
non-tried:    1969 GB,  bad-sector:        0 B,    error rate:  90595 kB/s
  rescued:  119975 kB,   bad areas:        0,        run time:  1h  4m 51s
pct rescued:    0.00%, read errors:     1448,  remaining time:         n/a
                              time since last successful read:         18s
Copying non-tried blocks... Pass 5 (forwards) 
Unaligned read error. Is sector size correct?

It stopped itself.
Now could you help me? What should I try to first recover what is valid?

Many thanks

MrNice · February 16, 2024, 5:09pm

I forgot to post the mapfile

# Mapfile. Created by GNU ddrescue version 1.23
# Command line: ddrescue -f -n -i 0xF01AC55000 /dev/sda /dev/sdb mapfile1
# Start time:   2024-02-15 18:09:36
# Current time: 2024-02-15 19:14:27
# Copying non-tried blocks... Pass 5 (forwards)
# current_pos  current_status  current_pass
0xF027010000     ?               5
#      pos        size  status
0x00000000  0xC8AC870000  +
0xC8AC870000  0x00010000  *
0xC8AC880000  0x01CA0000  ?
0xC8AE520000  0x276C730000  +
0xF01AC50000  0x00005000  ?
0xF01AC55000  0x0726B000  +
0xF021EC0000  0x05150000  *
0xF027010000  0x004A0000  ?
0xF0274B0000  0x00020000  *
0xF0274D0000  0x07270000  ?
0xF02E740000  0x00020000  *
0xF02E760000  0x0E4F0000  ?
0xF03CC50000  0x00020000  *
0xF03CC70000  0x1C9F0000  ?
0xF059660000  0x00020000  *
0xF059680000  0x393F0000  ?
0xF092A70000  0x00020000  *
0xF092A90000  0x727F0000  ?
0xF105280000  0x00020000  *
0xF1052A0000  0xE4FF0000  ?
0xF1EA290000  0x00020000  *
0xF1EA2B0000  0x1C9FF0000  ?
0xF3B42A0000  0x00020000  *
0xF3B42C0000  0x393FF0000  ?
0xF7482B0000  0x00020000  *
0xF7482D0000  0x6FC7E0000  ?
0xFE44AB0000  0x00010000  *
0xFE44AC0000  0x6FC7E0000  ?
0x105412A0000  0x00010000  *
0x105412B0000  0x6FC7E0000  ?
0x10C3DA90000  0x00010000  *
0x10C3DAA0000  0x6FC7E0000  ?
0x1133A280000  0x00010000  *
0x1133A290000  0x6FC7E0000  ?
0x11A36A70000  0x00010000  *
0x11A36A80000  0x6FC7E0000  ?
0x12133260000  0x00010000  *
0x12133270000  0x6FC7E0000  ?
0x1282FA50000  0x00010000  *
0x1282FA60000  0x6FC7E0000  ?
0x12F2C240000  0x00010000  *
0x12F2C250000  0x6FC7E0000  ?
0x13628A30000  0x00010000  *
0x13628A40000  0x6FC7E0000  ?
0x13D25220000  0x00010000  *
0x13D25230000  0x6FC7E0000  ?
0x14421A10000  0x00010000  *
0x14421A20000  0x6FC7E0000  ?
0x14B1E200000  0x00010000  *
0x14B1E210000  0x6FC7E0000  ?
0x1521A9F0000  0x00010000  *
0x1521AA00000  0x6FC7E0000  ?
0x159171E0000  0x00010000  *
0x159171F0000  0x6FC7E0000  ?
0x160139D0000  0x00010000  *
0x160139E0000  0x6FC7E0000  ?
0x167101C0000  0x00010000  *
0x167101D0000  0x6FC7E0000  ?
0x16E0C9B0000  0x00010000  *
0x16E0C9C0000  0x6FC7E0000  ?
0x175091A0000  0x00010000  *
0x175091B0000  0x6FC7E0000  ?
0x17C05990000  0x00010000  *
0x17C059A0000  0x6FC7E0000  ?
0x18302180000  0x00010000  *
0x18302190000  0x6FC7E0000  ?
0x189FE970000  0x00010000  *
0x189FE980000  0x6FC7E0000  ?
0x190FB160000  0x00010000  *
0x190FB170000  0x6FC7E0000  ?
0x197F7950000  0x00010000  *
0x197F7960000  0x6FC7E0000  ?
0x19EF4140000  0x00010000  *
0x19EF4150000  0x6FC7E0000  ?
0x1A5F0930000  0x00010000  *
0x1A5F0940000  0x6FC7E0000  ?
0x1ACED120000  0x00010000  *
0x1ACED130000  0x6FC7E0000  ?
0x1B3E9910000  0x00010000  *
0x1B3E9920000  0x6FC7E0000  ?
0x1BAE6100000  0x00010000  *
0x1BAE6110000  0x6FC7E0000  ?
0x1C1E28F0000  0x00010000  *
0x1C1E2900000  0x6FC7E0000  ?
0x1C8DF0E0000  0x00010000  *
0x1C8DF0F0000  0x6FC7E0000  ?
0x1CFDB8D0000  0x00010000  *
0x1CFDB8E0000  0x6FC7E0000  ?
0x1D6D80C0000  0x00010000  *
0x1D6D80D0000  0x6FC7E0000  ?
0x1DDD48B0000  0x00010000  *
0x1DDD48C0000  0x6FC7E0000  ?
0x1E4D10A0000  0x00010000  *
0x1E4D10B0000  0x6FC7E0000  ?
0x1EBCD890000  0x00010000  *
0x1EBCD8A0000  0x6FC7E0000  ?
0x1F2CA080000  0x00010000  *
0x1F2CA090000  0x6FC7E0000  ?
0x1F9C6870000  0x00010000  *
0x1F9C6880000  0x6FC7E0000  ?
0x200C3060000  0x00010000  *
0x200C3070000  0x6FC7E0000  ?
0x207BF850000  0x00010000  *
0x207BF860000  0x6FC7E0000  ?
0x20EBC040000  0x00010000  *
0x20EBC050000  0x6FC7E0000  ?
0x215B8830000  0x00010000  *
0x215B8840000  0x6FC7E0000  ?
0x21CB5020000  0x00010000  *
0x21CB5030000  0x6FC7E0000  ?
0x223B1810000  0x00010000  *
0x223B1820000  0x6FC7E0000  ?
0x22AAE000000  0x00010000  *
0x22AAE010000  0x6FC7E0000  ?
0x231AA7F0000  0x00010000  *
0x231AA800000  0x6FC7E0000  ?
0x238A6FE0000  0x00010000  *
0x238A6FF0000  0x6FC7E0000  ?
0x23FA37D0000  0x00010000  *
0x23FA37E0000  0x6FC7E0000  ?
0x2469FFC0000  0x00010000  *
0x2469FFD0000  0x6FC7E0000  ?
0x24D9C7B0000  0x00010000  *
0x24D9C7C0000  0x6FC7E0000  ?
0x25498FA0000  0x00010000  *
0x25498FB0000  0x6FC7E0000  ?
0x25B95790000  0x00010000  *
0x25B957A0000  0x6FC7E0000  ?
0x26291F80000  0x00010000  *
0x26291F90000  0x6FC7E0000  ?
0x2698E770000  0x00010000  *
0x2698E780000  0x6FC7E0000  ?
0x2708AF60000  0x00010000  *
0x2708AF70000  0x6FC7E0000  ?
0x27787750000  0x00010000  *
0x27787760000  0x6FC7E0000  ?
0x27E83F40000  0x00010000  *
0x27E83F50000  0x6FC7E0000  ?
0x28580730000  0x00010000  *
0x28580740000  0x6FC7E0000  ?
0x28C7CF20000  0x00010000  *
0x28C7CF30000  0x6FC7E0000  ?
0x29379710000  0x00010000  *
0x29379720000  0x6FC7E0000  ?
0x29A75F00000  0x00010000  *
0x29A75F10000  0x6FC7E0000  ?
0x2A1726F0000  0x00010000  *
0x2A172700000  0x6FC7E0000  ?
0x2A86EEE0000  0x00010000  *
0x2A86EEF0000  0x6FC7E0000  ?
0x2AF6B6D0000  0x00010000  *
0x2AF6B6E0000  0x6FC7E0000  ?
0x2B667EC0000  0x00010000  *
0x2B667ED0000  0x4395A0000  ?
0x2BAA1470000  0x00006000  *

Thanks for your help

MrNice · February 17, 2024, 11:44am

I tried this command

sudo ddrescue -f -R /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1032 GB, tried: 6775 MB, bad-sector: 0 B, bad areas: 0

Current status
     ipos:    3000 GB, non-trimmed:    6795 MB,  current rate:       0 B/s
     opos:    3000 GB, non-scraped:        0 B,  average rate:   3591 kB/s
non-tried:    1961 GB,  bad-sector:        0 B,    error rate:  20381 kB/s
  rescued:    1032 GB,   bad areas:        0,        run time:         10s
pct rescued:   34.41%, read errors:      312,  remaining time:  4d  9h 21m
                              time since last successful read:          0s
Copying non-tried blocks... Pass 5 (backwards)
EOF found below the size calculated from mapfile

then I mounted the drive . I know, bad idea.
However, I can go through the dirs and I saved 2 small files to another drive.
Just after, the system unmounted the faulty drive
Then I ran

sudo ddrescue -f -n /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1032 GB, tried: 6795 MB, bad-sector: 0 B, bad areas: 0

Current status
     ipos:  861896 MB, non-trimmed:    6796 MB,  current rate:       0 B/s
     opos:  861896 MB, non-scraped:        0 B,  average rate:   11027 B/s
non-tried:    1961 GB,  bad-sector:        0 B,    error rate:    983 kB/s
  rescued:    1032 GB,   bad areas:        0,        run time:         25s
pct rescued:   34.41%, read errors:       16,  remaining time:   2110d  8h
                              time since last successful read:          0s
Copying non-tried blocks... Pass 5 (forwards)
Unaligned read error. Is sector size correct?

I checked sector size is 512
Now I don’t know how what to run to skip the bad sectors.
Any help?

christomonte11 · February 21, 2024, 10:18am

Hi y’all, this is what phind.com is saying about the current state of affairs here:

The discussion you’ve provided is a thread where users are trying to recover data from a failing hard drive using ddrescue. The ddrescue tool is designed to copy data from one file or block device to another, trying to rescue the good parts first in case of read errors. It uses a mapfile to keep track of the progress and to know which parts of the source drive have already been read or not.

The users are encountering various issues:

MrNice is trying to recover data from a failing drive. He initially starts the recovery process but it’s too slow, so he stops it and tries to restart it. He encounters an error with the -i option, which specifies the input position. The issue is resolved by including the 0x prefix in the sector address, as it is required by ddrescue to indicate that the number is hexadecimal.
hui explains that the example provided in the documentation is just that, an example, and that the actual sector numbers should be replaced with the real values from the mapfile.
MrNice continues to struggle with the recovery process. He tries to calculate the next valid sector but is not sure how to do it. He also encounters an “Unaligned read error,” which might be due to an incorrect sector size.
MrNice attempts to recover the drive by using the -R option to retry bad sectors in reverse. He also tries to mount the drive, which is not recommended during recovery, but does it anyway and manages to recover some files.
MrNice then tries to continue the recovery process with ddrescue -f -n /dev/sda /dev/sdb mapfile1 but encounters an “Unaligned read error” again. He mentions that the sector size is correct.

To address the issues:

When using ddrescue, it’s important to use the correct format for sector addresses, including the 0x prefix if the address is hexadecimal.
The mapfile generated by ddrescue should be used to determine the next sector to try to recover.
Mounting a failing drive is not recommended as it can cause further damage.
The -R option can be used to retry bad sectors in reverse, which might help in some cases.
The “Unaligned read error” could be due to a misconfiguration or an issue with the drive itself. It’s important to ensure that the sector size is correct and that the drive is properly connected.

Here is a general approach to using ddrescue for data recovery:

Create an image of the failing drive without trying to access the bad sectors directly to avoid further damage.
Use the mapfile generated by ddrescue to determine which sectors have been successfully read and which ones have not.
Retry bad sectors using the -R option or by specifying the position with the -i option.
If possible, try to recover files from the image rather than directly from the failing drive.

Remember that data recovery can be a complex process and there’s always a risk of further data loss. It’s important to have backups of important data and to proceed with caution.

END of phind.com response.

Therefore, my question would be, if the advised image had been created already, so that the original - failing - disk could be spared from now on. Has any substantial data been recovered from the original failing disk up to now?

Regards, M.

MrNice · February 22, 2024, 9:54am

Thank you christomonte11 for this valuable answer.
I didn’t know phind.com very interesting, I’ll try it.

So, meanwhile, I ran more commands.

sudo ddrescue -f -n -i 0xF24FC80000 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
(sizes limited to domain 1040720592896 B to 3000592982016 B of 3000592982016 B)
rescued: 196206 kB, tried: 118089 kB, bad-sector: 0 B, bad areas: 0

Current status
     ipos:    1040 GB, non-trimmed:  185923 kB,  current rate:       0 B/s
     opos:    1040 GB, non-scraped:        0 B,  average rate:   6610 kB/s
non-tried:    1959 GB,  bad-sector:        0 B,    error rate:  67829 kB/s
  rescued:  295358 kB,   bad areas:        0,        run time:         14s
pct rescued:    0.01%, read errors:     1036,  remaining time:  5d  4h 48m
                              time since last successful read:          0s
Copying non-tried blocks... Pass 5 (forwards)
Unaligned read error. Is sector size correct?
*************

sudo ddrescue -f -R /dev/sda /dev/sdb mapfile1
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 7481 MB, bad-sector: 0 B, bad areas: 0

Current status
     ipos:    3000 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    3000 GB, non-scraped:    7390 MB,  average rate:   3511 kB/s
non-tried:    1959 GB,  bad-sector:   338944 B,    error rate:    338 kB/s
  rescued:    1033 GB,   bad areas:      183,        run time:         15s
pct rescued:   34.45%, read errors:      663,  remaining time:         n/a
                              time since last successful read:          0s
Scraping failed blocks... (backwards)         
Unaligned read error. Is sector size correct?
**********************

sudo ddrescue -f -R /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 7391 MB, bad-sector: 338944 B, bad areas: 183

Current status
     ipos:    2991 GB, non-trimmed:    9383 MB,  current rate:       0 B/s
     opos:    2991 GB, non-scraped:    7390 MB,  average rate:   24948 B/s
non-tried:    1950 GB,  bad-sector:   338944 B,    error rate:   3491 MB/s
  rescued:    1033 GB,   bad areas:      183,        run time:         21s
pct rescued:   34.45%, read errors:   143200,  remaining time:         n/a
                              time since last successful read:          2s
Copying non-tried blocks... Pass 5 (backwards)
Unaligned read error. Is sector size correct?
***********************

sudo ddrescue -f -n /dev/sda /dev/sdb mapfile1
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 16774 MB, bad-sector: 338944 B, bad areas: 183

Current status
     ipos:    3000 GB, non-trimmed:    1959 GB,  current rate:       0 B/s
     opos:    3000 GB, non-scraped:    7441 MB,  average rate:       0 B/s
non-tried:        0 B,  bad-sector:   339456 B,    error rate:   1616 MB/s
  rescued:    1033 GB,   bad areas:      184,        run time:      8m 48s
pct rescued:   34.45%, read errors: 29755527,  remaining time:         n/a
                              time since last successful read:         n/a
Finished                                     
*********************

sudo ddrescue -f /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 1966 GB, bad-sector: 339456 B, bad areas: 184

Current status
     ipos:    3000 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    3000 GB, non-scraped:        0 B,  average rate:       0 B/s
non-tried:        0 B,  bad-sector:    1966 GB,    error rate:   3746 kB/s
  rescued:    1033 GB,   bad areas:       22,        run time: 10h 55m 36s
pct rescued:   34.45%, read errors:3841469233,  remaining time:         n/a
                              time since last successful read:         n/a
Finished                            
********************

sudo ddrescue -f -r3 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 1966 GB, bad-sector: 1966 GB, bad areas: 22

Current status
     ipos:    1631 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    1631 GB, non-scraped:        0 B,  average rate:     230 B/s
non-tried:        0 B,  bad-sector:    1966 GB,    error rate:  10165 kB/s
  rescued:    1033 GB,   bad areas:       16,        run time:  3h 17m 49s
pct rescued:   34.45%, read errors:1168493102,  remaining time:         n/a
                              time since last successful read:  3h 16m 36s
Retrying bad sectors... Retry 1 (forwards)^C
  Interrupted by user
**************************

sudo ddrescue -f -r3 /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 1966 GB, bad-sector: 1966 GB, bad areas: 16

Current status
     ipos:    1631 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    1631 GB, non-scraped:        0 B,  average rate:    480 kB/s
non-tried:        0 B,  bad-sector:    1966 GB,    error rate:   35328 B/s
  rescued:    1033 GB,   bad areas:       17,        run time:         12s
pct rescued:   34.45%, read errors:       70,  remaining time:    101d 12h
                              time since last successful read:          0s
Retrying bad sectors... Retry 1 (forwards)
Unaligned read error. Is sector size correct?
*********************************

sudo ddrescue -f -R -r3 /dev/sda /dev/sdb mapfile1
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 1966 GB, bad-sector: 1966 GB, bad areas: 19

Current status
     ipos:    1631 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    1631 GB, non-scraped:        0 B,  average rate:   1985 kB/s
non-tried:        0 B,  bad-sector:    1966 GB,    error rate:       0 B/s
  rescued:    1033 GB,   bad areas:       17,        run time:         31s
pct rescued:   34.45%, read errors:        1,  remaining time:  7d  3h 57m
                              time since last successful read:          0s
Retrying bad sectors... Retry 1 (backwards)
Unaligned read error. Is sector size correct?
************************

Now when I run a command

sudo ddrescue -f /dev/sda /dev/sdb mapfile1
[sudo] password for root: 
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1033 GB, tried: 1966 GB, bad-sector: 1966 GB, bad areas: 17

Current status
     ipos:        0 B, non-trimmed:        0 B,  current rate:       0 B/s
     opos:        0 B, non-scraped:        0 B,  average rate:       0 B/s
non-tried:        0 B,  bad-sector:    1966 GB,    error rate:       0 B/s
  rescued:    1033 GB,   bad areas:       17,        run time:          0s
pct rescued:   34.45%, read errors:        0,  remaining time:         n/a
                              time since last successful read:         n/a
Finished

but I can’t mount the destination drive /dev/sdb.
I had more success mounting the failed drive and copy some mores files to a good drive.

christomonte11 · February 22, 2024, 12:18pm

Hi , you say you cannot mount the ddrescue-created destination drive? So you have a destination partition aka file system - say it is a BtrFS file system - housed on your destination drive and you cannot mount the destination BtrFS partition after you plugged in the destination drive into your desktop computer, right? However if you have pluggedt the thing in, I assume you can find the destination partition as some /dev/sdX , right?

Do you have a partition manager handy? Can you see the destination partition therein? What does your partition manager have to say about the destination partition? Any complaints right away? BTW. maybe you also want to install the gparted manager, it is quite useful.

Can you try to “check” (context menu) that partition (don’t forget to press “do it now”). If gparted does a “check” it also tries to repair that partition. A detailed report pops up which can be exported, too. Maybe folks can see your report here in a couple of days?

How was it going?

Regards, M.

MrNice · February 23, 2024, 4:41pm

No, all the drives are ext4 and all have a switch on/off and mount on demand when I switch on.
As you can read in my first post, I used the full drive to clone the faulty one.

Source is /dev/sda destination is dev/sdb
Now, when I start /dev/sdb I get from dmesg

[21380.508354] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[21380.508853] ata6.00: ATA-9: WDC WD40EFRX-68WT0N0, 82.00A82, max UDMA/133
[21380.509092] ata6.00: 7814037168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[21380.509658] ata6.00: configured for UDMA/133
[21380.509858] scsi 5:0:0:0: Direct-Access     ATA      WDC WD40EFRX-68W 0A82 PQ: 0 ANSI: 5
[21380.510281] sd 5:0:0:0: Attached scsi generic sg0 type 0
[21380.510397] sd 5:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[21380.510404] sd 5:0:0:0: [sdb] 4096-byte physical blocks
[21380.510431] sd 5:0:0:0: [sdb] Write Protect is off
[21380.510438] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[21380.510474] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[21380.510519] sd 5:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[21380.534962] sd 5:0:0:0: [sdb] Attached SCSI disk
[21431.917717] EXT4-fs (sdb): ext4_check_descriptors: Block bitmap for group 16320 overlaps superblock
[21431.917735] EXT4-fs (sdb): group descriptors corrupted!

I get a window with:

Error mounting /dev/sdb at /run/media/jp/Store5: mount(2) systrem call failed.

This was the first time I used gnu ddrescue and I followed the documentation.
Maybe I should have created a partition instead, I mean: dev/sda1 /dev/sdb1

Gparted fail to check the drive and freeze.

christomonte11 · February 23, 2024, 6:18pm

Hi , via DDG I found this: Mount fails for EXT4 filesystem with error message “group descriptors corrupted!”.

So, could there really be a bug within the ext4 filesystem software your OS? Can you start your System using SystemRescueCD or the like? Is disk access any better?

Good luck!

Regards, M.