Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


How bad is my disk?
New on LowEndTalk? Please Register and read our Community Rules.

How bad is my disk?

OseriOseri Member

Hello, I just got a Hetzner auction server and one of the disks shows 2 UDMA_CRC_Error_Count errors, shall I be concerned about?

Below is smartctl output:

[email protected] ~ # smartctl --all /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.19.5] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Ultrastar He10
Device Model:     HGST HUH721008ALE600
Serial Number:    7HKDAYGF
LU WWN Device Id: 5 000cca 257efe412
Firmware Version: LHGNT9G0
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Sep 15 00:47:03 2022 CEST
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:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
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:                (   93) 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:        (1048) 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   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   130   130   054    Pre-fail  Offline      -       108
  3 Spin_Up_Time            0x0007   199   199   024    Pre-fail  Always       -       301 (Average 359)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       13
  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   128   128   020    Pre-fail  Offline      -       18
  9 Power_On_Hours          0x0012   096   096   000    Old_age   Always       -       30770
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       13
 22 Helium_Level            0x0023   100   100   025    Pre-fail  Always       -       6553700
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       788
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       788
194 Temperature_Celsius     0x0002   187   187   000    Old_age   Always       -       32 (Min/Max 23/53)
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       -       2

SMART Error Log Version: 1
ATA Error Count: 2
        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 2 occurred at disk power-on lifetime: 3881 hours (161 days + 17 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 00 00 00 00  Error: ICRC, ABRT 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 00 a8 00 03 c3 40 08  12d+13:56:29.479  READ FPDMA QUEUED
  60 00 a0 00 07 c3 40 08  12d+13:56:29.444  READ FPDMA QUEUED
  47 00 01 13 00 00 a0 08  12d+13:56:29.439  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 08  12d+13:56:29.433  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 08  12d+13:56:29.428  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 1 occurred at disk power-on lifetime: 3881 hours (161 days + 17 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 43 00 00 00 00 00  Error: ICRC, ABRT 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 00 80 00 03 c3 40 08  12d+13:56:29.070  READ FPDMA QUEUED
  60 00 88 00 07 c3 40 08  12d+13:56:29.066  READ FPDMA QUEUED
  60 00 78 00 ff c2 40 08  12d+13:56:29.066  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 08  12d+13:56:29.057  FLUSH CACHE EXT
  61 20 38 40 23 f6 40 08  12d+13:56:29.038  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     30770         -
# 2  Extended offline    Completed without error       00%     30741         -

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.

Comments

  • You just drop them ticket for defective drive replacement with this smart log.
    Their support will check attached log and replace (or justify why not) disk.

    When I got same errors they replaced disk without any questions.

    Thanked by 2Oseri martheen
  • I also probably wouldn't be too concerned with whatever it is (even ignoring the link from emgh that suggests probably just a faulty cable).

    The two errors occurred at the same time, at 3881 hours. The disk is now at 30771 hours with no further errors, so even if there was a faulty portion of the disk, it looks like it's remapped it and it's no longer a problem.

    If you want to be really sure, and especially if you have nothing on the disk yet, fill it up with random data a couple of times and see if you get any more errors.

    dd if=/dev/urandom bs=16M | split -b 2G

    will create a lot of 2GB files with random data. Run that until the disk is full, delete them all and run again. If you don't have any more errors on SMART after that, it doesn't seem like it's a serious problem.

    Thanked by 3ehab Arkas Oseri
  • disk probably got disconnected while running a S.M.A.R.T. self-test
    nothing to worry about, happens when disk are hot swapped or the likes, esp. in a DC like Hetzners, where the disks are pulled, wiped and checked regularly.

    Thanked by 1Oseri
  • Thank you guys for your advice. Actually I sent a ticket to support and they confirmed is a non-critical error so my server shall be fine. Just for peace of mind I'll take @ralph advice to see if I get any further error.

  • jbilohjbiloh Administrator

    All spinning disks have sections of the platters that are not usable. This probably does not pose any risk to your data at this time.

    That said, since drive replacement is free to you as a dedicated server customer you might consider just doing it... Then again no guarantee the replacement disk is any better (it may not be new).

  • emgemg Member
    edited September 15

    @ralf said:
    I also probably wouldn't be too concerned with whatever it is (even ignoring the link from emgh that suggests probably just a faulty cable).

    The two errors occurred at the same time, at 3881 hours. The disk is now at 30771 hours with no further errors, so even if there was a faulty portion of the disk, it looks like it's remapped it and it's no longer a problem.

    If you want to be really sure, and especially if you have nothing on the disk yet, fill it up with random data a couple of times and see if you get any more errors.

    dd if=/dev/urandom bs=16M | split -b 2G

    will create a lot of 2GB files with random data. Run that until the disk is full, delete them all and run again. If you don't have any more errors on SMART after that, it doesn't seem like it's a serious problem.

    This command may run faster:
    cat /dev/urandom > wipefile; sync; sync; sleep 1; rm wipefile

    Explanation:
    Certain virtual machines of mine don't "shrink" properly unless you fill their virtual drive empty space with zeros first, defragment the drive next, and finally shrink it. This is the command I use to fill the drive with zeros. There are historical reasons for the extra sync commands. The extra sync commands are no longer needed, but they ensure that it'll work on any system, even the ancient ones.

    Ubuntu MATE 64-bit 22.04 with 8.2 Gbytes free space:

    Using cat = 21 seconds.

    $ date; cat /dev/zero > wipefile; sync; sync; sleep 1; sync; sync; sleep 1; rm wipefile; sync; sync; sleep 1; date
    Thu Sep 15 11:07:43 AM EDT 2022
    cat: write error: No space left on device
    Thu Sep 15 11:08:04 AM EDT 2022
    

    Using dd = 1 min, 3 sec:

    $ date; dd if=/dev/zero | split -b 2G; sync; sync; sleep 1; sync; sync; sleep 1; rm x*; sync; sync; sleep 1; date
    Thu Sep 15 11:10:29 AM EDT 2022
    split: xae: No space left on device
    Thu Sep 15 11:11:32 AM EDT 2022
    

    When I replaced "/dev/zero" with "/dev/urandom" the times were:

    Using cat = 48 seconds
    Using dd = 1 minute, 54 seconds

    IMPORTANT !!
    I forgot to mention ...
    -> Be sure you run my dd command in an empty directory.

    Otherwise the command will also delete any unrelated files that begin with the letter "x", due to the embedded " rm x* " command.

  • Try dd with a big block size like 16M as in my example. If it's below that it'll be intolerably slow. Above 16M it doesn't usually make all that much difference.

  • rm_rm_ Member
    edited September 15

    @Falzo said: disk probably got disconnected while running a S.M.A.R.T. self-test

    Not really. These are just from the poorly seated cable during normal operation. And yeah, only two errors which both happened about 3 years ago.

    @jbiloh said: That said, since drive replacement is free to you as a dedicated server customer you might consider just doing it...

    Even though free, environment-wise I hope this doesn't result in a good disk like this going to the trash. Hetzner, as they replied from the support, might not do that, but someone more automated and less caring like OVH, probably could.

  • emgemg Member
    edited September 16

    @ralf said:
    Try dd with a big block size like 16M as in my example. If it's below that it'll be intolerably slow. Above 16M it doesn't usually make all that much difference.

    One of my children suggested the same thing, so I tested it and learned that the "dd" command yielded the same speeds as the "cat" command if I used large block sizes rather than the default 512 bytes.

    Next I came here to update everyone, and found your post. You are right.

    The dd version would be something like, "dd if=/dev/urandom bs=16M ..."

    Thanked by 1ralf
Sign In or Register to comment.