Re: [smartmontools-support] exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen

[Jonas P. <jon...@xm...>]

Hi Justin and thanks for your prompt response,

Justin Piszcz skrev:
> On Sat, 30 Aug 2008, Jonas Petersson wrote:
>> [ I wasn't a member on my first submit and it seems that moderation is
>> somewhat slow so I resend this now ]
>>
>> Device Model:     FUJITSU MHY2250BH
>> Serial Number:    K43CT862GMK9
> 
> If the drive is capable of NCQ, I would try disable/enabling it (via
> kernel) parameter and see if that makes any difference (doubt it) but
> something to try.

That would be /sys/block/sda/device/queue_depth, right? I already 
checked that and it was "1" so I guess there is nothing to do.

>  Also, do/not run smart tests during heavy I/O?

They are certainly OK without heavy I/O. Those that take some time to 
run where run during "normal" I/O - I kept using the system normally. 
The problem occurs during low I/O conditions as far as I can tell. For 
example during the night (slocate may run at some stage, but according 
to the logs the problems has occured at 4 different time during the 
night and even a fairly long slocate session can't possibly have covered 
more than 2 of them at worst).


>  Have you tried disabline smartmontools to see if the problem persists?

Yes: Initially, it happened before I even installed smartmontools. It 
kept happening with while smartd was running for a while. It kept 
happening when I disabled smartd and just ran smartctl now and then. It 
also happened (one) about 5 minutes after rebooting when no 
smartmontools programs either smartd nor smartctl had efter run. In this 
particular case, the boot process involved automatic installation of the 
nvidia binary driver which may have caised a bit of heavy I/O for a while.

Does this give you any further clues? Would a full dump of smartctl 
--all help?

			Best / Jonas