Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Drive failing, now what?

Featured Replies

While on our honeymoon, I think one of my drives decided to fail about five days ago. I didn't notice it until tonight when we got home and fired up the media center to watch a TV show that I recently added to my server. The media player application froze, I checked unRAID webgui, and noticed the red ball. unMENU reports DISK_DSBL.

 

1. Syslog is here.

2. HDParm doesn't report anything - it's blank when I click the button. Works normally and shows results for the other drives.

3. SmartStatus report returns "Smartctl open device: /dev/sde failed: No such file or directory"

4. The machine did a monthly parity check on the first with no issues.

 

The drive in question is in an external eSATA port multiplier enclosure. I haven't power cycled the entire setup, because I wanted to be sure I did the right thing first. I have a feeling it's just a failed drive, but I just need a little guidance on how I should proceed.

 

After doing some research, I think my course of actions might be:

1. Attempt a complete power cycle

2. Test and reconnect power and data cables to drive in question

3. Replace drive

 

Thanks!

While on our honeymoon, I think one of my drives decided to fail about five days ago. I didn't notice it until tonight when we got home and fired up the media center to watch a TV show that I recently added to my server. The media player application froze, I checked unRAID webgui, and noticed the red ball. unMENU reports DISK_DSBL.

Congratulations on the recent wedding.

After doing some research, I think my course of actions might be:

1. Attempt a complete power cycle

2. Test and reconnect power and data cables to drive in question

3. Replace drive

 

Thanks!

You did your research well.

Yeah I think the first thing honestly I would ever do is power off the machine and then test any of my cables as the very first measure. If a cable is remotely suspect I'd swap it with another cable or use another drives cable as a last resort in a pinch. If another drive shows up as a problem then Its a pretty good guess that its the cable.

 

Congrats on the new wedding too.  ;D

  • Author

I power cycled, and reconnected cabling. The drive still shows as a red ball, however it's responding to HDParm:

 

/dev/sde:

ATA device, with non-removable media
Model Number:       WDC WD5000AAKS-22YGA0                   
Serial Number:      WD-WCAS83078127
Firmware Revision:  12.01C02
Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
Supported: 8 7 6 5 
Likely used: 8
Configuration:
Logical		max	current
cylinders	16383	16383
heads		16	16
sectors/track	63	63
--
CHS current addressable sectors:   16514064
LBA    user addressable sectors:  268435455
LBA48  user addressable sectors:  976773168
device size with M = 1024*1024:      476940 MBytes
device size with M = 1000*1000:      500107 MBytes (500 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16	Current = 0
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6 
     Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4 
     Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
Enabled	Supported:
   *	SMART feature set
    	Security Mode feature set
   *	Power Management feature set
   *	Write cache
   *	Look-ahead
   *	Host Protected Area feature set
   *	WRITE_BUFFER command
   *	READ_BUFFER command
   *	NOP cmd
   *	DOWNLOAD_MICROCODE
    	Power-Up In Standby feature set
   *	SET_FEATURES required to spinup after power up
    	SET_MAX security extension
    	Automatic Acoustic Management feature set
   *	48-bit Address feature set
   *	Device Configuration Overlay feature set
   *	Mandatory FLUSH_CACHE
   *	FLUSH_CACHE_EXT
   *	SMART error logging
   *	SMART self-test
   *	General Purpose Logging feature set
   *	64-bit World wide name
   *	Segmented DOWNLOAD_MICROCODE
   *	SATA-I signaling speed (1.5Gb/s)
   *	SATA-II signaling speed (3.0Gb/s)
   *	Native Command Queueing (NCQ)
   *	Host-initiated interface power management
   *	Phy event counters
    	DMA Setup Auto-Activate optimization
   *	Software settings preservation
   *	SMART Command Transport (SCT) feature set
   *	SCT Long Sector Access (AC1)
   *	SCT LBA Segment Access (AC2)
   *	SCT Error Recovery Control (AC3)
   *	SCT Features Control (AC4)
   *	SCT Data Tables (AC5)
    	unknown 206[12] (vendor specific)
    	unknown 206[13] (vendor specific)
Security: 
Master password revision code = 65534
	supported
not	enabled
not	locked
not	frozen
not	expired: security count
	supported: enhanced erase
134min for SECURITY ERASE UNIT. 134min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee25628273a
NAA		: 5
IEEE OUI	: 14ee
Unique ID	: 25628273a
Checksum: correct

 

And it's responding to Smart Status:

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Second Generation Serial ATA family
Device Model:     WDC WD5000AAKS-22YGA0
Serial Number:    WD-WCAS83078127
Firmware Version: 12.01C02
User Capacity:    500,107,862,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:    Fri Jul  9 08:43:02 2010 GMT+7
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: 		 (13200) 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: 	 ( 154) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x303f)	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     0x000f   200   200   051    Pre-fail  Always       -       0
 3 Spin_Up_Time            0x0003   176   174   021    Pre-fail  Always       -       6191
 4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       5078
 5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
 7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0
 9 Power_On_Hours          0x0032   076   076   000    Old_age   Always       -       18004
10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       165
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       126
193 Load_Cycle_Count        0x0032   199   199   000    Old_age   Always       -       5139
194 Temperature_Celsius     0x0022   117   067   000    Old_age   Always       -       33
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       42
200 Multi_Zone_Error_Rate   0x0008   200   200   051    Old_age   Offline      -       0

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]


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.

Then, odds are it failed at some point (power glitch?)

 

It will not re-enable itself.  Remember, a "write" to it failed, and that is why it was taken off-line.

 

You must now:

1. Stop the array

2. Un-assign the failed drive

3. Start the array with it un-assigned  (this will cause unRAID to forget its model/serial number)

4. Stop the array once more.

5. Re-Assign the failed drive  (Since unRAID has forgotten its model/serial number, it will think of it as a replacement for the failed drive)

6. Start the array by pressing "Start" 

 

unRAID will re-construct the contents of the drive onto itself, including anything that could not be written when it was originally taken out of service.

 

If you are using any version of unRAID prior to 4.5.6, DO NOT, DO NOT , DO NOT press the button labeled as "restore" as it is actually an "Initialize Disk Configuration and Immediately Invalidate Parity" button.  It is NOT what you want to do in this situation.  It has nothing to do with re-constructing a failed drive.

 

Joe L.

  • Author

Joe, thanks for your confirmation on the steps I should follow. I had read some of your prior advice to others in a similar situation, and I've already followed the steps you've presented.

 

And yes, I'm using pre 4.5.6, but I'm quite aware about the "restore" label being very ambiguous. Your constant warnings on the forums have kept that always in the back of my brain. Once I'm out of this quagmire, I'm going to update to 4.5.6.

 

2.5% done rebuilding. So far no errors. Crossing my fingers that everything goes smoothly.

  • Author

Rebuild went smoothly and it looks like I'm back up and running. I'm not sure what caused the hiccup, but I'm back up and running. Thanks for your help, Joe.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.