January 22, 201610 yr I am poised to upgrade my older server to 6.1.7 from 4.7. I thought I saw information as I was closing the array down before a close down suggesting a drive failure was about to occur I cant see the information anymore. Could someone please cast an expert eye over the attached sys log and advise me accordingly. Thanks Peter syslog-2016-01-22.txt
January 22, 201610 yr The syslog doesn't cover much time or use of the array but nothing stands out. A more useful diagnostic for your drives would be SMART reports for each. See v5 help in my sig, I know you are on an older version but getting SMART should be the same.
January 22, 201610 yr Author I have run a smart report on the drive I suspected it to be, It the report did not show up in the sys log for some reason but I viewed in UnMenu drive reports. I dont think things look good? If I put in a new drive and pre-clear would parity rebuild it? smartctl -a -d ata /dev/sdn (disk4) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3617251 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Jan 22 21:31:51 2016 GMT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 73) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: (36000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 0x002f 152 152 051 Pre-fail Always - 132388 3 Spin_Up_Time 0x0027 189 169 021 Pre-fail Always - 5533 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5077 5 Reallocated_Sector_Ct 0x0033 136 136 140 Pre-fail Always FAILING_NOW 1213 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 044 044 000 Old_age Always - 41315 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 138 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 23 193 Load_Cycle_Count 0x0032 188 188 000 Old_age Always - 36608 194 Temperature_Celsius 0x0022 126 111 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 360 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 70 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 33 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 040 037 000 Old_age Offline - 42736 SMART Error Log Version: 1 ATA Error Count: 35 (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 35 occurred at disk power-on lifetime: 40577 hours (1690 days + 17 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 -- -- -- -- -- -- -- 40 51 00 b0 8f a0 ef Error: UNC at LBA = 0x0fa08fb0 = 262180784 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 08 8f a0 ef 08 01:19:39.684 READ DMA c8 00 00 08 86 a0 ef 08 01:19:39.439 READ DMA e5 00 00 00 00 00 00 08 01:19:39.439 CHECK POWER MODE Error 34 occurred at disk power-on lifetime: 40556 hours (1689 days + 20 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 -- -- -- -- -- -- -- 40 51 00 b8 78 a0 ef Error: UNC at LBA = 0x0fa078b8 = 262174904 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 90 78 a0 ef 08 1d+07:15:36.940 READ DMA c8 00 00 90 6f a0 ef 08 1d+07:15:35.132 READ DMA Error 33 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 -- -- -- -- -- -- -- 40 51 00 48 3a 17 ef Error: UNC at LBA = 0x0f173a48 = 253180488 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:34.687 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:34.687 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:34.683 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:34.683 SET FEATURES [set transfer mode] Error 32 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 -- -- -- -- -- -- -- 40 51 00 90 39 17 ef Error: UNC at LBA = 0x0f173990 = 253180304 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:31.535 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:31.535 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:31.531 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:31.531 SET FEATURES [set transfer mode] Error 31 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 -- -- -- -- -- -- -- 40 51 00 40 3a 17 ef Error: UNC at LBA = 0x0f173a40 = 253180480 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:27.171 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:27.171 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:27.167 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:27.167 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: unknown failure 90% 41314 - # 2 Short offline Completed: read failure 90% 40055 93257669 # 3 Short offline Completed: read failure 90% 40055 93257665 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.
January 22, 201610 yr Yes that drive needs replacing. How do the others look? A successful rebuild will be much more likely when all other drives are good. Technically it is not required for a rebuild drive to be clear. The only time a drive is required to be clear is when it will be added to a new slot so parity will remain valid. Preclear is often used to test drives even when a clear drive isn't required.
January 26, 201610 yr Author The new disk has arrived, do I need to format the disk for the rebuild to work? I understand the pre-clear is not required. Thanks
January 26, 201610 yr The new disk has arrived, do I need to format the disk for the rebuild to work? I understand the pre-clear is not required. Thanks NO!!! Format means "write an empty filesystem to this disk". That is what it has always meant in any operating system you have ever used. unRAID treats that write just like any other and updates parity so then your parity will say the disk has an empty filesystem. You assign the disk to the same slot as the drive you are replacing and when you start unRAID will rebuild to that disk. If you do this right unRAID should not offer to format the disk. Don't know how some people get to a state where they format a rebuild. Also, though not required I still recommend a preclear to test the disk.
January 26, 201610 yr The new disk has arrived, do I need to format the disk for the rebuild to work? I understand the pre-clear is not required. No. The rebuild process always wipes anything that is already on the disk and as recreates the file system that is being rebuilt. The only time you would ever format a disk in unRAID is when you want to lose its existing contents.
Archived
This topic is now archived and is closed to further replies.