[App_rpt-users] Mighty GURU's - HSM Violation - Centos

[Stephen Rodgers]

Jim Duuuude wrote:
> yeah, sounds like your HD is not feeling well...
> 
>> Date: Thu, 30 Sep 2010 21:44:43 -0500
>> To: app_rpt-users at qrvc.com; dillo at armadillo.org
>> From: mcheavens at usa.net
>> Subject: [App_rpt-users] Mighty GURU's - HSM Violation - Centos
>>
>> Clean install of Centos (ACID).
>>
>> Intel SSD 40G drive SATA
>>
>> About twice a day I get this message on the screen and in /var/log/messages
>>
>> Sep 29 02:28:24 Asbury kernel: ata1.00: exception Emask 0x0 SAct 0x0 
>> SErr 0x0 action 0x6 frozen
>> Sep 29 02:28:24 Asbury kernel: ata1.00: cmd 
>> b0/d5:01:09:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
>> Sep 29 02:28:24 Asbury kernel:          res 
>> 58/00:ff:0b:4f:c2/00:00:00:00:00/00 Emask 0x2 (HSM violation)
>> Sep 29 02:28:24 Asbury kernel: ata1.00: status: { DRDY DRQ }
>> Sep 29 02:28:24 Asbury kernel: ata1: hard resetting link
>> Sep 29 02:28:24 Asbury kernel: ata1: SATA link up 1.5 Gbps (SStatus 
>> 113 SControl 310)
>> Sep 29 02:28:24 Asbury kernel: ata1.00: configured for UDMA/133
>> Sep 29 02:28:24 Asbury kernel: ata1: EH complete
>> Sep 29 02:28:24 Asbury kernel: SCSI device sda: 78165360 512-byte 
>> hdwr sectors (40021 MB)
>> Sep 29 02:28:24 Asbury kernel: sda: Write Protect is off
>> Sep 29 02:28:24 Asbury kernel: SCSI device sda: drive cache: write back
>>
>> Any suggestions?
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at qrvc.com
>> http://qrvc.com/mailman/listinfo/app_rpt-users
>  		 	   		  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users

Actually,

That's a Host State Machine Violation. It results in a downed SATA link.
Probably a quirk with the SATA controller hardware on the MOBO or a Linux driver not fully understanding
how to talk to the SATA controller to work around the quirk. I'd suggest trying a different
motherboard as we certainly can't be messing the drivers shipped with Centos.

Steve
WA6ZFT