I have a red ball on one of my drives. It passes all the tests, even the long SMART tests. I also made sure the controller port is good by putting another drive on it. The drive is recognized on a Windows machine just fine. Can't read/write to it, but it is recognized. I also used Simple Features utility to check the drive and everything indicates the drive passed, etc...

 

Anyone know why unraid keeps putting this drive as disabled/red ball? Does that REALLOCATED SECTOR COUNT give me a bad drive? Why would all tests pass then if that is the issue? I'm a little confused.

 

Did you check the unRAID logs for errors?

Did you check the unRAID logs for errors?

 

I checked the syslog multiple times, and no errors. All general normal bootup stuff. It even "mounts" the drive.

/mnt/disk9

 

 

 

Attach a syslog that shows when the disk is disabled.

It passes all the tests, even the long SMART tests.

 

It's called the Lance Armstrong bug. 

Wild, wild SWAG!  Any possibility your power supply is marginal when attempting to spin up fourteen WD Black 7200rpm drives? 

Wild, wild SWAG!  Any possibility your power supply is marginal when attempting to spin up fourteen WD Black 7200rpm drives?

 

Apparently unraid deems the drive defective. I removed the drive from my unraid server. Threw it in a Windows machine and formatted it with NTFS. I also did a sector check on the drive and it passed just fine. I then threw it back in my unraid server and unraid just doesn't like this drive apparently. I'm sending it back for an RMA anyway....all my drives are covered under 5 year warranty.

 

It is not a power supply issue. I have a Seasonic X2 series 850 in that baby. Hell, the power supply fan never even turns on to cool it since it runs so efficient. Also the server runs 24/7 and I don't utilize any spindown features. To me servers should run 24/7 and it really doesn't use much juice at idle. My client softwares are always writing and using the server anyway.

 

Thanks.