jcreynoldsii Posted June 29, 2015 Share Posted June 29, 2015 I came down to look as my unraid box and saw that one of my drives had 780 million errors on it. So I powered down my server and and checked all sata and power connections and rebooted. Unraid would not boot and the disk is clicking. So I changed out the sata cable and went to a different port on the MOBO and I still have the same result. After waiting for a while the server finally came up but it says disk 2 is not installed. Can anyone give me advice on what to do next? If you need logs let me know I will post them. I also now have another drive showing reallocated sectors, WTF? Is that just a coincidence or could it be related? Forgot to mention this all happened after I upgraded to 6.0.1. Is there any known issues with this version? Quote Link to comment
trurl Posted June 29, 2015 Share Posted June 29, 2015 Tools - Diagnostics. Collect and post Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 Tools - Diagnostics. Collect and post Attached bennysrv-diagnostics-20150629-1224.zip Quote Link to comment
trurl Posted June 29, 2015 Share Posted June 29, 2015 Disk 3 does not look good, but can't do anything about that with disk 2 disabled. Make sure nothing else writes to the server while in this state. Do you have another disk you can use to rebuild disk 2? Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 I do have another disk but its not a 4tb drive, I assume that doesn't matter? Quote Link to comment
itimpi Posted June 29, 2015 Share Posted June 29, 2015 I do have another disk but its not a 4tb drive, I assume that doesn't matter? If you want to replace a drive then the replacement needs to be the same size or larger (and cannot ever be larger than the parity disk). Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 I currently do not have any data on my unraid server. I am a new to unraid and I just have been recently getting everything together. Perhaps I clear my config and start all over from scratch. Quote Link to comment
trurl Posted June 29, 2015 Share Posted June 29, 2015 I currently do not have any data on my unraid server. I am a new to unraid and I just have been recently getting everything together. Perhaps I clear my config and start all over from scratch. Start by preclearing every disk. Search for the preclear script or use the plugin. It seems like you are trying to build your server with unreliable disks. Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 All disks were precleared 3x prior to going into an array. Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 I had my array up and running on 6.0.0 with no issues. I started having issues as soon as I went to 6.0.1. I plan to back track and clear my config, reformat my thumb drive and install 6.0.0 and try to rebuild my array. Quote Link to comment
trurl Posted June 29, 2015 Share Posted June 29, 2015 I had my array up and running on 6.0.0 with no issues. I started having issues as soon as I went to 6.0.1. I plan to back track and clear my config, reformat my thumb drive and install 6.0.0 and try to rebuild my array. These are hardware issues. Can you even see drive 2 in the BIOS? It is may be the clicking drive and can no longer be accessed, or maybe it isn't plugged in good or its port isn't working for some reason. Drive 3 has an unacceptable number of pending reallocations. That is the only component we have good diagnostics on, and they are very bad. What else can you tell us about your hardware? What is the exact model of your power supply? Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 I just upgraded the PSU: http://www.newegg.com/Product/Product.aspx?Item=N82E16817153198 MOBO: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128659 CPU: http://www.newegg.com/Product/Product.aspx?Item=N82E16819113379 Memory: http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314 I guess drive 3 could be failing I just don't want to believe it at this time. As far as the bios goes I will have to check when I get home. Quote Link to comment
trurl Posted June 29, 2015 Share Posted June 29, 2015 I wouldn't trust it, but you should at least preclear the Seagate again smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: S1F0GJMH LU WWN Device Id: 5 000c50 04b6af3c8 Firmware Version: CC9E User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Jun 29 12:25:19 2015 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: (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: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 331) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3081) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 112 084 006 Pre-fail Always - 42224464 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 82 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 680 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1267894 9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 19486 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 76 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 848 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 075 052 045 Old_age Always - 25 (Min/Max 22/25) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 68 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2475 194 Temperature_Celsius 0x0022 025 048 000 Old_age Always - 25 (0 14 0 0 0) 197 Current_Pending_Sector 0x0012 079 079 000 Old_age Always - 3528 198 Offline_Uncorrectable 0x0010 079 079 000 Old_age Offline - 3528 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 1396h+21m+19.087s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2630798061139 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1506615194259 SMART Error Log Version: 1 ATA Error Count: 848 (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 848 occurred at disk power-on lifetime: 19454 hours (810 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 b8 ff ff ff ef 00 14:13:09.912 READ DMA EXT 25 00 40 ff ff ff ef 00 14:13:09.895 READ DMA EXT ef 10 02 00 00 00 a0 00 14:13:09.894 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 14:13:09.894 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 14:13:09.893 IDENTIFY DEVICE Error 847 occurred at disk power-on lifetime: 19454 hours (810 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 14:13:06.510 READ DMA EXT 25 00 80 ff ff ff ef 00 14:13:06.502 READ DMA EXT ef 10 02 00 00 00 a0 00 14:13:06.501 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 14:13:06.501 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 14:13:06.501 IDENTIFY DEVICE Error 846 occurred at disk power-on lifetime: 19454 hours (810 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 14:13:00.066 READ DMA EXT 25 00 80 ff ff ff ef 00 14:13:00.007 READ DMA EXT 25 00 80 ff ff ff ef 00 14:12:51.713 READ DMA EXT 25 00 40 ff ff ff ef 00 14:12:48.895 READ DMA EXT 25 00 68 ff ff ff ef 00 14:12:46.628 READ DMA EXT Error 845 occurred at disk power-on lifetime: 19454 hours (810 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 80 ff ff ff ef 00 14:12:40.321 READ DMA EXT 25 00 40 ff ff ff ef 00 14:12:40.026 READ DMA EXT 25 00 40 ff ff ff ef 00 14:12:39.354 READ DMA EXT 25 00 80 ff ff ff ef 00 14:12:39.347 READ DMA EXT ef 10 02 00 00 00 a0 00 14:12:39.346 SET FEATURES [Enable SATA feature] Error 844 occurred at disk power-on lifetime: 19454 hours (810 days + 14 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 14:12:35.627 READ DMA EXT 25 00 98 ff ff ff ef 00 14:12:33.476 READ DMA EXT 25 00 50 ff ff ff ef 00 14:12:30.641 READ DMA EXT 25 00 70 ff ff ff ef 00 14:12:29.218 READ DMA EXT 25 00 40 ff ff ff ef 00 14:12:28.169 READ DMA EXT SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 Just seems weird all of a sudden I have issues with reallocated sectors and disk errors. I guess Seagate drives really are a piece of sh*t. Quote Link to comment
jcreynoldsii Posted June 29, 2015 Author Share Posted June 29, 2015 Preclearing the Seagate drive as we speak. The other drive I gave up on it is dead. It just clicks in an external as well. Quote Link to comment
jcreynoldsii Posted July 2, 2015 Author Share Posted July 2, 2015 Well that escalated quickly. How unfortunate, I'll never buy a Seagate again. 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.