Hello,

 

A couple off days ago i noticed that a disk is showing up red. I believe it also showed errors. However when i look now it says 0. It still shows up red though. I've never had this before so i looked into the manuel, there it says: Red: the disk is disabled.

 

But i can still access the disk and files on that disk. I've attached a screenshot. Do i need to buy a new drive or what? All the drives are jumpered ears. I hope i don't have to buy a new drive because i see that the price of the disks are way higher than when i bought them.

 

Anyway can someone please tell me what to do.

You should pull a SMART report for that drive. It should be replaced if the SMART is showing something bad. You could also run some tests on the drive to determine the health, such as running the preclear script on it or putting it into a PC and running drive diagnostics on it.

 

If you don't want to do any tests then you can try this;

 

Stop the array.

Unassign that drive.

Power down the server.

Check or replace the SATA and power cables for that drive.

Power up the server.

Stop the array.

Assign the drive again.

Start the array and let the drive rebuild. You'll have to check the "are you sure" box.

 

If the drive is truely bad then the rebuild will fail.

 

 

I just plugged the drive into my pc and started checking the health. The log file that i've attached ain't good. Guess i have to buy a new drive and start rebuilding.

Disk_report_2012_03_20.txt

Where do you see problems on the disk ? Disk looks okay to me .

Where do you see problems on the disk ? Disk looks okay to me .

 

I thought the smart report. Plus the fact that it says:

 

The drive found 373 bad sectors during its self test.

There are 414 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.

At this point, warranty replacement of the disk is not yet possible, only if the health drops further.

It is recommended to examine the log of the disk regularly. All new problems found will be logged there.

It is recommended to backup immediately to prevent data loss.

 

and health is 11 %.

 

But if it's ok then how come it's red in my unraid server?

It's red because a write to it failed. Replace with a pre-cleared spare and the pre-clear the fautly drive. Or rebuild the drive in place by starting the array with the disk unassigned and the restarting the array with the disk assigned. Run parity check after the rebuild.

It's red because a write to it failed. Replace with a pre-cleared spare and the pre-clear the fautly drive. Or rebuild the drive in place by starting the array with the disk unassigned and the restarting the array with the disk assigned. Run parity check after the rebuild.

 

I'm very sorry but i don't understand: Replace with a pre-cleared spare and the pre-clear the fautly drive.

 

Do you mean i should remove the 'bad?' disk and insert the new disk i've ordered? And then should i pre clear the bad disk again?

 

Or option 2, rebuild the drive by starting the array with the disk unassigned (= not connected?) and then restart and connect the drive and do a parity check?

 

I've never been in the situation before where a drive had a write fail. So i hope you can clarify this for me because this is very new to me.

 

And is the disk ok like Ryan00 says? Because i'm confused cause my program said 11% disk life and bad sectors.

It's red because a write to it failed. Replace with a pre-cleared spare and the pre-clear the fautly drive. Or rebuild the drive in place by starting the array with the disk unassigned and the restarting the array with the disk assigned. Run parity check after the rebuild.

 

I'm very sorry but i don't understand: Replace with a pre-cleared spare and the pre-clear the fautly drive.

 

Do you mean i should remove the 'bad?' disk and insert the new disk i've ordered? And then should i pre clear the bad disk again?

Yes. If the current faulty drive passes pre-clear it becomes the spare.

 

Or option 2, rebuild the drive by starting the array with the disk unassigned (= not connected?) and then restart and connect the drive and do a parity check?

 

Just unassigned. It does not have to be disconnected.

Thanks for the help, i understand it. Can't seem to download 4.7 right now. I'll try again tomorrow when my disk arrives.