comet424 Posted December 13, 2018 Share Posted December 13, 2018 hi i unable to reactivate my array.. or get the Faulty X off my one drive..is there a command to reforce it to reset.. it did a UDMA CRC error count and from what says online its not serious just a cable loose or something.. so i rechecked cable and pushed the drive in and out .. but didnt fix it . how do i fix it.. and here is the log file smart smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.18.17-unRAID] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD121KRYZ-01W0RB0 Serial Number: LU WWN Device Id: 5 000cca 253ce479f Firmware Version: 01.01H01 User Capacity: 12,000,138,625,024 bytes [12.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] 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 Dec 13 05:34:15 2018 EST 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: Enabled 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: (0x82) Offline data collection activity was completed without error. 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: ( 87) 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: (1303) 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--- 132 132 054 - 96 3 Spin_Up_Time POS--- 186 186 024 - 377 (Average 331) 4 Start_Stop_Count -O--C- 100 100 000 - 27 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--- 128 128 020 - 18 9 Power_On_Hours -O--C- 100 100 000 - 1052 10 Spin_Retry_Count PO--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 27 22 Unknown_Attribute PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 100 100 000 - 68 193 Load_Cycle_Count -O--C- 100 100 000 - 68 194 Temperature_Celsius -O---- 253 253 000 - 8 (Min/Max -3/25) 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-- 199 199 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 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 255 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 0x0c GPL R/O 5501 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x12 GPL R/O 1 SATA NCQ Non-Data log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x15 GPL R/W 1 Rebuild Assist log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 256 Current Device Internal Status Data log 0x25 GPL R/O 256 Saved Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host 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: 1 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 1 [0] occurred at disk power-on lifetime: 973 hours (40 days + 13 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 COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 84 -- 53 01 70 00 00 65 57 02 ef 40 00 Error: ICRC, ABRT 368 sectors at LBA = 0x655702ef = 1700201199 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 65 57 00 60 e0 08 24d+16:02:23.488 READ DMA EXT 25 00 00 05 40 00 00 65 56 fb 20 e0 08 24d+16:02:23.486 READ DMA EXT 25 00 00 02 c0 00 00 65 56 f8 60 e0 08 24d+16:02:23.480 READ DMA EXT 25 00 00 05 40 00 00 65 56 f3 20 e0 08 24d+16:02:23.478 READ DMA EXT 25 00 00 04 00 00 00 65 56 ef 20 e0 08 24d+16:02:23.473 READ DMA EXT SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1051 - # 2 Short offline Completed without error 00% 1030 - 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) SCT Support Level: 0 Device State: Active (0) Current Temperature: 8 Celsius Power Cycle Min/Max Temperature: 7/13 Celsius Lifetime Min/Max Temperature: -3/25 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 (43) Index Estimated Time Temperature Celsius 44 2018-12-13 03:27 9 - ... ..( 64 skipped). .. - 109 2018-12-13 04:32 9 - 110 2018-12-13 04:33 8 - ... ..( 7 skipped). .. - 118 2018-12-13 04:41 8 - 119 2018-12-13 04:42 7 - ... ..( 7 skipped). .. - 127 2018-12-13 04:50 7 - 0 2018-12-13 04:51 8 - ... ..( 15 skipped). .. - 16 2018-12-13 05:07 8 - 17 2018-12-13 05:08 7 - ... ..( 12 skipped). .. - 30 2018-12-13 05:21 7 - 31 2018-12-13 05:22 8 - ... ..( 10 skipped). .. - 42 2018-12-13 05:33 8 - 43 2018-12-13 05:34 9 - SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) supported [please try: '-l defects'] SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 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 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 3 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 2 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 Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 Re-enable the drive https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 ok thanks and i posted the diagnostic and the report above.. can you guys tell me if its safe to force it to reconstruct or do i need to get a replacement drive tower-diagnostics-20181213-0918.zip Quote Link to comment
JorgeB Posted December 13, 2018 Share Posted December 13, 2018 Disk look fine, if the emulated disk is mounting correctly replace the STA cable and rebuild. It is very cold, is your server in a refrigerator? 😛 Power Cycle Min/Max Temperature: 0/ 8 Celsius Lifetime Min/Max Temperature: -3/25 Celsius Likely a bad temp sensor. Quote Link to comment
JorgeB Posted December 13, 2018 Share Posted December 13, 2018 Well looking at the other disks looks like they are in a very cold environment: Power Cycle Min/Max Temperature: -5/ 5 Celsius Lifetime Min/Max Temperature: -7/43 Celsius This is not good, it can be as bad as high temps, min operating temp is 0C. Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 is the emulated drive the Parity drive?? as its fine its also 12TB the Disk 2 (12TB) got that error.. can you guys explain what that error says from that smart as for the drives ya i have a server in my shop its an uninsulated building i put there since i figured never have to need cooling its better then air conditioning free cold from the winter why is it bad if they really cold? but ok ill swap out this sata cable i planning on building new server case and then hot glue the sata cables to the hot swaps so they cant come out thanks for the input so far Quote Link to comment
JorgeB Posted December 13, 2018 Share Posted December 13, 2018 11 minutes ago, comet424 said: why is it bad if they really cold? Because disks are made to operate above freezing, and according to a test by Google IIRC, low temps, like <30C can be as bad for disks as hight temps, >45C, for better reliability disks should operate between those temps. Quote Link to comment
JonathanM Posted December 13, 2018 Share Posted December 13, 2018 10 minutes ago, comet424 said: why is it bad if they really cold? spinning bearings need lubrication. lubrication gets thick when it's cold. As long as you set the drives to never spin down you will be fine. Just don't shut down the server and let it get cold. Ideally you should build it a little insulated box with temperature controlled ventilation, so the server can keep itself warm, and use the cold outside air to moderate the heat. Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 ah ok i did shut server off to replace the cable but i found my cable too short so i just stuck old one back on and made sure she good and tight... i through a coat over it... and i guess i can pull the cooler fans off too.. i also have a Pfsense using a Micro gaming motherboarding and using a 120GB SSD and i have a towel over that so i dont have to clean the dust of it.. but is it safe as it doesnt have no spinning parts and i guess i can do that set it to never spin down... my hds do have a 5yr warrenty is it better for hard drives to never spin down Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 12 minutes ago, comet424 said: is the emulated drive the Parity drive? The emulated drive is the disabled drive, the one with the red X. When a write to a disk fails for whatever reason, Unraid disables the disk. After a disk is disabled, Unraid will not use it again until it is rebuilt. Any further attempts to read/write to that disk are done by emulating the disk from the parity calculation. If you read from the disk, Unraid doesn't actually attempt to read the disabled disk. Instead, it calculates the data by reading ALL other disks plus parity. If you write to the disk, Unraid doesn't actually attempt to write to the disabled disk. Instead, it updates parity as it would have if the disk had been written. So, on subsequent reads of the emulated disk, even that data can be calculated. Even the original failed write was emulated in this way, by updating parity. So the actual contents of the physical disk are no longer valid. But the valid contents are in the rest of the array from the parity calculation and the disk can be rebuilt so it will contain the complete and up-to-date valid contents. Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 learn something new everyday... its amazing how it knows how to emulated the data and stuff,,, way over my head.. for now i have it remounting fingers crossed... i got a coat over the intake.. and on weekend ill get another cable and ill unplug the fans are there any as i wanna get a Rackmount Case but are there any Temperature Sensor PC fan controllers you guys recommend as you mentioned about building a box and a sensor... is there one you guys recommend.. and i have set the hard drives from 15 min spin down to never Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 so the Array is started but Disk2 (12TB) still X and still states Faulty.. i take it it didnt work Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 2 minutes ago, comet424 said: for now i have it remounting What do you mean by that? I suspect you don't know what mounting even means. 1 minute ago, comet424 said: so the Array is started but Disk2 (12TB) still X and still states Faulty.. i take it it didnt work 9 minutes ago, trurl said: Unraid will not use it again until it is rebuilt. 1 hour ago, trurl said: Re-enable the drive https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 well remounting as i ment was Since the Array is unmounted.. and cant access Files... when you Click Start Array means remounting the drive is what i mean but ok miss read it too about removing the drive then readding the drive and starting and stopping array in the middle.. damn dislexia fingers crossed going to try now Quote Link to comment
itimpi Posted December 13, 2018 Share Posted December 13, 2018 The only way to clear the disabled status (without potential data loss) is to rebuild the disk so that the contents match the emulated disk. to do this: Stop the array set the disbled disk to “Unassigned” start the array. (you will be warned the array is now unprotect4d) stop the array reassign the disabled disk start the array (you will be told the disk is being rebuilt) the rebuild process will now start. Expect it to take a long time (roughly the same as a parity check). You can use the array while the disk is being rebuild but any disk I/O will slow down the rebuild process so you may prefer to leave it to complete first. Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 4 minutes ago, comet424 said: learn something new everyday... its amazing how it knows how to emulated the data and stuff,,, way over my head.. Parity isn't really very complicated. It is used in lots of ways in computers and communications. Understanding parity can help you understand many things about how Unraid works and how it makes you use it. Here is a wiki: https://wiki.unraid.net/UnRAID_6/Overview#Parity-Protected_Array 1 Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 ah ok ya i miss read it i was thinking just a simple Start stop procedure ya Partiy takes 23-25 Hours when doing the partiy check Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 ok thanks ill check out that article thank you for all the help soo far i really appreciate it Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 2 minutes ago, comet424 said: Partiy takes 23-25 Hours when doing the partiy check Seems pretty good for 12TB. Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 oh do they take longer usually?? its a WD Gold 12TB 7200RPM doing he PreClear x3 takes 1 week but they nice been a WD fan cuz of the 5 yrs i get and the Advanced Shipping of a replacement hard drive they offer instead of others you need to send in the hard drive before they send you one Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 My parity check for 6TB takes around 15 hours, but they are 5400rpm. Quote Link to comment
comet424 Posted December 13, 2018 Author Share Posted December 13, 2018 (edited) ah ok.. ya my drives are all 7200 rpms i been swaping out as my drives have been failing and i had them sitting mulitple computers now just made good server.. and then practice with a 2nd unriad as my backup of the main server.. well just the important like docs and photos they used to take longer with my 5400 and 5900 rpms and then on my other server i using just SATA 1 speed as that computer was 11 yrs old or so and the array is reconstructing so hopefully nothing bad goes down Edited December 13, 2018 by comet424 Quote Link to comment
Taddeusz Posted December 13, 2018 Share Posted December 13, 2018 (edited) Ouch, what are your disk tunables set to? My 9 drive 15TB array only takes about 8 hours to do a parity check. Edited December 13, 2018 by Taddeusz Quote Link to comment
itimpi Posted December 13, 2018 Share Posted December 13, 2018 15 minutes ago, Taddeusz said: Ouch, what are your disk tunables set to? My 9 drive 15TB array only takes about 8 hours to do a parity check. It is not the amount of data in the array that matters but the size of the largest drive in the array as far as estimating the elapsed time. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.