Hey all

 

I just had a disk give me errors in a parity check.

did another parity check and all fine.

then did a long smart check as per this post http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_media_issue_.231

the long smart test gave me a finish time and now i am posting everything but if i read the smart.txt it says in there "Self-test execution status:      ( 242) Self-test routine in progress...

20% of test remaining."

 

so i am now not sure what my next step is...

 

please find attached my syslog files for after the first parity check and then after the second parity check and also the smart.txt generated AFTER the time given to me by the console when i ran the test [i gave it 10 mins after the time specified by smartctl]

 

any help would be GREATLY appreciated

 

thanks

 

syslog.after.1st.parity.check.txt

syslog.after.2nd.parity.check.txt

smart.txt

There must be a mistake: Apart from a few lines at the end the log files are identical!

 

 

from your syslog it looks like disk2 had read errors, so im assuming you are seeing in the errors column next to disk2 a non zero number yes?.

 

just to confirm your seeing 0 errors for the parity check, just errors for disk2?

 

unraid will actually automatically remap data by writing the data back to the disk using the other disks and parity drive so its very possible your drive has had the bad blocks written back, taken from the unraid wiki:-

 

Occasionally unRAID will encounter a READ error (not a WRITE error) on a disk. When this happens, unRAID will read the corresponding sector contents of all the other disks + parity to compute the data it was unable to read from the source. It will then WRITE that data back to the source drive. Without going into the technical details, this allows the source drive to fix the bad sector so next time, a read of that sector will be fine. Although this will be reported as an "error", the error has actually been corrected already. This is one of the best and least understood features of unRAID!

 

so keep and eye on that disk, if you start seeing more errors then the drive could be on its way out, so replace asap. looking at your smart report the drive looks fine, it has no re-allocated sectors and none pending, so it has no issues with writing at the moment

there is no mistake, it was done like this to show that there was no hardware errors after the first parity check

there is no mistake

OK, I see (pretty quiet during the second parity check)

 

SMART looks good. Luckily you have unRAID and the parity.

As explained by binhex, the unreadable sectors have been rewritten from parity information.

 

For your information:

A friend of mine had 2 WD drives (1,5TB greens) in an external enclosure.

Just a few days ago he got himself a NAS and he copied the movies from those drives.

In the process he ended up with lots of unreadable files. Many of his stored movies are gone now. (I will try to ddrescue them)

 

One of mine 1,5TB WD drives died a few months ago during preclearing.

Reported bad sectors during 1st and 2nd preclear and during the 3rd preclear

it stopped responding.

Probing it with the WD diagnostic tool reported "drive failure".

 

This draws a bad picture of WD drives.

Imagine your second drive also reports bad sectors at the same location...bad luck!

Furthermore, it's questioning the practice of storing backups on standalone drives (like many do). 

 

its a sad situation we are in fireball3, but really there is only WD or seagate now left in the HD market :-(, i used to swear by ibm, hitachi and samsung HD, none of which are now available to buy, so been forced to buy WD as i just dont rate seagate.

from your syslog it looks like disk2 had read errors, so im assuming you are seeing in the errors column next to disk2 a non zero number yes?.

 

just to confirm your seeing 0 errors for the parity check, just errors for disk2?

 

unraid will actually automatically remap data by writing the data back to the disk using the other disks and parity drive so its very possible your drive has had the bad blocks written back, taken from the unraid wiki:-

 

Occasionally unRAID will encounter a READ error (not a WRITE error) on a disk. When this happens, unRAID will read the corresponding sector contents of all the other disks + parity to compute the data it was unable to read from the source. It will then WRITE that data back to the source drive. Without going into the technical details, this allows the source drive to fix the bad sector so next time, a read of that sector will be fine. Although this will be reported as an "error", the error has actually been corrected already. This is one of the best and least understood features of unRAID!

 

so keep and eye on that disk, if you start seeing more errors then the drive could be on its way out, so replace asap. looking at your smart report the drive looks fine, it has no re-allocated sectors and none pending.

 

thanks

I was looking for confirmation like this

my thinking was the same clear all errors and keep a close watch for more..

my main reason for this post was ALWAYS make sure clean parity and no errors before moving versions and i want to go from 5.0 to 5.0.3 ....so would you?

I did. No problems with 5.0.3

 

But I read a thread where a guy reported problems with the new Realtek NIC driver.

So if you have such a NIC, better postpone it or prepare to revert to 5.0 in case.

 

its a sad situation we are in fireball3, but really there is only WD or seagate now left in the HD market :-(, i used to swear by ibm, hitachi and samsung HD, none of which are now available to buy, so been forced to buy WD as i just dont rate seagate.

 

To be honest, in the distant past I used to stay very far away from Seagate and Maxtor drives.  Since I work in IT, I've just seen way too many of them fail compared to WD. But that all changed a few years ago IMHO. I've seen many a failed WD recently (especially the Greens) but very few failed Seagate drives. I have all Seagate in my array and couldn't be happier.  They have proved to be great drives.