sata_nv error with smartctl access

sata_nv error with smartctl access

[Richard Scobie]

Hi,

This may already be addressed, but in case anyone is interested.

Fedora Core 6 2.6.19-1.2911.6.5, NVIDIA MCP55 based board using sata_nv.

When querying a drive using smartctl and SMART is not enabled on the 
drive, I get the following error:

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
ata3: EH complete
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back

This does not seem to cause any problems and once SMART is enabled, 
there are no more errors.

Regards,

Richard

Re: sata_nv error with smartctl access

[Tejun Heo]

Richard Scobie wrote:
> Hi,
> 
> This may already be addressed, but in case anyone is interested.
> 
> Fedora Core 6 2.6.19-1.2911.6.5, NVIDIA MCP55 based board using sata_nv.
> 
> When querying a drive using smartctl and SMART is not enabled on the
> drive, I get the following error:
> 
> ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata3.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
> ata3: EH complete
[--snip--]
> This does not seem to cause any problems and once SMART is enabled,
> there are no more errors.

Yeah, that's just libata reporting that a command has failed, which is
expected in your case.  Maybe libata should shut up on passthru
commands.  Right, we're currently not honoring REQ_QUIET, but SG doesn't
seem to support that flag either.

Anyways, it's safe to ignore the messages.

-- 
tejun