Everend Posted March 28, 2016 Share Posted March 28, 2016 So is there an issue with this Hitachi disk? Why are all the disks listed under Unassigned Devices? I tried to go and look at SMART but it doesn't show anything. I'm going to try shutdown and inspect cables since I just had the case open 24hrs ago. Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 It took about 30 minutes to stop the array. I selected to stop the array from the GUI, the status on the bottom continued to repeat something about 'unmounting the disks'. I restarted my windows machine (only other PC on network) to see if that was holding up the array stop somehow. I pulled the network cable, that didn't work either. I then logged on via the console CLI and started to follow the process in the docs to "cleanly Stop the array from the command line[edit]". I entered the first command listed "/root/samba stop" then tried the second set of commands "umount /dev/md1" the response was that this drive was not mounted. After a few minutes of trying the umount command I noticed the GUI had come back and asked for user/passwd. After logging into the GUI I found the array stopped so I was able to shutdown. I checked the cables and reboot, the drive is still red X. This drive was installed new on 3/4/16 after preclear in order to replace another failed drive just like it. Is it coincidence that the same Disk 2 has failed after 1 month twice? Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 After restart I am able to get a SMART report for this disk. smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.15-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: Hitachi HDS723020ALA640 Serial Number: MK0171YFJ4ERXD LU WWN Device Id: 5 000cca 223de3411 Firmware Version: MK7OAAU0 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm 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: Mon Mar 28 00:16:13 2016 CDT 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: ( 24) 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: ( 305) 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 134 134 054 Pre-fail Offline - 89 3 Spin_Up_Time 0x0007 130 130 024 Pre-fail Always - 480 (Average 480) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 95 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 123 123 020 Pre-fail Offline - 31 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 583 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 98 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 98 194 Temperature_Celsius 0x0002 153 153 000 Old_age Always - 39 (Min/Max 25/47) 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 - 13 SMART Error Log Version: 1 ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 582 hours (24 days + 6 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 20 20 fd 4a 03 Error: ICRC, ABRT 32 sectors at LBA = 0x034afd20 = 55246112 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 00 fd 4a e0 08 23:15:11.078 WRITE DMA EXT ef 10 02 00 00 00 a0 08 23:15:11.078 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 23:15:11.078 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 23:15:11.077 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23:15:11.077 SET FEATURES [set transfer mode] Error 12 occurred at disk power-on lifetime: 582 hours (24 days + 6 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 50 f0 fd 4a 03 Error: ICRC, ABRT 80 sectors at LBA = 0x034afdf0 = 55246320 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 00 fd 4a e0 08 23:14:40.231 WRITE DMA EXT ef 10 02 00 00 00 a0 08 23:14:40.231 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 23:14:40.231 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 23:14:40.230 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23:14:40.229 SET FEATURES [set transfer mode] Error 11 occurred at disk power-on lifetime: 582 hours (24 days + 6 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 80 c0 ff 4a 03 Error: ICRC, ABRT 128 sectors at LBA = 0x034affc0 = 55246784 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 00 fd 4a e0 08 23:14:09.385 WRITE DMA EXT ef 10 02 00 00 00 a0 08 23:14:09.385 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 23:14:09.385 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 23:14:09.384 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23:14:09.384 SET FEATURES [set transfer mode] Error 10 occurred at disk power-on lifetime: 582 hours (24 days + 6 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 70 d0 fe 4a 03 Error: ICRC, ABRT 112 sectors at LBA = 0x034afed0 = 55246544 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 00 fd 4a e0 08 23:13:38.108 WRITE DMA EXT 35 00 40 c0 f7 4a e0 08 23:13:38.105 WRITE DMA EXT 35 00 40 80 f2 4a e0 08 23:13:38.102 WRITE DMA EXT 35 00 40 40 ed 4a e0 08 23:13:38.100 WRITE DMA EXT 25 00 28 80 f2 12 e0 08 23:13:38.100 READ DMA EXT Error 9 occurred at disk power-on lifetime: 564 hours (23 days + 12 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 01 5f c0 c4 0b Error: ICRC, ABRT 1 sectors at LBA = 0x0bc4c05f = 197443679 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 20 40 c0 c4 e0 08 05:19:48.213 WRITE DMA EXT 25 00 20 40 c0 c4 e0 08 05:19:48.200 READ DMA EXT 25 00 00 f8 d0 3a e0 08 05:19:48.196 READ DMA EXT 25 00 00 f8 cc 3a e0 08 05:19:48.180 READ DMA EXT 25 00 00 f8 c8 3a e0 08 05:19:48.164 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short captive Completed without error 00% 0 - 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. Does this indicate the drive is bad? Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 Looks more like a bad sata cable, if you have it post the syslog before rebooting. 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 13 If you don't have the syslog replace cable and you can try to rebuild to same disk. Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 This is SMART after the reboot. I didn't see the unfinished procedure documentation until after rebooting, so I don't have a syslog from before. https://lime-technology.com/wiki/index.php/Fixing_a_drive_with_red_status_indicator Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 What happens if I start the rebuild and the disk is bad? Am I taking additional risk by trying to rebuild with this disk vs a new one from Best Buy tomorrow? (I'm trying to look around to figure out how to rebuild the same disk.) I've assigned a new disk before to start the rebuild but not the same disk. And that was a month ago, I'm having trouble remembering how I did it then. Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 Not really, but if the rebuild doesn't successfully complete then the disk is probably bad even though SMART looks fine, in that case use a new and tested replacement disk. Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 To rebuild on the same disk: -stop array -unassign disabled disk (select "no device") -start array -stop array -reassign disk -start array to begin rebuild Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 Also, note that in the screen shot before the reboot all the drives are show in the Unassigned Devices section. Is this expected behavior for a failed drive/sata cable? sorry I didn't get syslogs before reboot Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 To rebuild on the same disk: -stop array -unassign disabled disk (select "no device") -start array -stop array -reassign disk -start array to begin rebuild thanks! Rebuild started Link to comment
Everend Posted March 28, 2016 Author Share Posted March 28, 2016 Rebuild was successful. Any idea why in the OP screen shot before the reboot all the drives are show in the Unassigned Devices section? Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 No, you should report that on the UD plugin thread. Link to comment
itimpi Posted March 28, 2016 Share Posted March 28, 2016 Any idea why in the OP screen shot before the reboot all the drives are show in the Unassigned Devices section? I seem to remember this being mentioned before if the array ha not been started. Was it started in this case? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.