June 19, 201313 yr Hey! Have had great experiences with my unRAID arrays but one of them is being a douche. The other day I noticed it had a flashing red ball, I assumed that the drive was pooched so I bought a new one, popped it in and it started to rebuild. After only a few hours (9 x 2TB disks = 720mins to rebuild apparently) the new disk is now flashing red too. The strange part is that the error count (384) is identical to the previous disk which I took a screen shot of before the swap, in case my disks got re-arranged for some reason. How can I fix 'er up? Is my parity drive the problem here? - Ian
June 19, 201313 yr Attaching a Syslog will help others isolate what the trouble might be. In my experience with the Red Ball it can arise from a write error which can be a drive, a connection problem, a power supply, a motherboard. The Syslog will help to narrow the choices down. Your old (original) drive might really be OK and you may need it to reconstruct your files if there are parity errors. Hopefully a "hero" member will help you more. Good luck getting your system all green again! I know it will take time, but you will probably want to PreClear the replacement drive first. It's a great way to test the quality of the drive and check for "infant mortality."
Archived
This topic is now archived and is closed to further replies.