Hello

I have HDD with red ball so went and bought new HDD, installed and started the rebuild, all seemed to be okay but when I came back to the server it had finished and the new drive has a red ball now. Any ideas why this has happened. All other drives are green.

 

Don't know what to do, any help would be appreciated.

 

Thanks

 

Hello

I have HDD with red ball so went and bought new HDD, installed and started the rebuild, all seemed to be okay but when I came back to the server it had finished and the new drive has a red ball now. Any ideas why this has happened. All other drives are green.

 

Don't know what to do, any help would be appreciated.

 

Thanks

 

Yes...

 

Either:

 

A. the new disk is also defective

or

B. The old disk was not defective, but something else in your server prevented it AND the new disk from being written. 

(bad SATA cable, SATA loose cable, bad backplane, bad disk controller, bad/loose  power cable, bad memory, incorrectly configured memory, hardware conflict, bad/inadequate power supply, etc)

 

Without you posting a syslog, there no no more analysis anybody can offer.  (see the sticky on how to submit a syslog)

I had one drive (2TB) in my system go "bad" only while installed in an unRAID box. I removed the "bad" drive and setup Windows 7 on it and did a sector by sector check and found nothing wrong. For some reason unRAID just didn't like this particular drive. It was just a WD 2TB Black series drive. The strange thing is after getting a new drive and installing it in my unRAID box worked just fine. To settle my curiosity I removed the drive I just installed and re-installed the "bad" drive. Once again unRAID had issues with it. This eliminates power / connections / etc...and in the end I just put back the new drive into the unRAID box and all is well again. Since my "bad" drive was still in warranty I did an RMA anyway. I just have a backup 2TB drive ready when ever. I can't explain what happened or what the issue really was but since the "bad" drive is gone there is no sense to drive myself crazy about it.

 

 

syslog attached in .txt file.

 

 

 

syslog.txt

System components

ASUS P5P43TD motherboard

Kingston 2x 2Gb RAM

Corsair HX850W power supply

Supermicro 8-channel SAS/SATA adapter

MINI-SAS (SFF-8087) to 4 x SATA cable with sideband

 

Unraid Ver 4.5.4

Drives

Parity Samsung 2T

Disk 1 Seagate 500Gb

Disk 2 Seagate 1T

Disk 3 Seagate 1.5T

Disk 4 WD 1T

Disk 5 WD 1T

Disk 6 Seagate 1T

Disk 7 Seagate 2T

Disk 8 Samsung 2T

The syslog does not show enough please post one after the system has been running for at least 10 minutes.

 

I put back in the drive with the error and started the restore and it has now completed and all GREEN. It must have been a read write error.

 

I now have a spare drive just in case.

 

Thank you for your help.

 

 

 

I put back in the drive with the error and started the restore and it has now completed and all GREEN. It must have been a read write error.

 

I now have a spare drive just in case.

 

Thank you for your help.

 

 

A drive is taken off-line (red indicator) only when a "write" to it fails. Read failures increment the "error" counter on the management display.  Parity errors can be caused by anything, including memory, disk controllers, disks, power supply.