I just upgraded my system from 4.7 to 5.0. I followed Tom's upgrade instructions, including a parity check immediately preceding the upgrade, a backup, and a reformatted flash. I am now conducting a new parity check. I am getting millions and millions (and counting as the parity check continues) of sync errors. Attached is my syslog. Whatever help you can provide will be greatly appreciated.

syslog_20130901_1616a.zip

I'm up to 250 million sync errors and the check is half-way done. I also noticed that none of the 6 drives (out of 15), that show sync errors, shows a temperature (however each has a solid green dot next to it). Also, when I access them via my Windows machine (non-Putty), they show that there is nothing on them. Thus, I'm assuming that they haven't spun up, however, I don't know what happened (because they were working fine in 4.7).

After hearing nothing here, I decided to show my system some mercy and end the parity check. I then rebooted and tried it again. This time, 4% into the check, the only drive that is showing errors is my parity drive (119). I plan to upgrade it anyways, so hopefully that will fix my problem with it. If it doesn't, I'll likely be whining here again.

 

As for why I had the previous "sync errors/discs not apparently spun up" issue immediately after my upgrade remains a mystery to me - especially since I didn't move anything except for the flash drive from the back of the case.

 

BTW, I just realized that I posted this in the wrong section. Perhaps this explains why I feel so lonely ...

Looking at your logs I would guess that one of the SAS controllers went off-line.    If it happens again you might want to check they are all seated properly. 

 

I had a similar issue when one of mine was not quite seated properly - everything would work the vast majority of the time, but things that stressed the system like parity checks would fail.