I tried replacing an old 250 gig drive with a somewhat newer 1 gig that I had laying around. I ran the expander and the disk is disabled due to write errors. Then I tried reverting back to the old disk, but it wont let me due to the disk needing to be equal or bigger. I attached  the smart log for the drive. I had just removed all the data from the 1 gig western digital drive.

Thanks in advance for the help

syslog.txt

I tried replacing an old 250 gig drive with a somewhat newer 1 gig that I had laying around. I run the expander and the disk is disabled due to write errors. Then I tried reverting back to the old disk, but it wont let me due to the disk needing to be equal or bigger. I attached  the smart log for the drive. I had just removed all the data from the 1 gig western digital drive.

Thanks in advance for the help

Did you, by any chance, save a copy of your config folder before you made the change in disks?

 

How much did you "write" to the array before the "write" failures occurred?

 

You did not post a full syslog... how many disks do you have in the array? 

 

Do you have a parity disk assigned?

 

Unfortunately I didn't save the config file. I didn't write anything to the drives, but it was building from parity not even a couple of minutes.

Unfortunately I didn't save the config file. I didn't write anything to the drives, but it was building from parity not even a couple of minutes.

If you did not write anything to the array at all you can use the trust my parity procedure to have unRAID rebuild a new super.dat and "trust" that parity is good.

 

It will accept the original drive that you've put back where it was in the array.

 

The procedure is described here in the wiki:

http://lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily

 

Make sure you let the parity check that will occur when you re-start the array complete.

 

What version of unRAID are you using?

 

Joe L.

 

I'm using 4.7. I have 2 samsung 2 tb drives with the updated firmware. I's that 1 tb drive bad? Would I be better trying to send back the Wd it's less than 2 years old.

I'm using 4.7. I have 2 samsung 2 tb drives with the updated firmware. I's that 1 tb drive bad? Would I be better trying to send back the Wd it's less than 2 years old.

The errors were all CRC errors.  (checksum errors in communicatig with the drive)

I'd suspect the SATA cable first.  Then the disk controller port if you've tried several disks and they all fail on the same port.

Okay parity check is running . Thanks Joe . Gonna try another port for the western digital once parity check is complete. Is there a way to avoid the problem I had if the drive fails again?