June 1, 201313 yr Hi When I tried to stop my array a moment ago my Unraid server stopt reacting. I couldn't access my server anymore and I had to force shutdown my server. After reboot I have now a red dot with a HD. That HD used to be my parity but about a month or two ago I changed that parity with another one because I wanted to add a 3 TB disc. That operation went without problems. This disc with the error is an Green WD 2 TB disc. When I go to my server I can still see that disc and I can still access it. I can also open a file that is on that disc. The disc itself is my first disc that I have added to my Supermicro AOC-SAS2LP-MV8 card. My other disc's are in my system via my motherboard. Does anybody have an idea what the problem could be? The Smart status report for that disc: Statistics for /dev/sdf WDC_WD20EARS-00MVWB0_WD-WCAZA6222259 smartctl -a -d ata /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA6222259 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jun 1 11:43:12 2013 CEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (37560) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) 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 187 165 021 Pre-fail Always - 5616 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 748 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14024 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 - 33 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 16646 194 Temperature_Celsius 0x0022 114 100 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 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 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% 14023 - # 2 Short offline Completed without error 00% 14023 - # 3 Extended offline Aborted by host 90% 14023 - # 4 Short offline Completed without error 00% 14023 - 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.
June 1, 201313 yr After reboot I have now a red dot with a HD. That HD used to be my parity but about a month or two ago I changed that parity with another one because I wanted to add a 3 TB disc. That operation went without problems. The red dot means it's marked as a failed disc, so is no longer in use by UnRAID. The SMART data shows some pending reallocations, and also has a few power-off retractions ... meaning it lost power unexpectedly and retracted the heads. I'd replace the drive and let the system rebuild it. This disc with the error is an Green WD 2 TB disc. When I go to my server I can still see that disc and I can still access it. I can also open a file that is on that disc. This is normal. You're not actually accessing the disc => the data is being reconstructed by reading the other discs plus parity and recreating the data for that disc. That's what fault-tolerance is all about
June 1, 201313 yr Just noticed your title ... "DISK_DSBL" => is the GUI showing that as the status? If that's the case, it doesn't think the drive is present. Before doing anything else, shut down and double-check the cables to the disk (data and power) ... then boot back up. There's a chance it may come back online, although I'm not sure what will happen since it's got pending reallocations. [These need to be cleared]
June 1, 201313 yr Author The GUI is showing this as status. I have just done a reboot. Still a red dot in the GUI. In Main I have the error code DISK_DSBL. So I suppose this disc is failing. Do I just take at the disc and put in a new? Or do I first put in a new disc and let unraid move the data to the new disc? I just bought a new WD RED disc from 3TB yesterday. Was planning on adding it today when I noticed that red dot in my system. That dot wasn't there yesterday. Thx for the help already
June 1, 201313 yr The GUI is showing this as status. I have just done a reboot. Still a red dot in the GUI. In Main I have the error code DISK_DSBL. So I suppose this disc is failing. Do I just take at the disc and put in a new? Or do I first put in a new disc and let unraid move the data to the new disc? I just bought a new WD RED disc from 3TB yesterday. Was planning on adding it today when I noticed that red dot in my system. That dot wasn't there yesterday. Thx for the help already You indicated your parity replacement went well last month -- have you done a recent parity check? ... and did it show everything was okay (0 sync errors)? As long as you have good parity, I'd just replace the drive and let it rebuild. You can NOT do another parity check now, so if you don't have good parity you're going to have to do this differently. ... but as long as parity is good, just replace the drive and let it rebuild. May as well use a nice new 3TB drive while you're doing it
June 1, 201313 yr Author Last parity check is 70 days ago. 0 sync errors. So I just take out the disc and let it rebuild.
June 1, 201313 yr Last parity check is 70 days ago. 0 sync errors. So I just take out the disc and let it rebuild. Yep ... just shut down; replace the disk with a nice new one; and power it back up. When you Start the array, it will start the rebuild.
June 1, 201313 yr Author Disc replaced. Rebuilding as we speak... 920 minutes left... Thx for the help!
June 1, 201313 yr After the rebuild is finished and your system is back to normal you might want to do some further testing on the drive you replaced. A long Smartctl test would be good and if it passes run Preclear on it a few times. You might find you have a usable spare. Going back through your saved Syslogs can help isolate why unRAID disabled the disk. Good luck with the rebuild!
June 1, 201313 yr Just noticed your title ... "DISK_DSBL" => is the GUI showing that as the status? If that's the case, it doesn't think the drive is present. No,that would be DISK_DSBL_NP (not present) DISK_DSBL indicates the disk was disabled because a WRITE to it failed. Before doing anything else, shut down and double-check the cables to the disk (data and power) ... then boot back up. There's a chance it may come back onlineNo, it will NEVER restore itself., although I'm not sure what will happen since it's got pending reallocations. [These need to be cleared] All that needs to happen, assuming re-seating the cables fixes the issue it to STOP THE ARRAY Un-ASSIGN THE DISABLED DISK START THE ARRAY WITH IT UN_ASSIGNED (this causes unRAID to forget the model/serial number of the disk) STOP THE ARRAY ONCE MORE RE-ASSIGN THE DISK START THE ARRAY ONCE MORE AND THE DISK WILL RE_CONSTRUCT ONTO ITSELF. Joe L.
June 1, 201313 yr I don't want to hijack this thread but I have a related question. If I replace that bad drive for a bigger one will unRAID rebuild the data?
June 1, 201313 yr I don't want to hijack this thread but I have a related question. If I replace that bad drive for a bigger one will unRAID rebuild the data? yes
June 1, 201313 yr If I replace that bad drive for a bigger one will unRAID rebuild the data? As Joe noted, Yes. But in fact it doesn't even have to be bad ==> you can replace any drive with a larger drive and it will rebuild. The only restriction is that you can't use a drive larger than your parity drive -- so if you want to "grow" your array this way, the first thing you'd typically do is replace the parity drive with a larger drive (e.g. with currently available drives, if you were replacing the parity drive you'd probably want to use a 4TB drive).
June 2, 201313 yr Author Just noticed your title ... "DISK_DSBL" => is the GUI showing that as the status? If that's the case, it doesn't think the drive is present. No,that would be DISK_DSBL_NP (not present) DISK_DSBL indicates the disk was disabled because a WRITE to it failed. Before doing anything else, shut down and double-check the cables to the disk (data and power) ... then boot back up. There's a chance it may come back onlineNo, it will NEVER restore itself., although I'm not sure what will happen since it's got pending reallocations. [These need to be cleared] All that needs to happen, assuming re-seating the cables fixes the issue it to STOP THE ARRAY Un-ASSIGN THE DISABLED DISK START THE ARRAY WITH IT UN_ASSIGNED (this causes unRAID to forget the model/serial number of the disk) STOP THE ARRAY ONCE MORE RE-ASSIGN THE DISK START THE ARRAY ONCE MORE AND THE DISK WILL RE_CONSTRUCT ONTO ITSELF. Joe L. Hmm. Thx for the tip but I already used the other method... My unraid is rebuild and I haven't lost any data. I'm doing a parity check now. When the parity check is finished I will put the disc I have taken out back into the system and see if it still works.
Archived
This topic is now archived and is closed to further replies.