[SOLVED] Help please. Red balled drive replaced. Same failures.

[veemann]

Yes, any critical data is backed up.  This server is 99% home theatre/jukebox content and not an issue if something did happen but I understand what you mean.

Thanks,

V

[veemann]

I am ready to proceed on this if someone is willing to direct.

Thanks.

V

[trurl]

Do you have space on another computer or an external drive you can copy the data to? You said the emulated disk was browsable, so you should be able to just copy its data just as if it were a real disk.

[veemann]

Yes, already did that.

 

Do you have space on another computer or an external drive you can copy the data to? You said the emulated disk was browsable, so you should be able to just copy its data just as if it were a real disk.

[trurl]

OK. Disk9 files backed up. Disk9 still redball and all other drives green. Original Disk9 SMART OK. You can rebuild to the original disk 9.

 

[veemann]

Yes correct.  Ok will do but how do I get to reassign the slot with the original disk9?  It says not allowed because the replacement was larger.

BTW:  I noticed some peculiar behavior when I was transferring the data to the other computer.  I received quite a few errors that stated the file being transferred didn't exist.  Is this indicative of corruption in the parity?

Thanks.

V

 

OK. Disk9 files backed up. Disk9 still redball and all other drives green. Original Disk9 SMART OK. You can rebuild to the original disk 9.

[veemann]

I apologize it is not currently red balled it is unassigned.

 

Yes correct.  Ok will do but how do I get to reassign the slot with the original disk9?  It says not allowed because the replacement was larger.

BTW:  I noticed some peculiar behavior when I was transferring the data to the other computer.  I received quite a few errors that stated the file being transferred didn't exist.  Is this indicative of corruption in the parity?

Thanks.

V

 

OK. Disk9 files backed up. Disk9 still redball and all other drives green. Original Disk9 SMART OK. You can rebuild to the original disk 9.

[trurl]

I apologize it is not currently red balled it is unassigned.

 

Yes correct.  Ok will do but how do I get to reassign the slot with the original disk9?  It says not allowed because the replacement was larger.

BTW:  I noticed some peculiar behavior when I was transferring the data to the other computer.  I received quite a few errors that stated the file being transferred didn't exist.  Is this indicative of corruption in the parity?

Thanks.

V

 

OK. Disk9 files backed up. Disk9 still redball unassigned and all other drives green. Original Disk9 SMART OK. You can rebuild to the original disk 9.

Do you have another disk with good SMART as large as the one you tried before? If so it would be simpler to rebuild to that instead.

 

I wouldn't call it corruption in the parity but I wouldn't be surprised if there wasn't some corruption with the emulated filesystem. We may be able to fix that after the rebuild.

[veemann]

I have one on the way but not in hand.

 

[trurl]

I'll let you decide.

 

You can wait on the new disk, test it, have a simpler rebuild procedure, and wind up with more capacity than you had before.

 

Or you can try a somewhat more complicated rebuild procedure on the original disk, which you say failed before though it is not at all clear that the disk itself was at fault since its SMART looks OK.

 

 

[veemann]

That all makes sense to me.  I'll wait for the new.

Thanks for all your help so far, I appreciate it.

V

 

I'll let you decide.

 

You can wait on the new disk, test it, have a simpler rebuild procedure, and wind up with more capacity than you had before.

 

Or you can try a somewhat more complicated rebuild procedure on the original disk, which you say failed before though it is not at all clear that the disk itself was at fault since its SMART looks OK.

[veemann]

I have 2 drives preclearing and should be done soon.  Do I proceed by assigning one and go ahead with the new drive rebuild?

Thanks,

V

 

You can wait on the new disk, test it, have a simpler rebuild procedure, and wind up with more capacity than you had before.

[trurl]

Assign a new disk to the slot the failed disk was in then if you look at the Start button unRAID should tell you that starting the array will begin rebuild.

[veemann]

New pre-cleared disk is currently rebuilding.  After that is finished my intent is to start a parity check which is exactly the point my last 3 failures have occurred.

V

[veemann]

Disk9 is rebuilt green balled and running.  Now I would like to run a parity check as its been a long time since its been clear.  Do I initiate with 'write corrections to parity disk' checked or unchecked?

Thanks,

V

[trurl]

Disk9 is rebuilt green balled and running.  Now I would like to run a parity check as its been a long time since its been clear.  Do I initiate with 'write corrections to parity disk' checked or unchecked?

Thanks,

V

After a data disk rebuild is the one time it probably makes sense to do a non-correcting parity check. Then if there are any sync errors parity is still the same and you can decide to rebuild the data disk again.

[veemann]

Ok thanks.  So ordinarily the monthly checks would be correcting?

V

 

