Hi all,

 

I have a drive with some errors. Let me explain a bit how it happened, I decided that now would be a good time to start some upgrades on my server. First thing I wanted to do was to switch over to xfs.

 

My server is <50% compacity, I decided I would remove several drives which were empty, preclear them, format as xfs and copy the entire array to them. The advantage being that if something went wrong, I still had the parity and data in the reiserfs drives.

 

I rsynced the data over and everything seemed ok, no errors. I didn't add a parity drive at this point so that the copying was quicker. Then I did a parity sync, now one of the drives shows 320 errors. See attached report.

 

I assume these errors occurred during the parity sync and so the parity isn't correct and that data on this drive is no good. But the drive has not red balled.

 

What would be the next course of action? Would you replace that drive? Since I still have a  copy of the data and the old parity, I can always copy the data back.

 

I've attached my syslog and smart reports.

tower-syslog-20160118-2113.zip

tower-smart-20160118-2114.zip

Disk has pending sectors and should be replaced, since both its data and the new parity can't be trusted I would copy data from the old disks to the replacement.

Disk has pending sectors and should be replaced, since both its data and the new parity can't be trusted I would copy data from the old disks to the replacement.

 

Thanks, that's what I thought too, I've never have gotten any errors on my drives before so I wanted to double check before I binned it. I got a new drive on the way and I'm going to copy back from the original.

Disk has pending sectors and should be replaced, since both its data and the new parity can't be trusted I would copy data from the old disks to the replacement.

 

Thanks, that's what I thought too, I've never have gotten any errors on my drives before so I wanted to double check before I binned it. I got a new drive on the way and I'm going to copy back from the original.

 

When you replace a disk in the array, then unRAID will rebuild the content for that drive. You don't need to copy anything yourself. Just keep the original drive handy in case of issues.