rattfink Posted February 24, 2015 Share Posted February 24, 2015 I have a couple disks with reallocated sectors I need to upgrade ASAP but of course this morning one of my disks redballed so need to figure out what's wrong with this before replacing the other disks with reallocated sectors. I'm running Unraid 6b14. Disk 1 is showing "Faulty" on the Dashboard page and Red Ball on the "Main" page in Unraid. syslog.txt Quote Link to comment
trurl Posted February 24, 2015 Share Posted February 24, 2015 Red ball means a write to it has failed and unRAID has taken it offline. Any access to that disk will be emulated by the other drives plus parity. The usual procedure is to rebuild to a new disk, or possibly to the same disk if it can be determined that something else was the cause. You say you have 2 other suspect disks in addition to the redballed one? Post a smart report of each of these drives. Quote Link to comment
rattfink Posted February 24, 2015 Author Share Posted February 24, 2015 Well the disk that is redball is a new 3TB which has only been running for maybe a week or 2. What are the steps to determine if this is indeed a BAD disk and I need to replace it or if it's some other problem. I'm sure the recommended solution to every red ball disk is NOT to just replace it and rebuild... Isn't this real problem with the disk in the syslog? I just don't see anything in the syslog I attached which provides information on what the problem with the disk is. Maybe the steps to determine if a RED BALL disk should be replaced is by executing a smart report and that'll determine the need to replace the disk or not. Quote Link to comment
trurl Posted February 24, 2015 Share Posted February 24, 2015 I did say post a smart report of all of the suspect drives. Did you preclear any of your drives before using them? You will have to do a rebuild or a new config to get unRAID to use the disk again. Post the smart reports and we can go from there. Quote Link to comment
rattfink Posted February 24, 2015 Author Share Posted February 24, 2015 root@Tower:~# smartctl -a /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00SPEB0 Serial Number: WD-WCC4ECYT5N92 LU WWN Device Id: 5 0014ee 20a890e1d Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Feb 24 17:52:28 2015 EST 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: (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: (38880) 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: ( 390) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 181 177 021 Pre-fail Always - 7950 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 124 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1492 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 65 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 44 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1517 194 Temperature_Celsius 0x0022 130 119 000 Old_age Always - 22 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 Warning: ATA error count 2553 inconsistent with error log pointer 4 ATA Error Count: 2553 (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 2553 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:02.205 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:02.185 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.676 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.656 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] Error 2552 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 -- -- -- -- -- -- -- 04 61 08 00 10 00 e0 Device Fault; Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 e0 08 1d+10:07:01.676 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.656 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.616 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.107 READ DMA Error 2551 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.616 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.107 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.086 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] Error 2550 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 -- -- -- -- -- -- -- 04 61 08 00 10 00 e0 Device Fault; Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 08 00 10 00 e0 08 1d+10:07:01.107 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.086 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.047 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:00.537 READ DMA Error 2549 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.047 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:00.537 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:00.517 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:00.497 SET FEATURES [set transfer mode] 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. root@Tower:~# Yes I normally always run a preclear; actually running one now on new drive as possibly replacement but I guess I can't say 100% sure I ran preclear on the drive in question or not. So it sounds like what you're saying once a drive gets "RED BALL" for ANY reason unraid won't start using it again until a rebuild is executed or new config. Even if RED BALL was due to a faulty cable then a rebuild or new config would still need to be executed upon installing a new cable in order to remove the redball. Quote Link to comment
itimpi Posted February 24, 2015 Share Posted February 24, 2015 So it sounds like what you're saying once a drive gets "RED BALL" for ANY reason unraid won't start using it again until a rebuild is executed or new config. Even if RED BALL was due to a faulty cable then a rebuild or new config would still need to be executed upon installing a new cable in order to remove the redball. Yes. All unRAID knows is that a write failed so the data on the drive is now in an unknown state. You are expected to look at the information available and decide which of these is the way you wish to proceed. It is quite common to decide the disk is actually OK, and therefore rebuild onto itself to clear the error condition. Quote Link to comment
trurl Posted February 25, 2015 Share Posted February 25, 2015 So sdk is the drive with the redball? You mentioned a couple of other drives you were concerned about. What about their SMART reports? What about the size of these disks? Do you have a new disk you could rebuild onto? What I would probably do is rebuild onto a new disk. Preclear the new disk first so you can be reasonably sure it is good. Then, if the rebuild fails for some reason, you still have the original to try to recover files from. After you are confident the rebuild was successful, then you could preclear that disk and use it to rebuild one of your other suspect disks to, assuming it is big enough. Quote Link to comment
rattfink Posted February 26, 2015 Author Share Posted February 26, 2015 Finished pre-clearing new drive and raid is now rebuilding on new drive. What I couldn't figure out and wondering for future reference is how and is it possible to force a rebuild to the existing "red ball" drive? I couldn't find an option to force a rebuild. Quote Link to comment
trurl Posted February 26, 2015 Share Posted February 26, 2015 Finished pre-clearing new drive and raid is now rebuilding on new drive. What I couldn't figure out and wondering for future reference is how and is it possible to force a rebuild to the existing "red ball" drive? I couldn't find an option to force a rebuild. I think the way this is usually done is to stop the array, unassign the disk, start the array so unRAID sees it is missing, stop the array again, assign the disk, and start the array again. Don't remember if this is is exactly. Haven't done it. Unless you actually diagnose the real problem and determine it is not the drive, it's better to rebuild to a new drive. That way you still have the original disk and can possibly recover data from it if you have a problem during rebuild. Also, you can then really retest the drive by preclearing it. Quote Link to comment
hackztor Posted February 27, 2015 Share Posted February 27, 2015 Looks like the correct steps. Finished pre-clearing new drive and raid is now rebuilding on new drive. What I couldn't figure out and wondering for future reference is how and is it possible to force a rebuild to the existing "red ball" drive? I couldn't find an option to force a rebuild. I think the way this is usually done is to stop the array, unassign the disk, start the array so unRAID sees it is missing, stop the array again, assign the disk, and start the array again. Don't remember if this is is exactly. Haven't done it. Unless you actually diagnose the real problem and determine it is not the drive, it's better to rebuild to a new drive. That way you still have the original disk and can possibly recover data from it if you have a problem during rebuild. Also, you can then really retest the drive by preclearing it. 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.