Some time ago one of my hard drives, a 3TB Seagate ST3000DM001, wouldn’t mount anymore. It worked fine up to the day before, except the week before there were some errors from a single file. Some GUI applications gave me errors about it, but cp created a copy that I was able to validate, even when moved back to the original path to replace the original file. I didn’t get any more errors about that file.
I’ve got Kubuntu 16.04. Starting up the computer with the drive attached takes an unsually long time, and there’s a strange clicking sound from the drive. Since the drive wouldn’t mount anymore, I’ve checked and tried a few things.
syslog:
/var/log/syslog.1:Dec 12 23:06:45 grimripper-desktop systemd[1]: dev-disk-byx2duuid-32798b9cx2da158x2d42f4x2db0d0x2dec13f1d9f287.device: Job dev-disk-byx2duuid-32798b9cx2da158x2d42f4x2db0d0x2dec13f1d9f287.device/start timed out.
Currently there are seven of those from last night but none from today.
sudo fdisk -l /dev/sdb
fdisk: laitetta /dev/sdb ei voi avata: I/O-virhe
(It says device /dev/sdb can’t be opened: I/O error)
sudo fsck -n /dev/sdb
fsck – util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: Attempt to read block from filesystem resulted in short read yritettäessä avata /dev/sdb
Could this be a zero-length partition?
(It says short read while trying to open /dev/sdb)
sudo file -s /dev/sdb
/dev/sdb: ERROR: cannot read `/dev/sdb' (Input/output error)
sudo smartctl -a /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-210-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST3000DM001
Serial Number: W1F1SHNJ
LU WWN Device Id: 5 000c50 05da67bd0
Firmware Version: CC24
User Capacity: 137 438 952 960 bytes [137 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s
Local Time is: Fri Oct 22 22:25:31 2021 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Read SMART Data failed: scsi error badly formed scsi parameters
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
Read SMART Log Directory failed: scsi error badly formed scsi parameters
Read SMART Error Log failed: scsi error badly formed scsi parameters
Read SMART Self-test Log failed: scsi error badly formed scsi parameters
Selective Self-tests/Logging not supported
I tried Analyse -> Quick Search with TestDisk, but it didn’t find any partitions.
Today I’ve had ddrescue running (the drive changed from sdb to sdd when I added a new drive):
sudo ddrescue /dev/sdd sdd.dd sdd.log
GNU ddrescue 1.19
Press Ctrl-C to interrupt
rescued: 0 B, errsize: 4142 MB, current rate: 0 B/s
ipos: 129520 kB, errors: 1, average rate: 0 B/s
opos: 129520 kB, run time: 13.47 h, successful read: 13.48 h ago
Scraping failed blocks... (forwards)
It hasn’t been able to rescue anything, and it’s been going at about 9MB/h which would mean several hundred years to finish a 3TB drive at that speed.
I’ve got about 40 million lines from today in syslog and kern.log, mostly repeating this:
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485325] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485336] ata5.00: irq_stat 0x40000001
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485344] ata5.00: failed command: READ DMA
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485359] ata5.00: cmd c8/00:00:00:00:00/00:00:00:00:00/e0 tag 28 dma 131072 in
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485359] res 51/04:00:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485367] ata5.00: status: { DRDY ERR }
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485373] ata5.00: error: { ABRT }
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485537] ata5.00: configured for UDMA/133
Dec 13 08:27:45 grimripper-desktop kernel: [ 825.485551] ata5: EH complete
There’s a few other things I’ve found, similar to ddrescue, but looking at what’s happening with that it seems a bit pointless and probably would take a long time.
Is there any way to recover the data on this drive?
