Have you ruled out hard drive failure using smartctl? Do a long selftest and review the results.<div><br></div><div>Also, swap out your SATA cables or at least ensure they are fully seated.</div><div><br></div><div>Finally, check to see if there are known issues with the SATA interface you are using (is it onboard, add-in card, raid card?) and the linux kernel you have installed.<br>
<br><div class="gmail_quote">On Sat, Oct 16, 2010 at 12:59 AM, Troy Anderson <span dir="ltr"><<a href="mailto:freeswitch@tlainvestments.com">freeswitch@tlainvestments.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Many times there isn't anything suspect in any logs, but recently on one system, I saw the following (repeated many times over time):<br>
<br>
Oct 13 19:40:13 localhost kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen<br>
Oct 13 19:40:13 localhost kernel: ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0<br>
Oct 13 19:40:13 localhost kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)<br>
Oct 13 19:40:13 localhost kernel: ata2.00: status: { DRDY }<br>
Oct 13 19:40:17 localhost kernel: ata2: soft resetting link<br>
Oct 13 19:40:17 localhost kernel: ata2.00: configured for UDMA/33<br>
Oct 13 19:40:17 localhost kernel: sd 1:0:0:0: timing out command, waited 7s<br>
Oct 13 19:40:17 localhost kernel: ata2: EH complete<br>
Oct 13 19:40:17 localhost kernel: SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)<br>
Oct 13 19:40:17 localhost kernel: sda: Write Protect is off<br>
Oct 13 19:40:18 localhost kernel: SCSI device sda: drive cache: write back<br>
<br>
Can anyone help me with pointers on how to determine what they mean?<br>
<div><div></div><div class="h5"><br>
<br>
On Oct 15, 2010, at 4:34 PM, mazilo wrote:<br>
<br>
><br>
><br>
> Troy Anderson wrote:<br>
>> At this point, I am trying to figure out what may be the root cause. Has<br>
>> anyone else experienced something this? Any suggestions?<br>
> Your best bet on this is to look at the log file (/var/log/messages and<br>
> among others in the same sub-dir) and see if you can identify what triggered<br>
> the HD into a RO mode.<br>
><br>
> -----<br>
> don't and stop are the ONLY two 4-letter words considered offensive to men,<br>
> but not when used together.<br>
> --<br>
> View this message in context: <a href="http://freeswitch-users.2379917.n2.nabble.com/Read-only-filesystem-tp5640425p5640809.html" target="_blank">http://freeswitch-users.2379917.n2.nabble.com/Read-only-filesystem-tp5640425p5640809.html</a><br>
> Sent from the freeswitch-users mailing list archive at Nabble.com.<br>
><br>
> _______________________________________________<br>
> FreeSWITCH-users mailing list<br>
> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-Rupa<br>
</div>