[Freeswitch-users] Read only filesystem

[Steven Ayre]

See below.

Steve on iPhone

On 16 Oct 2010, at 06:59, Troy Anderson <freeswitch at tlainvestments.com> wrote:

> Many times there isn't anything suspect in any logs, but recently on one system, I saw the following (repeated many times over time):
> 
> Oct 13 19:40:13 localhost kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> Oct 13 19:40:13 localhost kernel: ata2.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
> Oct 13 19:40:13 localhost kernel:          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

The driver asked the drive to do something and got no response from the drive. The numbers tell you what, but is only really useful if you're a developer of the driver.

> Oct 13 19:40:13 localhost kernel: ata2.00: status: { DRDY }
> Oct 13 19:40:17 localhost kernel: ata2: soft resetting link

Chipset is disconnecting and reconnecting the drive, since that can sometimes fix a problem by resetting the drive.

> Oct 13 19:40:17 localhost kernel: ata2.00: configured for UDMA/33

Fallen speed back to UDMA 33 (slowest UDMA), since some problems are caused by the drive running faster than the drive/cable can cope with.

> Oct 13 19:40:17 localhost kernel: sd 1:0:0:0: timing out command, waited 7s

Something timed out - not sure if this is the reset or the failed action that triggered the reset.

> Oct 13 19:40:17 localhost kernel: ata2: EH complete
> Oct 13 19:40:17 localhost kernel: SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
> Oct 13 19:40:17 localhost kernel: sda: Write Protect is off
> Oct 13 19:40:18 localhost kernel: SCSI device sda: drive cache: write back

Drive is back.

> 
> Can anyone help me with pointers on how to determine what they mean?
> 
> 
> On Oct 15, 2010, at 4:34 PM, mazilo wrote:
> 
>> 
>> 
>> Troy Anderson wrote:
>>> At this point, I am trying to figure out what may be the root cause.  Has
>>> anyone else experienced something this?  Any suggestions?
>> Your best bet on this is to look at the log file (/var/log/messages and
>> among others in the same sub-dir) and see if you can identify what triggered
>> the HD into a RO mode.
>> 
>> -----
>> don't and stop are the ONLY two 4-letter words considered offensive to men,
>> but not when used together.
>> -- 
>> View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Read-only-filesystem-tp5640425p5640809.html
>> Sent from the freeswitch-users mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
> 
> 
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org