May 13, 201313 yr ok - a bit more searching and I found the answer anyway, it's a 'harmless' error which will get taken out as and when time allows... assuming that unraidd being 'Tainted' in my syslog and 'untainted' in the linked thread doesn't mean anything... http://lime-technology.com/forum/index.php?topic=25425.msg221266#msg221266 -------------------------------------------------------------------------------------------- I'm towards the end of a (regular) parity check (running 5.0rc11), and I've noticed that the syslog contains a series of errors, apparently related to a CPU stall (syslog attached below), happened once after a couple of hours, then a few times in quick succession about 7 hours later on; no parity errors reported so far (86% done) (and no SMART errors showing), and running at a decent speed. looking back the previous thirty or so days of the log are nothing but spinups and spindowns, and the server's been working fine; however I noticed that in fact the previous parity check was throwing up the same errors, I'd missed it at the time, but doesn't seem to have had any bad effect (hopefully). I suspect it may have something to do with the extension card I installed around then, an AOC-SAS2LP-MV8, which so far just has one drive running from it, as I didn't see these errors in parity checks before. Can anyone shed any light on what's going on? Thanks, syslog.txt
Archived
This topic is now archived and is closed to further replies.