May 15, 201511 yr I just got two SATA cards and hooked up all of my 3x5 bays. I was experimenting a bit to try to understand how unraid works. I moved the parody drive to a new slot and it had to rebuild because I didn't take the array offline. After that I took the array offline and moved two drives to allow more space between them in the cage (slots 2 and 4). Unraid said it couldn't find a disk so I moved them both back and everything was fine. I just tried it again to try to test to see whether or not the slot was bad. Unraid finds the disk but it has a red ball next to it. I don't see anything in the log indicating an error. I'm doing a SMART (long) check now to see if I can find something wrong with it. Curious to know what to do if SMART is good to go. I think I'll do the file system check next but I'm not sure. I don't understand why it threw the error at this point.
May 15, 201511 yr A red ball means unRAID has disabled the drive because a write to it failed. It is now simulating the drive by calculating its data from all other array drives including parity. The only way to clear a red ball is to rebuild or do a new config. Rebuild is the the recommended method since the data on the drive is not trustworthy. You say you were experimenting. Do you have any important data on the drives, or is it just test data?
May 15, 201511 yr Author It's data that I can find again but not something I really want to lose. I was just moving drives around to test to make sure each slot was working. I'll let the SMART finish. After that I'm not sure how to do a rebuild. I assume it restores what's meant to be on the disk from parody?
May 15, 201511 yr It's data that I can find again but not something I really want to lose. I was just moving drives around to test to make sure each slot was working. I'll let the SMART finish. After that I'm not sure how to do a rebuild. I assume it restores what's meant to be on the disk from parody? Since you said parody twice now I was wondering if you thought that was the right word but looking at your post history I see you have used parity so I guess just a typo. I certainly make my share of typos I've learned. See this wiki for a better understanding of how parity works. Did you preclear any of your drives before trying to use them in unRAID? It is important to know if all of the drives in the array can be trusted because they are all needed when a drive fails. It requires parity plus all of the other array drives to rebuild a drive. The best way to do it is to rebuild onto a new drive. This has the advantage of keeping the failed drive intact in case there is a problem rebuilding, and allows you to determine later whether the failed drive can be trusted again. The next best way is to rebuild onto the same drive. Do you have a spare drive to rebuild to? You can only rebuild onto a drive that is the same size or larger than the original disk, but not larger than the parity disk.
May 15, 201511 yr Author Autocorrect decided parody was the right word. lol. I don't have a spare drive. I did do the preclear and I've only been running these drives for about 6 months.
May 15, 201511 yr Author Attaching the syslog. Drive ending in 29FE is the one having a problem. New_Text_Document.txt
May 15, 201511 yr Author Statistics for /dev/sdc ST4000DM000-1F2168_Z30129FE smartctl -a -d ata /dev/sdc smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z30129FE LU WWN Device Id: 5 000c50 0653aa24e Firmware Version: CC52 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 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.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri May 15 09:58:04 2015 EDT 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: ( 592) 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: ( 515) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) 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 118 099 006 Pre-fail Always - 193614888 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 416 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1328956 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5297 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 37 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 095 095 000 Old_age Always - 5 190 Airflow_Temperature_Cel 0x0022 073 050 045 Old_age Always - 27 (Min/Max 26/31) 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 - 22 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 3966 194 Temperature_Celsius 0x0022 027 050 000 Old_age Always - 27 (0 4 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 362h+44m+36.334s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 9413858984 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 88209679391 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 5295 - # 2 Extended offline Completed without error 00% 5291 - 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.
May 15, 201511 yr You said 29FE, which looks like a 4TB Seagate Barracuda, but you posted the SMART for a 150GB WD Raptor. Your original post is a little unclear about what exactly you have been doing. In particular I am not sure what you mean by offline. Before plugging or unplugging SATA disks in unRAID, I recommend you stop the array, then shutdown. While it may be possible to hot plug by stopping the array only, that is not really supported and has inconsistent results. Also, you should always stop the array before shutting down or rebooting. If you don't you will always get a correcting parity check the next time you boot. The syslog doesn't really tell us anything about how you got to the red ball. If you have rebooted since you got it then that is why. The syslog is in RAM and doesn't survive a reboot. The unRAID OS files are all in RAM like many "embedded" devices and unpacked fresh from your flash drive on each boot. I would still like to see the SMART for the red ball before proceeding, especially since this syslog does not tell me anything about it.
May 15, 201511 yr Author I was only stopping the array, not shutting down. I posted the status for the redballed drive. Thanks for your help, I appreciate it!
May 15, 201511 yr I was only stopping the array, not shutting down. I posted the status for the redballed drive. Thanks for your help, I appreciate it! I would not recommend experimenting with hotswap, especially with array disks.
May 15, 201511 yr The SMART report looks OK. Could you post a screenshot so I can more easily tell what your current array configuration is?
May 15, 201511 yr There is also an entry in the syslog regarding the flash drive. Shut down unRAID, pull the flash drive, attach to a Windows computer, and run a chkdsk.
May 15, 201511 yr Author I've definitely learned my lesson. I thought they were hot-swappable. No worries, shutting down and booting only takes a few minutes and will potentially save hours.
May 15, 201511 yr To rebuild onto the same drive: Stop the array and unassign the disk. Start the array. Disk should show as missing. Stop the array and reassign the disk. Start the array and rebuild.
May 15, 201511 yr Author Rebuild in progress. All of these drives were purchased about 6 months ago. I'm sure it was my own ignorance that caused this due to hot-swapping.
May 15, 201511 yr Author Is it rebuilding just the data on the drive or the free space too? I only had about 1tb of data on it and it's currently 1.6Tb done with 272 min remaining.
May 15, 201511 yr Is it rebuilding just the data on the drive or the free space too? I only had about 1tb of data on it and it's currently 1.6Tb done with 272 min remaining. Rebuild is the whole disk. It doesn't even know there are files on there. See the wiki link I posted in my first reply to you.
May 16, 201511 yr Author rebuild is done. It wanted to do a parity check so we're doing that now this morning. HDD is greenballed now anyway so that's good.
May 16, 201511 yr rebuild is done. It wanted to do a parity check so we're doing that now this morning. HDD is greenballed now anyway so that's good. Great! Yes, you should always do a parity check after a data or parity rebuild.
May 16, 201511 yr Author If nothing else, this has been a good learning experience. Not sure why the red ball happened but I'm sure it's got something to do with the hot-swapping.
May 18, 201511 yr Author Done. All is well, no errors or anything else wonky. I shut the machine down, reorganized the drives, booted it and everything's green. Thanks a ton for the help Trurl.
Archived
This topic is now archived and is closed to further replies.