December 27, 20196 yr Since I'm a brand new user (to unraid and server worlds) and I've heard nothing but good things about support on the forum, I wanted to get your opinions. This is my first error (Device is disabled, contents emulated) Currently my system is stopped as I'm worried about losing the other 20TB of data This disk is one of 3 identical drives that are added through a Sata PCIe expander. Poor MB choice on first build. What is the next step? smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.88-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HITACHI HUA723030ALA640 Serial Number: YHHKYX6A LU WWN Device Id: 5 000cca 225d64217 Firmware Version: MKAONS01 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Dec 26 21:26:01 2019 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Disabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: 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: (27370) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 457) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance P-S--- 100 100 054 - 0 3 Spin_Up_Time POS--- 117 117 024 - 654 (Average 660) 4 Start_Stop_Count -O--C- 100 100 000 - 19 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate PO-R-- 100 100 067 - 0 8 Seek_Time_Performance P-S--- 100 100 020 - 0 9 Power_On_Hours -O--C- 100 100 000 - 251 10 Spin_Retry_Count PO--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 11 192 Power-Off_Retract_Count -O--CK 100 100 000 - 21 193 Load_Cycle_Count -O--C- 100 100 000 - 21 194 Temperature_Celsius -O---- 136 136 000 - 44 (Min/Max 20/51) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 1 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 7 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x20 GPL R/O 1 Streaming performance log [OBS-8] 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 63 Current Device Internal Status Data log 0x80 GPL R/W 63 Host vendor specific log 0x81-0x9f GPL,SL R/W 16 Host vendor specific log 0xa2 GPL VS 1 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) Device Error Count: 2 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register 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 [1] occurred at disk power-on lifetime: 250 hours (10 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 84 -- 51 05 40 00 00 15 8b 12 48 05 00 Error: ICRC, ABRT at LBA = 0x158b1248 = 361435720 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 05 40 00 c8 00 00 15 8b 1c c8 40 08 03:36:16.182 WRITE FPDMA QUEUED 61 05 40 00 c0 00 00 15 8b 17 88 40 08 03:36:16.178 WRITE FPDMA QUEUED 61 05 40 00 90 00 00 15 8b 12 48 40 08 03:36:16.174 WRITE FPDMA QUEUED 61 05 40 00 50 00 00 15 8b 0d 08 40 08 03:36:16.170 WRITE FPDMA QUEUED 61 05 40 00 b8 00 00 15 8b 07 c8 40 08 03:36:16.165 WRITE FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 70 00 00 08 25 85 c8 08 00 Error: IDNF at LBA = 0x082585c8 = 136676808 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 03 78 00 10 00 00 08 25 86 38 40 08 00:19:32.284 WRITE FPDMA QUEUED 61 00 70 00 f0 00 00 08 25 85 c8 40 08 00:19:32.277 WRITE FPDMA QUEUED 61 01 d8 00 78 00 00 08 25 83 f0 40 08 00:19:32.277 WRITE FPDMA QUEUED 61 05 40 00 60 00 00 08 25 7e b0 40 08 00:19:32.277 WRITE FPDMA QUEUED 61 05 40 00 48 00 00 08 25 79 70 40 08 00:19:32.271 WRITE FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 251 - 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. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 44 Celsius Power Cycle Min/Max Temperature: 36/44 Celsius Lifetime Min/Max Temperature: 20/51 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (85) Index Estimated Time Temperature Celsius 86 2019-12-26 19:19 42 *********************** ... ..( 7 skipped). .. *********************** 94 2019-12-26 19:27 42 *********************** 95 2019-12-26 19:28 41 ********************** ... ..( 8 skipped). .. ********************** 104 2019-12-26 19:37 41 ********************** 105 2019-12-26 19:38 42 *********************** ... ..( 2 skipped). .. *********************** 108 2019-12-26 19:41 42 *********************** 109 2019-12-26 19:42 41 ********************** 110 2019-12-26 19:43 42 *********************** ... ..( 24 skipped). .. *********************** 7 2019-12-26 20:08 42 *********************** 8 2019-12-26 20:09 43 ************************ ... ..( 9 skipped). .. ************************ 18 2019-12-26 20:19 43 ************************ 19 2019-12-26 20:20 44 ************************* 20 2019-12-26 20:21 43 ************************ ... ..( 58 skipped). .. ************************ 79 2019-12-26 21:20 43 ************************ 80 2019-12-26 21:21 44 ************************* 81 2019-12-26 21:22 44 ************************* 82 2019-12-26 21:23 44 ************************* 83 2019-12-26 21:24 43 ************************ 84 2019-12-26 21:25 44 ************************* 85 2019-12-26 21:26 44 ************************* SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 11 --- Lifetime Power-On Resets 0x01 0x010 4 251 --- Power-on Hours 0x01 0x018 6 1914518024 --- Logical Sectors Written 0x01 0x020 6 2131809 --- Number of Write Commands 0x01 0x028 6 16002824224 --- Logical Sectors Read 0x01 0x030 6 21749589 --- Number of Read Commands 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 130 --- Spindle Motor Power-on Hours 0x03 0x010 4 130 --- Head Flying Hours 0x03 0x018 4 21 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 11 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 1 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 2 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 44 --- Current Temperature 0x05 0x010 1 43 N-- Average Short Term Temperature 0x05 0x018 1 - N-- Average Long Term Temperature 0x05 0x020 1 51 --- Highest Temperature 0x05 0x028 1 20 --- Lowest Temperature 0x05 0x030 1 48 N-- Highest Average Short Term Temperature 0x05 0x038 1 25 N-- Lowest Average Short Term Temperature 0x05 0x040 1 - N-- Highest Average Long Term Temperature 0x05 0x048 1 - N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 68 --- Number of Hardware Resets 0x06 0x010 4 46 --- Number of ASR Events 0x06 0x018 4 1 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 1 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0009 2 11 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 10 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS
December 27, 20196 yr Community Expert Looks fine, problem likely the result of a bad SATA cable, but you can run an extended SMART test to confirm all is well.
December 27, 20196 yr Community Expert Would have been better to get us complete Diagnostics with the server still up. You will have to rebuild the disk to enable it again.
December 28, 20196 yr Author 18 hours ago, trurl said: Would have been better to get us complete Diagnostics with the server still up. You will have to rebuild the disk to enable it again. How do I go about doing this?
December 28, 20196 yr Community Expert I will explain how to get us complete diagnostics before I explain how to rebuild the disk. Then we will have a better idea if you have any other issues that might cause problems for the rebuild. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.
Archived
This topic is now archived and is closed to further replies.