Red Ball V5 [version: 5.0-rc5] - Advice.

[Thomss]

Evening all,

Hope I get a little heads up on how to proceed now if that's ok.

 

I just went to grab a file from a disk I do not often get files from and noticed it was copying very slowly to my local drive, naturally I checked what was up and seen Disk 3 had red balled.

 

I grabbed the syslog, powered down and checked all cables, all looked good - powered back up.

 

Now I am able to assign the disk, however its status is still a red ball and I am not able to do a parity check, also there is no temp showing on the main web page as all the other disks have.

 

What would be the recommended course of action please?

 

New config etc,

 

 

Thanks in advance!

 

 

 

 

Thomas.

 

 

syslog.zip

[garycase]

The reason access is slow is you're not actually reading from that disk anymore ==> the data is being reconstructed from the other disks plus parity, as it's failed.

 

Course of action:  Replace the failed disk.

 

[Thomss]

Thanks, just went and unassigned it, started the array, stopped it again and reassigned the drive it and let it build again, that completed and now it is 50% through a parity check. I'll keep an eye on that drive in the future.