You are not logged in.
Hi everybody,
After a reboot, this error appeared on my /boot (/dev/sda1) partition. I tried to solved this but after some commands and a reboot, the partitions on the /dev/sda disk where not listed anymore. I get this error (close to the first one):
ata6.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
ata6.00: irq_stat 0x40000008
ata6.00: failed command: READ FPDMA QUEUED
ata6.00: cmd 60/20:a0:00:00:00/00:00:00:00:00/40 tag 20 ncq dma 16384 in
res 41/40:20:00:00:00/00:00:00:00:00/40 Emask 0x409 (media error) <F>
ata6.00: status: { DRDY ERR }
ata6.00: error: { UNC }
ata6.00: configured for UDMA/100
sd 5:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 5:0:0:0: [sda] tag#20 Sense Key : Medium Error [current]
sd 5:0:0:0: [sda] tag#20 Add. Sense: Unrecovered read error - auto reallocate failed
sd 5:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00
print_req_error: I/O error, dev sda, sector 0
ata6: EH complete
Here is the smartctl -a /dev/sda:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-21-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD075
Serial Number: 346PTQUUT
LU WWN Device Id: 5 000039 561c02030
Firmware Version: AX0A4M
User Capacity: 750 156 374 016 bytes [750 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
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 (current: 3.0 Gb/s)
Local Time is: Fri Feb 9 14:39:04 2018 UTC
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 194) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 2356
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3654
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 066 066 000 Old_age Always - 13819
10 Spin_Retry_Count 0x0033 172 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3648
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 163
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 89
193 Load_Cycle_Count 0x0032 081 081 000 Old_age Always - 197659
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 31 (Min/Max 12/48)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 13
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 80
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 071 071 000 Old_age Always - 11977
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 269
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 568 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 568 occurred at disk power-on lifetime: 13819 hours (575 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 60 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 60 00 00 00 40 00 00:31:52.720 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:31:52.720 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:31:52.719 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 00:31:52.718 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:31:52.718 SET FEATURES [Set transfer mode]
Error 567 occurred at disk power-on lifetime: 13819 hours (575 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 d0 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 d0 00 00 00 40 00 00:31:48.918 READ FPDMA QUEUED
60 08 c8 e0 66 54 40 00 00:31:48.916 READ FPDMA QUEUED
60 08 b8 00 66 54 40 00 00:31:48.894 READ FPDMA QUEUED
ec 00 01 00 00 00 00 00 00:31:48.893 IDENTIFY DEVICE
ec 00 01 00 00 00 00 00 00:31:48.889 IDENTIFY DEVICE
Error 566 occurred at disk power-on lifetime: 13819 hours (575 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 e0 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 e0 00 00 00 40 00 00:31:45.086 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:31:45.085 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 00:31:45.085 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 00:31:45.084 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:31:45.084 SET FEATURES [Set transfer mode]
Error 565 occurred at disk power-on lifetime: 13819 hours (575 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 60 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 60 00 00 00 40 00 00:31:41.284 READ FPDMA QUEUED
60 08 58 e0 66 54 40 00 00:31:41.283 READ FPDMA QUEUED
60 08 48 00 66 54 40 00 00:31:41.259 READ FPDMA QUEUED
ec 00 01 00 00 00 00 00 00:31:41.257 IDENTIFY DEVICE
ec 00 01 00 00 00 00 00 00:31:41.254 IDENTIFY DEVICE
Error 564 occurred at disk power-on lifetime: 13819 hours (575 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 78 00 00 00 40 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 78 00 00 00 40 00 00:31:37.451 READ FPDMA QUEUED
60 08 70 e0 66 54 40 00 00:31:37.449 READ FPDMA QUEUED
60 08 f0 00 66 54 40 00 00:31:37.420 READ FPDMA QUEUED
ec 00 01 00 00 00 00 00 00:31:37.419 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 00 00:31:37.418 SET FEATURES [Enable SATA feature]
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% 13815 -
# 2 Short offline Completed: read failure 00% 13815 2048
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.
The partitions where like this:
- /boot part. of ~125M
- root part. of ~20G
- /home part. in the whole left space on the disk
I don't want to lose the data that where on the /dev/sda3 (/home) partition but the partitions can't be listed so I wonder if there is any hope and if the disk can still be used. Maybe somebody here can help me solve this.
Last edited by Delyas (2018-02-12 17:23:33)
Offline
This seems to indicate the disk is not trustworthy anymore:
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 152
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 13
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 80
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Actually that's wrong. It indicates that THIS DISK IS DEAD.
DO NOT BOOT IT but use a live system like grml and BACKUP AS MUCH AS YOU CAN! NOW!
dd or dd_rescue the entire disk onto a good one and then see whether you can find filesystems, see https://wiki.archlinux.org/index.php/Fi … d_PhotoRec
Do NOT operate on the failing disk except for cloning it.
Offline
I just started cloning the disc with ddrescue, following this link https://wiki.archlinux.org/index.php/di … g_ddrescue on a liveUSB.
Last edited by Delyas (2018-02-09 15:59:57)
Offline
I cloned the disk on another disk (/dev/sdc) with these commands:
ddrescue -f -n /dev/sda /dev/sdc rescue.log
ddrescue -d -f -r3 /dev/sda /dev/sdc rescue2.log
I tried the command
fsck -f /dev/sdc
but it gave me:
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a dos partition table in /dev/sdc
The same append with the given commands.
I mounted the /dev/sdc1 partiton (the only one that there is) but there is only what were on the /boot partition. Is there any hope to recover the data?
Last edited by Delyas (2018-02-10 18:53:50)
Offline
fsck operates on (formatted) partitions, not disks.
tesdisk can search for partitions, see https://www.cgsecurity.org/wiki/TestDis … partitions and check the entire documentation over there on how to deal w/ data.
When messing around, you should withdraw write permissions from that image (or clone it again to have a save backup from the image you're messing around with)
Offline
Thank you for you help, I was able to retrieve the partitions in the cloned disk with TestDisk's quick search. Only the /boot partition was damaged so the personal data were still there.
Offline