Re: What is this ata exception
On Mon, Mar 31, 2008 at 02:04:28PM +0000, T o n g wrote:
> I saw the following for the first time when I rebooted just now:
> Mar 31 09:10:04 cxmr kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Mar 31 09:10:04 cxmr kernel: ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in
> Mar 31 09:10:04 cxmr kernel: res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
> Mar 31 09:10:04 cxmr kernel: ata1: soft resetting port
> Mar 31 09:10:04 cxmr kernel: ata1.00: configured for UDMA/133
> Mar 31 09:10:04 cxmr kernel: ata1: EH complete
> Mar 31 09:10:04 cxmr kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Mar 31 09:10:04 cxmr kernel: ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in
> Mar 31 09:10:04 cxmr kernel: res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
> Mar 31 09:10:04 cxmr kernel: ata1: soft resetting port
> Mar 31 09:10:04 cxmr kernel: ata1.00: configured for UDMA/133
> Mar 31 09:10:04 cxmr kernel: ata1: EH complete
>
> It repeated several times after. What does it mean?
Doesn't look good whatever it is. Hope you have a good reliable backup.
> FYI, my box experiences sudden freeze and lock up recently so I enabled my
> smart monitor. In fact the reason for the reboot is that the system locked
> up entirely. It all goes like this, I didn't do anything, and it freezes.
This doesn't sound good either.
> BTW, I am still not quite sure what will happen when I enabled smartd. Do
> I get report from cron, or I have to pull it myself from time to time?
See man smartctl. You run a -t long test on the drive which will tell
you how long the test will take. Wait at least that long and use
smartctl to check the results. Ideally "completed without error" but you
will also get a list of all smart parameter values so you can see how
things are going.
NB: if SMART says that the drive is failing believe it. If SMART says
that the drive is fine, look further. Check the drive temp, listen to
it, watch those errors. Given those errors, I'd be checking the
warranty on the drive.
Doug.
Reply to: