On Tue, Apr 17, 2012 at 7:07 PM, Jerry Rubinow <span dir="ltr"><<a href="mailto:jerrymr@gmail.com">jerrymr@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im">On Tue, Apr 17, 2012 at 9:02 AM, Mark Lord <span dir="ltr"><<a href="mailto:mythtv@rtr.ca" target="_blank">mythtv@rtr.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 12-04-16 11:36 PM, Jerry Rubinow wrote:<br>
> My mythbackend computer locked up today, the whole computer, not just mythbackend. Following is the<br>
> syslog at the time this happened. It's been rock steady for months, and I haven't made any changes<br>
> lately. I rebooted and now it seems to be functioning normally.<br>
><br>
> Any suggestions for what I should do? Is this a sign of disk errors?<br>
</div>..<br>
<br>
No, not with the scanty information provided.<br>
If there are disk errors, then there will be kernel logs along with them.<br>
<br>
Also, "smartctl -a /dev/sdX" will give very good information<br>
about the error state of the drives.<br></blockquote><div><br></div></div><div>Thanks Mark. kern.log had the same info as syslog, and smartctl wasn't revealing. Sorry for the scanty info, but I'm not sure what direction to look.</div>
<div><br></div><div>Once more piece of data is that I saw a very high load before it completely locked up, but the top items in top were not using much cpu.</div><span class="HOEnZb"><font color="#888888"><div><br></div>
</font></span></div></blockquote><div><br> That high load is caused by IO wait, which you can see in top as %wa. The longer the disk takes to complete a task, the more processes backup in the queue, causing a high load to be reported. Look closely at your disk, as it most likely has issues.<br>
</div></div>