This has happened to me twice. I've had two hard drives die in my unraid array. I'll then take those drives and stick them in my Windows computer(s), reformat them and use them with no problems. One drive has actually been in use for over 6 months now. And before I started to use them I did a sector by sector read/write/verify on each drive. I'll even try to install the drive again and unraid just doesn't like it. Soon as I install a new drive, it starts to rebuild and everything is fine. Has this ever happened to anyone? I'm curious as to what it could be. A little weird.

 

 

By the way, does anyone think if I upgrade my mainboard and add more memory (I have 8GB now) I will get better performance out of my system? I don't use a cache drive, I don't want to deal with it. You can see how old my mainboard is, it is in my signature. I'm also using that very popular Supermicro AOC-SASLP-MV8 8 port SATA card which has been great. You think if I upgrade the mainboard, add more memory and upgrade to 6Gbs it would perform better?

 

 

I see no reason to upgrade your motherboard/CPU/memory ... an E6750 is fine for UnRAID.  It's a lot more "horsepower" than I have in either of my servers.    And 8GB is plenty.

 

As for the drive issues -- UnRAID will disable and red-ball a drive anytime there's a single write error.    Have you tried simply Stopping the array; un-assigning the drive; Starting the array (so it shows as a missing drive); then Stopping it again, re-assigning the drive, and then letting it do the rebuild on the same drive?    If the issue was due to a write error, this will often result in the bad sector(s) being reallocated during the rebuild, and it will work fine.    I've seen this on a couple of different systems over the years.

 

I see no reason to upgrade your motherboard/CPU/memory ... an E6750 is fine for UnRAID.  It's a lot more "horsepower" than I have in either of my servers.    And 8GB is plenty.

 

As for the drive issues -- UnRAID will disable and red-ball a drive anytime there's a single write error.    Have you tried simply Stopping the array; un-assigning the drive; Starting the array (so it shows as a missing drive); then Stopping it again, re-assigning the drive, and then letting it do the rebuild on the same drive?    If the issue was due to a write error, this will often result in the bad sector(s) being reallocated during the rebuild, and it will work fine.    I've seen this on a couple of different systems over the years.

 

Yes, I did try all that. Unraid actaully wouldn't let me assign the drive back to where it was. In the end, I replaced the drive with an upgraded model anyway and have been using it in my Windows computer just fine. I did two sector by sector checks on it and both came out clean. I'm kind of glad you said don't worry about upgrading. I don't think I will. Thanks!