• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

DISK Errors OpenIndiana + Napp-it

Y

Yagobg

n00b
Joined
Feb 3, 2012
Messages
7
Hi all,

Have a server with about ten 2T drives and it works grate. However, this morning I was checking the system and found some disk errors via the Napp-it GUI. DISK -> Details.
One of the drives had "Error: S:0 H:245 T:409". Found couple of posts saying that those can be ignored and cleared. However, this is a productive NAS and can't afford any data loss so I got a new drive and replaced the one with the errors. Resilvering now.

Anyway, Can somebody explain what kind of errors are those and can they be ignored. For the 10 hours I was monitoring it they didn't increment. Also if I do zpool status I don't get any Read Write or Checksum errors. I didn't notice any performance issues. The only thing I can recall for the last month was that scrub will always report " scrub repaired 29k in xxxx with 0 errors".

Since I have the presumably bad drive out of the system will check it tomorrow and see if the manufacture software detects any errors.

Thanks for your help.
 
These iostat error messages can mean a possible future disk problem or other problems (ex bad cable, power)
or some transport failures that can be ignored
more https://blogs.oracle.com/chrisg/entry/iostat_e_whats_that_all

Checking the disk with a manufacturers tool is an option.
More important is to be prepared for a real disk failure with the help
of redundancy and hot or cold spares
 
_Gea said:
These iostat error messages can mean a possible future disk problem or other problems (ex bad cable, power)
or some transport failures that can be ignored
more https://blogs.oracle.com/chrisg/entry/iostat_e_whats_that_all

Checking the disk with a manufacturers tool is an option.
More important is to be prepared for a real disk failure with the help
of redundancy and hot or cold spares
Click to expand...


Thanks for the response _Gea.
So I'm on the right track if it is a (bad cable or power issue) should have errors on the new drive. Also will check the old drive. I'm suspecting it is the old HD due to it being a Green WD ears drive and it has been in 24/7 use for the last year.
Again thanks for your help
 
How many actual errors were there ?

Note that running smartctl against drives will increment the hardware error count for the drives as well. This is a known issue.

Also, in almost all cases there will be a corresponding entry in /var/adm/messages when a disk error is logged. You can examine that file as well to determine if it was merely a recoverable error as a result of smartctl.
 
I already exchanged the suspected drive with new Hitachi. I did test the drive with the manufacture diagnostic software (I want to make sure if I send it back they would exchange it not low format it and send it back). The first test it came with bad sectors so did a full low format and on the second run it came back all good. However, I'm scared to put the drive back in production and WD will not exchange the drive so just going to eat it. Thinking of attaching it to a testing system and do a script of constant writes and deletes for 24 hours and then check it again. Any ideas ?

Thanks for the help
 
That sounds like a simple sector remapping issue. My wd's I noticed really need to be forced to make them remap, and untill they remap it, you keep getting errors, but afterwards it should be ok.
 
You must log in or register to reply here.
Back
Top