I have. toshiba disk in my array that throws up reads errors every parity check or so.  My setup is dual parity so it makes sense to change Paroty 2 disk to an array disk, copy what I need to over and then pull the dodgy disk out.

 

What's the best sequence do this?  Stop array, remove P2 disk from config as a parity drive, preClear it, add, copy files and then pull out suspect drive?

 

Or pull both parity 2 and suspect drive out of the array, re-adding the P2 as a array disk and let the system preclear and rebuild on it's own?

 

Or just go back to bed and hope the hangover clears soon..

What I would do is buy a new disk same size as my parity drive(s). Preclear it. Replace dodgy disk and let dual parity restore its contents automagically.

...Or pull both parity 2 and suspect drive out of the array, re-adding the P2 as a array disk and let the system preclear and rebuild on it's own?...

This is close. Maybe what you meant is this:

Use P2 to replace the bad disk, then let unRAID rebuild the contents of the old bad array disk to the "new" (former P2) replacement array disk.

 

Like so:

Unassign P2.

Assign P2 disk to the slot formerly occupied by the bad disk.

Start will begin rebuild of data that was on the bad disk onto the former P2 disk.

 

This should work in principle, but I'm not entirely sure that unRAID won't want you to set a new config at some point to make it forget about P2 assignment.

 

Before doing anything though, post a diagnostic so we can see if we can determine the cause of the read errors.

 

And maybe johnnie.black will chime in with his own experiences (I wouldn't be at all surprised if he had some) with this particular scenario.

What I would do is buy a new disk same size as my parity drive(s). Preclear it. Replace dodgy disk and let dual parity restore its contents automagically.

 

I've decided I don't really need dual parity so I'll just redeploy what I have.  Means I save money and get it all done today.  Not sure I could buy a disk today.

 

This is close. Maybe what you meant is this:

Use P2 to replace the bad disk, then let unRAID rebuild the contents of the old bad array disk to the "new" (former P2) replacement array disk.

 

Like so:

Unassign P2.

Assign P2 disk to the slot formerly occupied by the bad disk.

Start will begin rebuild of data that was on the bad disk onto the former P2 disk.

 

This should work in principle, but I'm not entirely sure that unRAID won't want you to set a new config at some point to make it forget about P2 assignment.

 

Before doing anything though, post a diagnostic so we can see if we can determine the cause of the read errors.

 

And maybe johnnie.black will chime in with his own experiences (I wouldn't be at all surprised if he had some) with this particular scenario.

 

Thanks.  That sounds the easiest.

 

WRT logs I'll do a dump, but I'm convinced it's the drive stuttering when it gets too hot.  It only happens to the Toshi 4TB and only during parity checks.  I've changed cables, placing in the server case and even replaced the server case to a bigger cooler one.  The Toshi runs hotter than my other drives, all Seagates.  Being in the tropics means average disk temps are in he low 40s.  Parity checks will push the seagates to high 40s now.  The Toshiba crosses over to 50c

Like so:

Unassign P2.

Assign P2 disk to the slot formerly occupied by the bad disk.

Start will begin rebuild of data that was on the bad disk onto the former P2 disk.

 

IIRC this won't work, but it will with 2 extra steps:

 

Unassign P2.

Start array

Stop array

Assign P2 disk to the slot formerly occupied by the bad disk.

Start will begin rebuild of data that was on the bad disk onto the former P2 disk.