Hello all

I'm experiencing a boot problems with an ubuntu desktop where the boot process drops to the busybox shell . I run fsck from a live version and at that point the system seems booting correctly but i found a lot of ata error running dmesg and in the syslog file like this:


Kernel: [18756.192066] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 0x0kernel: [18756.192072] ata5.00: irq_stat 0x40000008
kernel: [18756.192077] ata5.00: failed command: READ FPDMA QUEUED
kernel: [18756.192085] ata5.00: cmd 60/00:70:e0:08:1b/01:00:14:00:00/40 tag 14 ncq dma 131072 in
kernel: [18756.192085] res 41/40:70:70:09:1b/00:01:14:00:00/00 Emask 0x409 (media error) <F>
kernel: [18756.192088] ata5.00: status: { DRDY ERR }
kernel: [18756.192091] ata5.00: error: { UNC }
kernel: [18756.193158] ata5.00: configured for UDMA/133
kernel: [18756.193166] sd 4:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [18756.193167] sd 4:0:0:0: [sda] tag#14 Sense Key : Medium Error [current]
kernel: [18756.193169] sd 4:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
kernel: [18756.193170] sd 4:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 14 1b 08 e0 00 01 00 00
kernel: [18756.193171] print_req_error: I/O error, dev sda, sector 337316208
kernel: [18756.193179] ata5: EH complete
kernel: [18756.291949] ata5.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x0
kernel: [18756.291951] ata5.00: irq_stat 0x40000008
kernel: [18756.291953] ata5.00: failed command: READ FPDMA QUEUED
kernel: [18756.291955] ata5.00: cmd 60/08:38:70:09:1b/00:00:14:00:00/40 tag 7 ncq dma 4096 in
kernel: [18756.291955] res 41/40:08:70:09:1b/00:00:14:00:00/00 Emask 0x409 (media error) <F>
kernel: [18756.291956] ata5.00: status: { DRDY ERR }
kernel: [18756.291957] ata5.00: error: { UNC }
kernel: [18756.292911] ata5.00: configured for UDMA/133
kernel: [18756.29
i have also used smartd to check the status of the disk but the problems is the same. I'm do able to have a clair idea if i have hardware or software problems on the disk. i suppose to have hardware problems with the ssd but i would like to be sure...

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-64-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org


=== START OF INFORMATION SECTION ===
Device Model: SK hynix SC308 SATA 512GB
Serial Number: FJ6AN56621040AO1Q
Firmware Version: 30001P10
User Capacity: 512.110.190.592 bytes [512 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Jan 16 17:29:48 2020 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: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 4) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 105) seconds.
Offline data collection
capabilities: (0x19) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save 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: ( 40) minutes.


SMART Attributes Data Structure revision number: 0
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 166 166 006 Pre-fail Always - 53
5 Reallocated_Sector_Ct 0x0032 253 100 036 Old_age Always - 0
9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 21729
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 89
100 Unknown_Attribute 0x0032 098 098 000 Old_age Always - 89390658
171 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
174 Unknown_Attribute 0x0030 100 100 000 Old_age Offline - 44
175 Program_Fail_Count_Chip 0x0032 253 253 000 Old_age Always - 0
176 Erase_Fail_Count_Chip 0x0032 253 253 000 Old_age Always - 0
177 Wear_Leveling_Count 0x0032 037 037 000 Old_age Always - 677
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 000 Old_age Always - 96
179 Used_Rsvd_Blk_Cnt_Tot 0x0032 100 100 000 Old_age Always - 578
180 Unused_Rsvd_Blk_Cnt_Tot 0x0032 100 100 000 Old_age Always - 10430
181 Program_Fail_Cnt_Total 0x0032 253 253 000 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 253 253 000 Old_age Always - 0
183 Runtime_Bad_Block 0x0032 253 253 000 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 57
188 Command_Timeout 0x0032 253 253 000 Old_age Always - 0
191 Unknown_SSD_Attribute 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 035 000 000 Old_age Always - 35 (Min/Max 12/67)
195 Hardware_ECC_Recovered 0x0032 086 001 000 Old_age Always - 598249198
199 UDMA_CRC_Error_Count 0x0032 253 253 000 Old_age Always - 0
201 Unknown_SSD_Attribute 0x000e 100 100 000 Old_age Always - 53
204 Soft_ECC_Correction 0x000e 001 001 000 Old_age Always - 408369
231 Temperature_Celsius 0x0033 037 037 010 Pre-fail Always - 64
234 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 735787569568
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 30390826955
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 34100204301
250 Read_Error_Retry_Rate 0x0032 100 100 000 Old_age Always - 40172041


