March 28, 201610 yr Ahhh... another problem. After I fixed the new 6TB drive size issue with a reboot, I decided to do a parity check before upgrading to v6. That did not go too well, I am seeing a multitude of errors, on parity drive and other drives. Disk 17 is redballed. I am quite unsure what I need to do at this point. I could replace drive 17, which was totally fine until now, but I am concerned about about errors on the parity drive. Any help would be much appreciated. By the way, the reboot did not go too well. The server did not come back up. I had to shut it down via telnet (saw some kind of error message there, forget what it said exactly) and start again. Thanks very much in advance.
March 28, 201610 yr Issues with multiple drives. Try reseating your controller. What is the exact model of your power supply?
March 28, 201610 yr You should also post SMART reports for all disks, or at least the ones with issues, see trurl's signature if you don't know how.
March 28, 201610 yr Author Thank you guys. I've been doing some investigating on my end, looks like it's the sickbeard that caused that. The mover ran pretty much when the errors began. I recall this happened to me a few years back. In both cases I was running parity check. I now disable Sabnzbd and Sickbeard when I run checks, but forgot to do that this time. Anyway, all drives are fine, I ran SMART checks and all passed. Performing restore procedure now.
Archived
This topic is now archived and is closed to further replies.