You are not logged in.

#1 2018-03-07 17:32:06

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

[SOLVED] Sata interface fatal errors

I am using arch and windows dual booted on a laptop.

I have been getting system freezes since yesterday. The whole system would freeze but mouse and current apps would stay responsive, they just don't do anything. I can switch between running apps but can't even open terminal. I switched to tty2 and login prompt would now appear. I had to hard reset the system. After rebooting the boot manager was missing and had to be reinstalled. This happened several times, I was able to catch it in cli and some errors showed up. Since the whole system was unresponsive, I took an image from my mobile:

https://i.imgur.com/CFc3Rx7.jpg

These crashes are now becoming more frequent so I am keeping the system off for now.

I would really appreciate any insight. Even a temporary fix would be great (this happened in middle of an important project).

Last edited by yash_aggarwal (2018-03-24 18:25:35)

Offline

#2 2018-03-07 17:35:11

Pryka
Member
Registered: 2018-02-07
Posts: 69

Re: [SOLVED] Sata interface fatal errors

Will you be able to provide S.M.A.R.T logs of this HDD?

Offline

#3 2018-03-07 17:55:58

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

Yeah, the system is stable again for now.

SMART Error Log Version: 1
ATA Error Count: 545 (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 545 occurred at disk power-on lifetime: 4886 hours (203 days + 14 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
  -- -- -- -- -- -- --
  84 51 01 07 99 ad 08  Error: ICRC, ABRT at LBA = 0x08ad9907 = 145594631

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 c8 00 99 ad 40 00      00:22:53.796  WRITE FPDMA QUEUED
  60 b0 c0 58 ad 3b 40 00      00:22:53.638  READ FPDMA QUEUED
  60 08 b8 80 3a 11 40 00      00:22:53.631  READ FPDMA QUEUED
  60 08 b0 68 bf 63 40 00      00:22:53.616  READ FPDMA QUEUED
  60 08 a8 30 09 54 40 00      00:22:53.603  READ FPDMA QUEUED

Error 544 occurred at disk power-on lifetime: 4886 hours (203 days + 14 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:22:51.121  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:22:51.110  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:22:51.081  READ DMA EXT
  25 00 01 01 00 00 40 00      00:22:51.081  READ DMA EXT
  25 00 01 00 00 00 40 00      00:22:51.061  READ DMA EXT

Error 543 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:33.942  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:33.931  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:33.902  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:33.901  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:33.854  READ DMA EXT

Error 542 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:32.720  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:32.709  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:32.680  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:32.679  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:32.678  READ DMA EXT

Error 541 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:32.631  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:32.620  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:32.593  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:32.593  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:32.571  READ DMA EXT

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%      4885         -
# 2  Extended offline    Aborted by host               90%      4885         -

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 am sorry if I am making this hard, I am complete noob in these matters.

Offline

#4 2018-03-07 17:59:17

Pryka
Member
Registered: 2018-02-07
Posts: 69

Re: [SOLVED] Sata interface fatal errors

Post the full output:

smartctl --all /dev/sdX

Offline

#5 2018-03-07 18:00:34

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.15.5-1-ARCH] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Travelstar 5K1000
Device Model:     HGST HTS541010A9E680
Serial Number:    JD1009DM1XDG7H
LU WWN Device Id: 5 000cca 827db00aa
Firmware Version: JA0OA560
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes 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 T13/1699-D revision 6
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Mar  7 23:29:59 2018 IST
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:                (   45) 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:        ( 238) 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   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   253   253   033    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0012   090   090   000    Old_age   Always       -       16489
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   089   089   000    Old_age   Always       -       4887
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1128
191 G-Sense_Error_Rate      0x000a   099   099   000    Old_age   Always       -       65537
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       94
193 Load_Cycle_Count        0x0012   077   077   000    Old_age   Always       -       232491
194 Temperature_Celsius     0x0002   171   171   000    Old_age   Always       -       35 (Min/Max 8/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       511
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 545 (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 545 occurred at disk power-on lifetime: 4886 hours (203 days + 14 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
  -- -- -- -- -- -- --
  84 51 01 07 99 ad 08  Error: ICRC, ABRT at LBA = 0x08ad9907 = 145594631

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 c8 00 99 ad 40 00      00:22:53.796  WRITE FPDMA QUEUED
  60 b0 c0 58 ad 3b 40 00      00:22:53.638  READ FPDMA QUEUED
  60 08 b8 80 3a 11 40 00      00:22:53.631  READ FPDMA QUEUED
  60 08 b0 68 bf 63 40 00      00:22:53.616  READ FPDMA QUEUED
  60 08 a8 30 09 54 40 00      00:22:53.603  READ FPDMA QUEUED

Error 544 occurred at disk power-on lifetime: 4886 hours (203 days + 14 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:22:51.121  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:22:51.110  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:22:51.081  READ DMA EXT
  25 00 01 01 00 00 40 00      00:22:51.081  READ DMA EXT
  25 00 01 00 00 00 40 00      00:22:51.061  READ DMA EXT

Error 543 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:33.942  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:33.931  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:33.902  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:33.901  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:33.854  READ DMA EXT

Error 542 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:32.720  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:32.709  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:32.680  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:32.679  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:32.678  READ DMA EXT

Error 541 occurred at disk power-on lifetime: 4885 hours (203 days + 13 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
  -- -- -- -- -- -- --
  84 51 01 01 00 00 00  Error: ICRC, ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  35 00 01 01 00 00 40 00      00:00:32.631  WRITE DMA EXT
  25 00 20 8f 6d 70 40 00      00:00:32.620  READ DMA EXT
  25 00 01 af 6d 70 40 00      00:00:32.593  READ DMA EXT
  25 00 01 01 00 00 40 00      00:00:32.593  READ DMA EXT
  25 00 01 00 00 00 40 00      00:00:32.571  READ DMA EXT

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%      4885         -
# 2  Extended offline    Aborted by host               90%      4885         -

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.

Offline

#6 2018-03-07 18:04:18

Pryka
Member
Registered: 2018-02-07
Posts: 69

Re: [SOLVED] Sata interface fatal errors

UDMA_CRC_Error_Count it's a transmission error. Try to change SATA cable and port on motherboard.

EDIT:
Also G-sense error rate is huge.  Is this a laptop? Is it getting any bigger? Some HDD show actual value from the sensor.

Last edited by Pryka (2018-03-07 18:09:50)

Offline

#7 2018-03-07 18:11:55

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

Yes I am on a laptop. I removed the back cover. There is no sata cable, the hard disk is slid into socket and then screwed in place. Should I replace the hard disk?

EDIT: starting to monitor it, will tell you if it increases

Last edited by yash_aggarwal (2018-03-07 18:12:42)

Offline

#8 2018-03-07 18:17:24

Pryka
Member
Registered: 2018-02-07
Posts: 69

Re: [SOLVED] Sata interface fatal errors

The best way to be sure in this situation would be to temporary change the HDD and check if UDMA_CRC_Error_Count still occurs. It's hard to tell for 100% who is the culprit because in this scenario it can be also faulty connector directly on Laptop.

Also You can check this HDD on some different computer and again watch if UDMA is getting any bigger. If not, its probably the connector on your laptop. If it still rises is the HDD itself.

Last edited by Pryka (2018-03-07 18:20:07)

Offline

#9 2018-03-07 18:20:02

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

Ok will try that. G-sense error is same so far. Will post updates after replacing the hard disk.
You have been very helpful. Thanks a lot!

Offline

#10 2018-03-07 18:21:14

Pryka
Member
Registered: 2018-02-07
Posts: 69

Re: [SOLVED] Sata interface fatal errors

Try to borrow HDD or use some old if you have, there is a chance this is not HDD and you will just waste money for the new one.

EDIT: Also backup your data, just in case.

Last edited by Pryka (2018-03-07 18:23:09)

Offline

#11 2018-03-07 22:17:46

R00KIE
Forum Moderator
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] Sata interface fatal errors

I second that the G-Sense_Error_Rate is a bit too high, another thing that jumps out is the high value of Load_Cycle_Count. The last one is a really large number and most disks have a specified lifetime number of cycle count of around 300000 so you might want to adjust the APM level to keep that number from increasing a lot more in a short amount of time.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#12 2018-03-13 21:04:21

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

Sorry R00KIE, Pryka. Didn't notice there were more replies. Unfortunately I wasn't able to test with another hard disk. Had to give my laptop to a technician, I just usually avoid going to them in my area because they can be quite unqualified. Once I had a guy claim 90 degrees was normal cpu temp in laptop.

Well I was able to back up most of my data. Thanks for your advice, will post results after I get back my laptop.

Last edited by yash_aggarwal (2018-03-13 21:04:57)

Offline

#13 2018-03-24 18:23:28

yash_aggarwal
Member
Registered: 2018-03-07
Posts: 7

Re: [SOLVED] Sata interface fatal errors

Apparently the problem was with the chip connecting hdd to the main board. Thanks a bunch. Your pointers really helped, found the problem after trying out a friends ssd.

Offline

Board footer

Powered by FluxBB