SMART Error Log Version: 1
ATA Error Count: 94 (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 94 occurred at disk power-on lifetime: 21727 hours (905 days + 7 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 00 00 00 00 00 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 30 c0 99 0d 40 40 2d+00:31:18.750 READ FPDMA QUEUED
47 00 01 30 08 00 a0 a0 2d+00:31:18.740 READ LOG DMA EXT
ef 10 02 00 00 00 a0 a0 2d+00:31:18.740 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 e0 2d+00:31:18.740 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 a0 2d+00:31:18.740 IDENTIFY DEVICE


Error 93 occurred at disk power-on lifetime: 21727 hours (905 days + 7 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 00 00 00 00 00 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 10 c0 99 0d 40 40 2d+00:31:18.700 READ FPDMA QUEUED
60 08 08 b8 99 0d 40 40 2d+00:31:18.700 READ FPDMA QUEUED
60 08 00 b0 99 0d 40 40 2d+00:31:18.700 READ FPDMA QUEUED
60 08 f0 a8 99 0d 40 40 2d+00:31:18.700 READ FPDMA QUEUED
60 08 e8 a0 99 0d 40 40 2d+00:31:18.700 READ FPDMA QUEUED


Error 92 occurred at disk power-on lifetime: 21727 hours (905 days + 7 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 00 00 00 00 00 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 18 e0 96 0d 40 40 2d+00:31:18.610 READ FPDMA QUEUED
61 08 10 c0 63 90 40 40 2d+00:31:18.610 WRITE FPDMA QUEUED
47 00 01 30 08 00 a0 a0 2d+00:31:18.610 READ LOG DMA EXT
ef 10 02 00 00 00 a0 a0 2d+00:31:18.610 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 e0 2d+00:31:18.610 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]


Error 91 occurred at disk power-on lifetime: 21727 hours (905 days + 7 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 00 00 00 00 00 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 e8 e0 96 0d 40 40 2d+00:31:18.560 READ FPDMA QUEUED
60 08 e0 d8 96 0d 40 40 2d+00:31:18.560 READ FPDMA QUEUED
60 08 d8 d0 96 0d 40 40 2d+00:31:18.560 READ FPDMA QUEUED
60 08 d0 c8 96 0d 40 40 2d+00:31:18.560 READ FPDMA QUEUED
60 08 c8 c0 96 0d 40 40 2d+00:31:18.560 READ FPDMA QUEUED


Error 90 occurred at disk power-on lifetime: 21727 hours (905 days + 7 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 00 00 00 00 00 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 50 38 8b 0d 40 40 2d+00:31:18.490 READ FPDMA QUEUED
47 00 01 30 08 00 a0 a0 2d+00:31:18.490 READ LOG DMA EXT
ef 10 02 00 00 00 a0 a0 2d+00:31:18.480 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 e0 2d+00:31:18.480 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 a0 2d+00:31:18.480 IDENTIFY DEVICE


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% 21727 -
# 2 Short offline Completed without error 00% 0 -


Selective Self-tests/Logging not supported

2916] sd 4:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: [18756.292917] sd 4:0:0:0: [sda] tag#7 Sense Key : Medium Error [current]
kernel: [18756.292318] sd 4:0:0:0: [sda] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
kernel: [18756.292919] sd 4:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 14 1b 09 70 00 00 08 00
kernel: [18756.292220] print_req_error: I/O error, dev sda, sector 337316208
kernel: [18756.292927] ata5: EH complete

but i don't know how to interpret these errors, they are hardware problems? I also used smartd but i have the same problems i'm not able to understandand the report. can you help to undestand if i face hardware or software problems?

See here for some info that may be helpful to you:

https://techoverflow.net/2016/07/25/...or-unc-at-lba/

giobaxx,

It seems strange that you have nothing listed for 197 Current_Pending_Sector which is often a culprit.

These links may help:
https://www.smartmontools.org/wiki/BadBlockHowto

https://bbs.archlinux.org/viewtopic.php?id=192065

https://www.linuxquestions.org/quest...ve-4175662039/

Tanks for all the links...it will help me to understand how to read the report......

1 members found this post helpful.

Whenever you post diagnostic data from a command you should wrap that output in code tags to make columnar data understandable. You can still do that here by editing your OP.

1 members found this post helpful.

Update:

Because of the error of dmesg i have re-seat the connection cable and the things seems going in the right way. We didn't receive any smartd alert via mail anymore, and in dmesg it does not appear the ata5 erros. Also the smart report has changed with the Soft Read Error Rate changed in the RAW Value from 53 to 0

I should say that the disk is fine, but i'm far from completely understand the tool so i'm not really sure. For example i run the extended test three time with the following result

And i don't understand if the read failure are related because historically happened read failure. The Extended test should run for 40 min but it finished max after one or two minute.

In addition the error below that still appear in the report

That i suppose are error happened and registered when the sata cable was badly connetcted...but also in this case i'm not sure...

I'm really confused....