[mythtv-users] Mythtv recording filesystem (sata) goes read only

[Rich West]

Jason Spears wrote:
> On Fri, Apr 4, 2008 at 3:04 PM, Rich West <Rich.West at wesmo.com> wrote:
>
>   
>>  A larger snippet from the messages log is (dmesg gets cleared after reboot):
>>  Apr  3 16:47:27 mythtv1 kernel: ata4.00: exception Emask 0x0 SAct 0x0
>>  SErr 0x0 action 0x2 frozen
>>  Apr  3 16:47:27 mythtv1 kernel: ata4.00: cmd
>>  c8/00:00:77:31:21/00:00:00:00:00/e1 tag 0 dma 131072 in
>>  Apr  3 16:47:27 mythtv1 kernel:          res
>>  40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
>>  Apr  3 16:47:27 mythtv1 kernel: ata4.00: status: { DRDY }
>>  Apr  3 16:47:27 mythtv1 kernel: ata4: soft resetting link
>>  Apr  3 16:47:57 mythtv1 kernel: ata4.00: qc timeout (cmd 0x27)
>>  Apr  3 16:47:57 mythtv1 kernel: ata4.00: failed to read native max
>>  address (err_mask=0x4)
>>  Apr  3 16:47:57 mythtv1 kernel: ata4.00: HPA support seems broken, will
>>  skip HPA handling
>>  Apr  3 16:47:57 mythtv1 kernel: ata4.00: revalidation failed (errno=-5)
>>  Apr  3 16:47:57 mythtv1 kernel: ata4: failed to recover some devices,
>>  retrying in 5 secs
>>  Apr  3 16:48:02 mythtv1 kernel: ata4: soft resetting link
>>  Apr  3 16:48:02 mythtv1 kernel: ata4.00: configured for UDMA/133
>>  Apr  3 16:48:02 mythtv1 kernel: ata4: EH complete
>>  Apr  3 16:49:02 mythtv1 kernel: ata4.00: exception Emask 0x0 SAct 0x0
>>  SErr 0x0 action 0x2 frozen
>>  Apr  3 16:49:02 mythtv1 kernel: ata4.00: cmd
>>  c8/00:00:77:31:21/00:00:00:00:00/e1 tag 0 dma 131072 in
>>  Apr  3 16:49:02 mythtv1 kernel:          res
>>  40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
>>  Apr  3 16:49:02 mythtv1 kernel: ata4.00: status: { DRDY }
>>  Apr  3 16:49:02 mythtv1 kernel: ata4: soft resetting link
>>  Apr  3 16:49:03 mythtv1 kernel: ata4.00: configured for UDMA/133
>>  Apr  3 16:49:03 mythtv1 kernel: ata4: EH complete
>>
>>     
>
> Your messages look a lot like the ones here:
>
> http://www.spinics.net/lists/linux-ide/msg20225.html

Thanks!  And yikes.  Then end result of that one was to give up and 
replace the motherboard. :(  I'm getting closer to that conclusion.

-Rich