I'm currently running v4.7.  Yesterday my unRAID server was hung so I had to do a hard reboot, so obviously a parity checked started when I started the system back up.  Well not only are several errors coming through, but the parity check is going EXTREMELY slow.  A parity check typically takes about 8 hours on my system.  Well the parity check has been going for about 12 hours now and it's only 15.6% complete.

 

I also have unMenu installed.  Was thinking I should also run a smart report, but was afraid to do that while a parity check was in progress.  I've attached my syslog.

syslog-2012-03-12.txt

Here is a screen cap of my setup, in case it helps.

Can you post smart reports. Disk1 might cause some problems.

Is it okay to do that while the parity check is running?

Is it okay to do that while the parity check is running?

yes

I just ran a Short Smart Disk on that Disk1 that seemed to be getting all the errors.

 

Statistics for /dev/sdd 00R6B0_WD-WCAVY1327176
smartctl -a -d ata /dev/sdd
smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EADS-00R6B0
Serial Number:    WD-WCAVY1327176
Firmware Version: 01.00A01
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:  Exact ATA specification draft version not indicated
Local Time is:    Mon Mar 12 16:46:02 2012 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:  (0x85)	Offline data collection activity
				was aborted by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (  39)	The self-test routine was interrupted
				by the host with a hard or soft reset.
Total time to complete Offline 
data collection: 		 (40800) 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: 	       (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     0x002f   200   200   051    Pre-fail  Always       -       135513
  3 Spin_Up_Time            0x0027   149   140   021    Pre-fail  Always       -       9508
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1474
  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   074   074   000    Old_age   Always       -       19474
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       164
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       116
193 Load_Cycle_Count        0x0032   164   164   000    Old_age   Always       -       110689
194 Temperature_Celsius     0x0022   111   102   000    Old_age   Always       -       41
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   196   196   000    Old_age   Always       -       1429
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   174   174   000    Old_age   Offline      -       5274

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       Interrupted (host reset)      70%     19474         -

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.

Replace the drive a.s.a.p.  The drive has way too many pending sectors.

I'd run pre-clear on that disk first and the then check the the SMART report. The pending sectors may resolve without reallocation. There may be another problem with the server.

I'm at a loss on what to do.  I just checked the WD website and that drive is still covered under warranty, so I guess I will just have them send me a new one.

 

I'm hesitant to do a preclear on the drive because every time I've had complete hard drive failures in unRaid, I've lost data.

 

The server is all but unusable at this point due to the performance, even if I cancel the parity check.

 

Since at this rate a full parity check won't complete for weeks, am I at risk of losing data on that disk when I replace it?

RMA it. It's safest to turn the system off until the disk is replaced.

Does the parity check show any errors that are being corrected?

 

I personally would just stop the parity check.

 

The log is strange. It shows a bunch of errors that look like disk read errors and then a bunch that look like a SATA connection error.

I have a new drive on the way from WD.

 

So is there anything I can do to minimize data loss?  If I lose any data from the bad drive, I assume the data should at least be retrievable off of the bad drive?

 

I noticed in another thread (http://lime-technology.com/forum/index.php?topic=18228.msg163460#msg163460) a user was getting the same error messages that I'm getting (handle_stripe read error), but in their case it was on the PARITY drive, which is not the case for me.  In that thread, Joe L suggested - "Best bet is to stop the arraay, un-assign the parity disk, start the array with it un-assigned, stop the array once more, re-assign the parity disk, and let unRAID re-construct it.  If it successfully re-allocates the sectors pending re-allocation, then just keep an eye on it."  Is there anything similar to that I could try?  At this point it seems parity will never finish.  It's now at 35% and it's been 2 days and seems to be going slower as it goes.  It does indicate 23 sync errors have been corrected, but the drive itself shows 3,000+ errors.

There should be no data loss. Start the array without the bad disk and its contents will be simulated by unRAID. It's best not to run in this degraded mode because a second disk failure will cause data loss. Once the replacement is installed and assigned to the correct slot the contents will be restored.

Thanks dgaschk, that's encouraging.  I guess my worry is that I won't be able to get a good parity check in before swapping in the new drive.

Do a parity check after the rebuild. Not before.