March 23, 201115 yr Only just got unRAID setup, i'm a newb Anyway I had a powercut earlier and when the server came back online I had a red ball on one of my drives. Been following the troubleshooting guide here: http://www.lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F I've run the command: smartctl -a -d ata /dev/sde >/boot/smart.txt (sde is the correct drive) Here are the results of the SMART test: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1CZ701254 Firmware Version: 1AN10003 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: ATA-8-ACS revision 6 Local Time is: Wed Mar 23 16:38:50 2011 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: 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: (27240) 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: ( 255) minutes. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 77 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 061 060 025 Pre-fail Always - 11856 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1598 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 899 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 42 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 45 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 059 000 Old_age Always - 25 (Lifetime Min/Max 9/41) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5845 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. I can't make head no tales of it even after reading the recommended link. Any help in getting my array back to green would be much appreciated. Thanks
March 23, 201115 yr Only just got unRAID setup, i'm a newb Anyway I had a powercut earlier and when the server came back online I had a red ball on one of my drives. Been following the troubleshooting guide here: http://www.lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F I've run the command: smartctl -a -d ata /dev/sde >/boot/smart.txt (sde is the correct drive) Here are the results of the SMART test: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1CZ701254 Firmware Version: 1AN10003 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: ATA-8-ACS revision 6 Local Time is: Wed Mar 23 16:38:50 2011 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: 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: (27240) 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: ( 255) minutes. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 77 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 061 060 025 Pre-fail Always - 11856 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1598 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 899 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 42 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 45 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 059 000 Old_age Always - 25 (Lifetime Min/Max 9/41) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5845 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. I can't make head no tales of it even after reading the recommended link. Any help in getting my array back to green would be much appreciated. Thanks The smart report shows nothing unusual. Please attach a syslog. It might have the clues needed to identify why the disk was taken off-line. We know it was taken of-line because a "write" to it failed, we just do not know what kind of error was involved or even if it was after the power failure. (it could have been before and you might not have noticed the drive being disabled since the contents would be simulated by unRAID by using the parity disk in combination with all the other data disks. Joe L.
March 23, 201115 yr Author I've restarted and stopped python servers as well stopping the array and all sorts since I noticed it. Will any of that matter? Syslog is here: http://pastebin.com/nk1DD9Xv Thanks.
March 23, 201115 yr Unrelated but you also have HPA on these drives: ata1.00: HPA detected: current 312579695, native 312581808 ata1.00: ATA-7: WDC WD1600AAJS-00PSA0, 05.06H05, max UDMA/133 ata5.01: HPA detected: current 3907027055, native 3907029168 ata5.01: ATA-8: SAMSUNG HD203WI, 1AN10002, max UDMA/133 Edit: Noticed the link dropped a few times, Mar 23 15:45:12 unraid kernel: ata5.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 23 15:45:12 unraid kernel: ata5.01: hard resetting link Mar 23 15:45:12 unraid kernel: ata5.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 23 15:45:12 unraid kernel: ata5.02: hard resetting link Mar 23 15:45:12 unraid kernel: ata5.02: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Mar 23 15:45:12 unraid kernel: ata5.03: hard resetting link Mar 23 15:45:12 unraid kernel: ata5.03: failed to resume link (SControl 0) Mar 23 15:45:12 unraid kernel: ata5.03: SATA link down (SStatus 0 SControl 0) Mar 23 15:45:12 unraid kernel: ata5.04: hard resetting link Mar 23 15:45:12 unraid kernel: ata5.04: failed to resume link (SControl 0) Mar 23 15:45:12 unraid kernel: ata5.04: SATA link down (SStatus 0 SControl 0) as well as these lines: Mar 23 16:02:39 unraid kernel: md: disk0 missing Mar 23 16:02:39 unraid kernel: md: disk1 missing Mar 23 16:02:39 unraid kernel: md: disk2 missing Mar 23 16:03:30 unraid kernel: md: disk1 missing Mar 23 16:03:30 unraid kernel: md: disk2 missing Mar 23 16:03:30 unraid kernel: md: disk3 removed
March 23, 201115 yr The SMART data appears OK. Generally, you unassign it and start the array. Then, stop the array and re-assign it. The next start will ask you if you want to rebuild the data onto this new drive. unRAID forgets any info about a drive if you start the array with it unassigned. I‘d want to investigate why the drive dropped out. It‘s possible you have a power supply or SATA cable issue. It shouldn‘t just happen for no reason. Now the odd part. Which disk is missing? I see 5 disks in the box and the data disk1, disk2, disk3 and cache all being created and mounted fine meaning 4 disks out of 5 are data disks. I‘d then think the 5th drive is parity. I did not see any disk errors or any other disks being simulated. FYI, I also noticed HPA‘s on 2 disks sda and sdd. Are you running a Gigabyte board? Mar 23 15:45:12 unraid kernel: ata1.00: HPA detected: current 312579695, native 312581808 Mar 23 15:45:12 unraid kernel: ata1.00: ATA-7: WDC WD1600AAJS-00PSA0, 05.06H05, max UDMA/133 Mar 23 15:45:12 unraid kernel: ata5.01: HPA detected: current 3907027055, native 3907029168 Mar 23 15:45:12 unraid kernel: ata5.01: ATA-8: SAMSUNG HD203WI, 1AN10002, max UDMA/133 Peter
March 23, 201115 yr Author Firstly I'd like to add that I unassigned the disks and re-assigned them hoping it would solve the issue. Could that have anything to do with the issues your talking about? Secondly its a ZOTAC NM10 F-E board. Thirdly I'm a moron that likes to shoot first and ask questions later as you can quite clearly see lol! EDIT: Also its disk3 that has the red ball. EDIT2: May I also add that the drives that have HPA were previously used with a gigabyte board. The WD drive is what I'm using as cache and the Samsung may be the drive that's causing the issue. EDIT3: Just been reading about HPA. I'll remove that when I get home. So should I be good just to unassign the disk, reboot, reassign and reboot? Or can I do this: http://www.lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily EDIT4: Sorry for all these edits. May I add that I don't care about the data on this drive. There's only 50GB written to it and I still have a copy of it on another machine that I can easily copy back across. Does that change anything?
March 23, 201115 yr do NOTdo anything about the HPA until you get the array back to normal. You will cause more problems if you do it in the middle of a recovery effort
March 23, 201115 yr That is odd because I do not see anything indicating disk3 did not get mounted. However, you can start with it unassigned and then start again with it assigned and the drive will be rebuilt. Peter
March 23, 201115 yr Author If I rebuild the drive, how long will it take? Will it write out the entire drive or just the 50GB of data on it? Thanks
March 23, 201115 yr The entire drive and it will take likely 8 hours for a 2T drive. You could try the "trust my parity" procedure and then allow the parity check to complete if you know you did not write to that drive while it was failed or cause the failure by writing to it and you also know the drive and file-system on it are OK. Otherwise, the rebuild will reconstruct what unRAID thinks should be on the drive. Peter
March 23, 201115 yr Author How about unassigning the drive, restarting, pressing restore to reset the config and re-assigning each drive and re-running parity check. That way I can still use the array and get the drive back? Will that work or am I soling rubbish? Thanks.
March 23, 201115 yr Same difference. It'll take 8hrs or so to build parity. If the drive acts up you'll be in the same situation again. Peter
Archived
This topic is now archived and is closed to further replies.