After a data disk rebuild is the one time it probably makes sense to do a non-correcting parity check. Then if there are any sync errors parity is still the same and you can decide to rebuild the data disk again.

[trurl]

Ok thanks.  So ordinarily the monthly checks would be correcting?

V

 

After a data disk rebuild is the one time it probably makes sense to do a non-correcting parity check. Then if there are any sync errors parity is still the same and you can decide to rebuild the data disk again.

There has been some debate about that but many would say that it is more likely that any sync errors are due to parity being wrong than any data disk being wrong, and since you can't identify the disk from a single parity bit anyway might as well correct parity. The only time I have ever had parity errors was due to an unclean shutdown, which is known to have the potential to make parity out-of-sync since parity writes may not have completed.

 

If you are ever in a situation (such as just after a data disk rebuild) where you aren't fully confident in a particular data disk, then it makes sense to do a non-correcting parity check.

[veemann]

Noted.

Thank you very much for all your help trurl.  It looks like everything is sorted and back to normal.  Though I just don't really know what happened to begin with.

I will be going through the original disk9 and seeing if I can find anything though I don't expect to.  As to the failed replacement, who knows what I'll do with that.... maybe target practice.

Thanks again,

V

[petjek]

Hi all,

 

I read all the thread here because I had quite the same problem with one of my drives. I replaced a 1TB drive after it showed 782 Errors with a bigger 3TB drive. Really needed some more space so it was an easy decision. After install I started a rebuild (didn't perform a preclear before) and everything seemed to be ok after a few hours. A week later all of a sudden there was an error message showing the same 782 Errors again. So I did some web research and finally found this thread.

First of all I copied all data from that drive to an external drive which took some time due to rebuilding data.

Today I wanted to continue by preclearing the drive and you can't imagine my amazement when unRAID told me the drive has returned to normal operation. What? How? Why?

And what shall I do now? Just ignore and return to normal operation, too? Or should I continue the preclear/rebuild process anyway?

 

.:Confused:.

 

Regards,

petjek

[trurl]

Hi all,

 

I read all the thread here because I had quite the same problem with one of my drives. I replaced a 1TB drive after it showed 782 Errors with a bigger 3TB drive. Really needed some more space so it was an easy decision. After install I started a rebuild (didn't perform a preclear before) and everything seemed to be ok after a few hours. A week later all of a sudden there was an error message showing the same 782 Errors again. So I did some web research and finally found this thread.

First of all I copied all data from that drive to an external drive which took some time due to rebuilding data.

Today I wanted to continue by preclearing the drive and you can't imagine my amazement when unRAID told me the drive has returned to normal operation. What? How? Why?

And what shall I do now? Just ignore and return to normal operation, too? Or should I continue the preclear/rebuild process anyway?

 

.:Confused:.

 

Regards,

petjek

What version of unRAID?

[petjek]

Sorry. It's 5.0.5

[trurl]

Sorry. It's 5.0.5

Post syslog and SMART for the drive in question.

[petjek]

OK, found syslog download in Utils -> System Log. See attachment

 

How to gain SMART data? Is this correct?

 

Model Family:     Western Digital Red (AF)
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WMC4N0F94WJX
LU WWN Device Id: 5 0014ee 65a58ca5b
Firmware Version: 82.00A82
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:    Wed Nov 23 14:49:24 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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   182   180   021    Pre-fail  Always       -       5866
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       36
  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   100   100   000    Old_age   Always       -       334
10 Spin_Retry_Count        0x0032   100   253   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       -       9
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       49
194 Temperature_Celsius     0x0022   131   106   000    Old_age   Always       -       19
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   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

pre>

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: 		(40020) 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: 	 ( 401) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       159    

No Errors Logged

 

syslog.zip

[trurl]

Drive looks OK. The syslog is mostly just

Nov 23 04:43:56 hightower avahi-daemon[6977]: Invalid response packet from host 192.168.10.59.
Nov 23 04:44:33 hightower avahi-daemon[6977]: Invalid response packet from host 192.168.10.103.

which is not about the disks and not really helpful. Your older syslogs are in /var/log if you can get them. They would have names like syslog.1 for example. See this sticky

 

There are a number of things in your original description that aren't entirely clear.

First of all I copied all data from that drive to an external drive which took some time due to rebuilding data.

Today I wanted to continue by preclearing the drive and you can't imagine my amazement when unRAID told me the drive has returned to normal operation. What? How? Why?

And what shall I do now? Just ignore and return to normal operation, too? Or should I continue the preclear/rebuild process anyway?

 

.:Confused:.

In particular, you can't preclear a drive that is part of the array, and you can't rebuild a drive that isn't part of the array. So I am confused too, but my confusion is about your description.

 

Maybe a screenshot would help.