My parity drive did show 1,500 errors during a copy and was shown as bad by unRAID. Smartctl (see attachment) shows errors.

 

Now I read on Seagates site that I need to report an error number from their SeaTools. What should I say: All SeaTools tests show that this is a good drive.

 

Hmm, is this drive bad and can I RMA this drive even if SeaTools report a good drive?

 

Thanks in advance.

smartctl.txt

I've never been question by any major drive manufacturer r.e. whether or not a drive I returned was bad.    I'm simply filled out the form (online); and sent the drive in according to their instructions.  With Western Digital drives, I always use an Advance Replacement ... so they ship a replacement before I even return the old drive.    Seagate doesn't have this option, but nevertheless they're quite good at promptly replacing a drive.

 

If you simply fill out the online RMA form and return the drive per their instructions (just leave the SeaTools error code blank), I'm confident they'll replace it.

 

Note, however, that drives replaced under warranty are typically refurbished drives -- although they warrant them until the end of your original warranty period, so you don't lose any warranty time.

 

 

There are 8 sectors pending re-allocation.  They will be re-allocated the next time they are written.  The disk has a pool of several thousand spare sectors for just that purpose... that is why it is being reported as fine by seatools.    The current value for that parameter is 100, unchanged from the initial value set when the disk was manufactured.

 

Joe L.

Ah, I see. So I just put this drive back in,  unRAID "discovers" a new parity drive,  and I let unRAID do a parity check to record the new values?

 

When the errors popped up I did restart the machine and the parity drive had a blue icon after the restart.

 

My guess was that this drive must be bad but if SeaTools reports a good drive something else must been happened.

 

Thanks a lot.

 

After parity is written to the drive the Current_Pending_Sector RAW_VALUE should be zero. If it's not zero then the drive is having problems.

Ah, I see. So I just put this drive back in,  unRAID "discovers" a new parity drive,  and I let unRAID do a parity check to record the new values?

Actually, not a "check", but an initial parity "calculation".

When the errors popped up I did restart the machine and the parity drive had a blue icon after the restart.

If detected as new, the array must have been detected as "missing" (or unassigned) when the array was booted previously.

My guess was that this drive must be bad but if SeaTools reports a good drive something else must been happened.

Sounds more like an intermittent cable or drive tray connection to the disk.

 

Let the new parity calc complete, then do a parity CHECK.  AS mentioned, the number of sectors pending re-allocation should go to 0.