You are not logged in.
Pages: 1
Hello dear archers!
I have benefitted a long time already from this forum but now it's time for my first own post.
I copied a huge amount of files from one HDD to another and after ~2/3 the progress was stuck.
Nemo crashed when aborting the copy operation and the system wouldn't let me restart without password.
The target HDD was unresponsive since then and didn't let me mount or unmount.
I hesitated and searched for solutions but found nothing fitting, so I restarted regardless (jeah I know, maybe shouldn't have!).
On shutdown I got some unfamiliar errors
https://i.imgur.com/j3B5akn.jpg
https://i.imgur.com/HJi2qMC.jpg
Since then, I still can't mount the drive successfully, neither under arch nor Windows. (Windows told me I had to format the drive first - which I really don't want to.)
I had a similar problem with a USB pen drive before which seems to be fixed by itself by now. I doubt this will work here though.
I would appreciate any help to fix the drive, if you need more logs/info I will try my best to provide it.
Thanks in advance for your time!
Edit: forgot to mention, both HDDs are plugged in via USB.
moderator edit -- replaced oversized images with links.
Pasting pictures and code
Last edited by 2ManyDogs (2020-03-24 22:51:11)
Offline
Can you run a S.M.A.R.T. test on the drive? May not be possible with the USB interface.
Please also post the journal from the boot where the copy failed.
Offline
Unfortunately a tracker-process made my journal huge and quite messy, so I had to upload the journal as .txt into a GitHub repository.
Around 18:35 errors mentioning the sdf device appear.
I was able to run a short S.M.A.R.T test, the long one will take a few hours.
Afterwards the result of
sudo smartctl -H /dev/sdfwas:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.5.11-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.Edit:
The result of
sudo smartctl -l selftest /dev/sdfwas:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.5.11-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error device will be ready soon
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.And result of
sudo smartctl -a /dev/sdf gave:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.5.11-zen1-1-zen] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital AV-GP (AF)
Device Model: WDC WD20EURS-63S48Y0
Serial Number: WD-WCAZAJ018777
LU WWN Device Id: 5 0014ee 2b20e9670
Firmware Version: 51.0AB51
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Wed Mar 25 01:57:12 2020 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (38880) 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: ( 375) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status 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 196 196 051 Pre-fail Always - 706
3 Spin_Up_Time 0x0027 173 168 021 Pre-fail Always - 6316
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 119
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 60
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 100 100 000 Old_age Always - 118
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 110
194 Temperature_Celsius 0x0022 126 109 000 Old_age Always - 24
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 14
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
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 Extended offline Completed: read failure 90% 60 6479844
# 2 Short offline Completed: read failure 90% 60 6479840
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.Those two requests were made after the short test while the long was running.
Last edited by sleep-yearning (2020-03-25 01:01:58)
Offline
Mar 24 18:35:09 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:35:09 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:35:09 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:35:09 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 01 00 00
Mar 24 18:35:09 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
Mar 24 18:35:11 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:35:11 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:35:11 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:35:11 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 00 08 00
Mar 24 18:35:11 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 24 18:35:11 archX kernel: Buffer I/O error on dev sdf2, logical block 778851, async page read
Mar 24 18:35:14 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:35:14 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:35:14 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:35:14 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 00 08 00
Mar 24 18:35:14 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 24 18:35:14 archX kernel: Buffer I/O error on dev sdf2, logical block 778851, async page read
Mar 24 18:35:17 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:35:17 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:35:17 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:35:17 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 00 08 00
Mar 24 18:35:17 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 24 18:35:17 archX kernel: Buffer I/O error on dev sdf2, logical block 778851, async page read
Mar 24 18:35:21 archX tracker-store[9541]: OK
Mar 24 18:35:21 archX systemd[907]: tracker-store.service: Succeeded.
Mar 24 18:35:47 archX kernel: usb 2-4: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Mar 24 18:35:50 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:35:50 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:35:50 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:35:50 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 00 08 00
Mar 24 18:35:50 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 24 18:35:50 archX kernel: Buffer I/O error on dev sdf2, logical block 778851, async page read
Mar 24 18:36:21 archX kernel: usb 2-4: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Mar 24 18:36:23 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 24 18:36:23 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 24 18:36:23 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 24 18:36:23 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 63 1b 18 00 00 08 00
Mar 24 18:36:23 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6495000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 24 18:36:23 archX kernel: Buffer I/O error on dev sdf2, logical block 778851, async page readAt least one block on the drive has gone bad. What is the journal from the a boot where you can not mount the drive? If you filter it to just kernel messages you will exclude output from tracker e.t.c..
Offline
This is the journal from my current boot: https://gist.github.com/sleep-yearning/ … 0d51364702
Offline
At least one block on the drive has gone bad.
So it's a mechanical issue? Any chances to get it running again or at least save the data?
Offline
Mar 25 00:07:03 archX kernel: sd 7:0:0:0: [sdf] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
Mar 25 00:07:03 archX kernel: sd 7:0:0:0: [sdf] Write Protect is off
Mar 25 00:07:03 archX kernel: sd 7:0:0:0: [sdf] Mode Sense: 47 00 10 08
Mar 25 00:07:03 archX kernel: sd 7:0:0:0: [sdf] No Caching mode page found
Mar 25 00:07:03 archX kernel: sd 7:0:0:0: [sdf] Assuming drive cache: write through
Mar 25 00:07:04 archX kernel: sdf: sdf1 sdf2
Mar 25 00:07:04 archX kernel: sd 7:0:0:0: [sdf] Attached SCSI disk
Mar 25 00:07:04 archX kernel: ses 7:0:0:1: Attached Enclosure device
Mar 25 00:07:19 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=8s
Mar 25 00:07:19 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:19 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:19 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df b8 00 01 00 00
Mar 25 00:07:19 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479800 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Mar 25 00:07:22 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 25 00:07:22 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:22 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:22 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 e0 b8 00 01 00 00
Mar 25 00:07:22 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6480056 op 0x0:(READ) flags 0x80700 phys_seg 12 prio class 0
Mar 25 00:07:25 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 25 00:07:25 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:25 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:25 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df e0 00 00 01 00
Mar 25 00:07:25 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479840 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 25 00:07:25 archX kernel: Buffer I/O error on dev sdf2, logical block 6215648, async page read
Mar 25 00:07:28 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Mar 25 00:07:28 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:28 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:28 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df e1 00 00 07 00
Mar 25 00:07:28 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479841 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215649, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215650, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215651, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215652, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215653, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215654, async page read
Mar 25 00:07:28 archX kernel: Buffer I/O error on dev sdf2, logical block 6215655, async page read
Mar 25 00:07:31 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 25 00:07:31 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:31 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:31 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df e0 00 00 08 00
Mar 25 00:07:31 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479840 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215648, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215649, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215650, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215651, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215652, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215653, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215654, async page read
Mar 25 00:07:31 archX kernel: Buffer I/O error on dev sdf2, logical block 6215655, async page read
Mar 25 00:07:34 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 25 00:07:34 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:34 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:34 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df e0 00 00 01 00
Mar 25 00:07:34 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479840 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 25 00:07:34 archX kernel: Buffer I/O error on dev sdf2, logical block 6215648, async page read
Mar 25 00:07:37 archX kernel: sd 7:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Mar 25 00:07:37 archX kernel: sd 7:0:0:0: [sdf] tag#0 Sense Key : Medium Error [current]
Mar 25 00:07:37 archX kernel: sd 7:0:0:0: [sdf] tag#0 Add. Sense: Unrecovered read error
Mar 25 00:07:37 archX kernel: sd 7:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 62 df e1 00 00 07 00
Mar 25 00:07:37 archX kernel: blk_update_request: critical medium error, dev sdf, sector 6479841 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215649, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215650, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215651, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215652, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215653, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215654, async page read
Mar 25 00:07:37 archX kernel: Buffer I/O error on dev sdf2, logical block 6215655, async page read
Mar 25 00:07:55 archX kernel: kauditd_printk_skb: 5 callbacks suppressedThe journal shows more blocks that are unreadable. You could try cloning the disk see how much you can recover from it.
Once you have recovered everything you can try badblocks to force the drive to remap bad sectors. Sector remapping requires the drive has spare sectors left to remap.
Last edited by loqs (2020-03-25 01:39:44)
Offline
Okay, thanks a lot for the analysis and help so far!
I will have to order another device to clone this one, so this might take a few days.
Any more tips or explanations, why this could have happened?
The drive was rather new and not used that much.
Offline
Pages: 1