Skip to main content

Got A Bad Deal On A Disk

From:
root <myemailaddress.com>
To:root@archdesktop.localdomain
Bcc:
<myemailaddress.com>
Subject:SMART error (ErrorCount) detected on host: archdesktop
Date:Fri, 06 Oct 2017 18:01:17 +0800
This message was generated by the smartd daemon running on:


                      host name:  archdesktop
                      DNS domain: [Empty]

           The following warning/error was logged by the smartd daemon:

           Device: /dev/sda [SAT], ATA error count increased from 0 to 2

           Device info:
            Hitachi HUS724030ALE641, S/N:P8HEUS2R, WWN:5-000cca-22cd460f8, FW:MJ8OA5F0, 3.00 TB

           For details see host's SYSLOG.

           You can also use the smartctl utility for further investigation.
           No additional messages about this problem will be sent.

It seems SMART detected errors when I added a supposedly new disk to my RAID array.

$sudo smartctl -a /dev/sda

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: 18128 hours (755 days + 8 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 40 e0 e7 b7 01  Error: ICRC, ABRT at LBA = 0x01b7e7e0 = 28829664

  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 20 48 00 e4 b7 40 00      00:55:20.605  WRITE FPDMA QUEUED
  61 60 40 a0 e1 b7 40 00      00:55:20.597  WRITE FPDMA QUEUED
  61 08 38 98 e1 b7 40 00      00:55:20.594  WRITE FPDMA QUEUED
  61 10 30 88 e1 b7 40 00      00:55:20.594  WRITE FPDMA QUEUED
  61 10 28 78 e1 b7 40 00      00:55:20.593  WRITE FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 18128 hours (755 days + 8 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 c0 40 50 b5 01  Error: ICRC, ABRT at LBA = 0x01b55040 = 28659776

  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 40 78 c0 4f b5 40 00      00:55:17.832  WRITE FPDMA QUEUED
  61 c0 70 00 4c b5 40 00      00:55:17.827  WRITE FPDMA QUEUED
  61 c0 68 40 49 b5 40 00      00:55:17.821  WRITE FPDMA QUEUED
  61 40 60 00 44 b5 40 00      00:55:17.818  WRITE FPDMA QUEUED
  61 b0 58 50 40 b5 40 00      00:55:17.810  WRITE FPDMA QUEUED

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%     18151         -
# 2  Short offline       Completed without error       00%     18133         -
# 3  Vendor (0xb0)       Completed without error       00%     18015         -
# 4  Vendor (0x71)       Completed without error       00%     18015         -

This "new" disk has 18,124 power-on-hours. Somebody tried to clean it and pass it off as new. I bought this disk online. It's easy to get information from a disk when you're using SMART tools in your computer. But SMART gave it a PASSED tag. The error itself is discussed at this forum. Perhaps replacing the cable is next though.


Comments

Popular posts from this blog

ZFS Unable to System Snapshot, bpool is Full?

I first encountered the problem after a routine update / upgrade of the system. Well there was a kernel upgrade and I have not checked how many old kernels are still left for backups in /boot. Apparently, there was a few and the partition is 85% full. Every software update included a warning because of the restriction in disk space. Also, zfs could not create snapshots. It is also full. This is not very clear to me. Snapshots were suppose to be diff copies so why would it take up a large space. Most of the snapshots are less than 2MB. Or 0MB. Another problem that popped up is the constant freezing of Rhythmbox. I don't know if the config files are corrupted. The CPU cycles from one to the next. Peaks for 5-6 seconds then on to the next CPU. This forced me to download Clementine and Audacious. But both applications do not find the zfs pool or don't show the zfs structure. Why not? My final solution is to reinstall Rhythmbox via snaps. I re-scanned the music libr

Renter's ID and Business Licensing 2023

Last year's business permit application involved an undertaking of submitting lessee list to the Barangay in order to get them ID's including one for the lessor himself. I received a letter of notification just before New Year's Day. It informed me that I might be denied renewal of permits because I did not comply with this undertaking. So the Renter's ID is a serious thing now. When I went ahead and applied for a business permit renewal at the local government office everything went well except they want my list of lessee. So I had to backtrack and go to the Barangay and submit the list. They produced the ID's and I provided the photo ID's and of course have it signed by the lessee. After that, they pointed me to the cashier to pay the taxes and permit fees which totaled php15,305.00 ($280.33) During the payment of Fire and Safety department, they reminded me to bring my fire extinguisher official receipts of payment. I can pick up my new pe

How To Verify iso Image After Download In Linux

I assume that you have downloaded the image / iso file in a folder. Navigate to the folder where the iso is. You have to get the public gpg key for fedora downloads. [ donato@archdesktop Downloads]$ ls builds  debian-live--9.0.0-amd64-gnome  Fedora-Workstation-Live-x86_64-25  Fedora-Workstation-Live-x86_64-26 [ donato@archdesktop Downloads]$ cd Fedora-Workstation-Live-x86_64-26 [ donato@archdesktop Fedora-Workstation-Live-x86_64-26]$ ls Fedora-Workstation-26-1.5-x86_64-CHECKSUM  Fedora-Workstation-Live-x86_64-26-1.5.iso [ donato@archdesktop Fedora-Workstation-Live-x86_64-26]$ gpg --verify Fedora-Workstation-Live-x86_64-26-1.5.iso gpg: no valid OpenPGP data found. gpg: the signature could not be verified. Please remember that the signature file (.sig or .asc) should be the first file given on the command line. [ donato@archdesktop Fedora-Workstation-Live-x86_64-26]$ ls Fedora-Workstation-26-1.5-x86_64-CHECKSUM  Fedora-Workstation-Live-x86_64-26-1.5.iso