Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
1,302 Views

DP67BG SATA port problem?

I'm noticing errors on my (very old) DP67BG SATA ports as of late, particularly under heavy SATA usage.

Might this be due to the 6-series chipset error (which this MB exhibits)?

System is running Ubuntu 12.10 64-bit.

Example errors follow.

Regards,

Gary

Nov 25 01:07:52 powerspec kernel: [ 2081.561802] ata3.00: exception Emask 0x52 SAct 0x7 SErr 0x880d00 action 0x6 frozen

Nov 25 01:07:52 powerspec kernel: [ 2081.561808] ata3.00: irq_stat 0x08000000, interface fatal error

Nov 25 01:07:52 powerspec kernel: [ 2081.561813] ata3: SError: { UnrecovData Proto HostInt 10B8B LinkSeq }

Nov 25 01:07:52 powerspec kernel: [ 2081.561817] ata3.00: failed command: READ FPDMA QUEUED

Nov 25 01:07:52 powerspec kernel: [ 2081.561826] ata3.00: cmd 60/80:00:31:1b:32/00:00:22:00:00/40 tag 0 ncq 65536 in

Nov 25 01:07:52 powerspec kernel: [ 2081.561826] res 40/00:04:31:1b:32/00:00:22:00:00/40 Emask 0x52 (ATA bus error)

Nov 25 01:07:52 powerspec kernel: [ 2081.561830] ata3.00: status: { DRDY }

Nov 25 01:07:52 powerspec kernel: [ 2081.561834] ata3.00: failed command: READ FPDMA QUEUED

Nov 25 01:07:52 powerspec kernel: [ 2081.561841] ata3.00: cmd 60/80:08:b1:1b:32/00:00:22:00:00/40 tag 1 ncq 65536 in

Nov 25 01:07:52 powerspec kernel: [ 2081.561841] res 40/00:04:31:1b:32/00:00:22:00:00/40 Emask 0x52 (ATA bus error)

Nov 25 01:07:52 powerspec kernel: [ 2081.561845] ata3.00: status: { DRDY }

Nov 25 01:07:52 powerspec kernel: [ 2081.561849] ata3.00: failed command: READ FPDMA QUEUED

Nov 25 01:07:52 powerspec kernel: [ 2081.561857] ata3.00: cmd 60/08:10:11:9e:c0/00:00:03:00:00/40 tag 2 ncq 4096 in

Nov 25 01:07:52 powerspec kernel: [ 2081.561857] res 40/00:04:31:1b:32/00:00:22:00:00/40 Emask 0x52 (ATA bus error)

Nov 25 01:07:52 powerspec kernel: [ 2081.561861] ata3.00: status: { DRDY }

Nov 25 01:07:52 powerspec kernel: [ 2081.561867] ata3: hard resetting link

Nov 25 01:07:52 powerspec kernel: [ 2081.561885] ata4.00: exception Emask 0x52 SAct 0x1 SErr 0x880d00 action 0x6 frozen

Nov 25 01:07:52 powerspec kernel: [ 2081.561886] ata4.00: irq_stat 0x08000000, interface fatal error

Nov 25 01:07:52 powerspec kernel: [ 2081.561887] ata4: SError: { UnrecovData Proto HostInt 10B8B LinkSeq }

Nov 25 01:07:52 powerspec kernel: [ 2081.561888] ata4.00: failed command: READ FPDMA QUEUED

Nov 25 01:07:52 powerspec kernel: [ 2081.561891] ata4.00: cmd 60/80:00:b9:1b:32/00:00:22:00:00/40 tag 0 ncq 65536 in

Nov 25 01:07:52 powerspec kernel: [ 2081.561891] res 40/00:04:b9:1b:32/00:00:22:00:00/40 Emask 0x52 (ATA bus error)

Nov 25 01:07:52 powerspec kernel: [ 2081.561892] ata4.00: status: { DRDY }

Nov 25 01:07:52 powerspec kernel: [ 2081.561893] ata4: hard resetting link

Nov 25 01:07:52 powerspec kernel: [ 2081.879125] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 25 01:07:52 powerspec kernel: [ 2081.879149] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 25 01:07:52 powerspec kernel: [ 2081.890816] ata3.00: configured for UDMA/133

Nov 25 01:07:52 powerspec kernel: [ 2081.903045] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903049] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Nov 25 01:07:52 powerspec kernel: [ 2081.903052] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903054] Sense Key : Aborted Command [current] [descriptor]

Nov 25 01:07:52 powerspec kernel: [ 2081.903058] Descriptor sense data with sense descriptors (in hex):

Nov 25 01:07:52 powerspec kernel: [ 2081.903060] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903069] 22 32 1b 31

Nov 25 01:07:52 powerspec kernel: [ 2081.903074] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903076] Add. Sense: No additional sense information

Nov 25 01:07:52 powerspec kernel: [ 2081.903078] sd 2:0:0:0: [sdb] CDB:

Nov 25 01:07:52 powerspec kernel: [ 2081.903080] Read(10): 28 00 22 32 1b 31 00 00 80 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903088] end_request: I/O error, dev sdb, sector 573709105

Nov 25 01:07:52 powerspec kernel: [ 2081.903128] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903130] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Nov 25 01:07:52 powerspec kernel: [ 2081.903132] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903133] Sense Key : Aborted Command [current] [descriptor]

Nov 25 01:07:52 powerspec kernel: [ 2081.903136] Descriptor sense data with sense descriptors (in hex):

Nov 25 01:07:52 powerspec kernel: [ 2081.903138] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903147] 22 32 1b 31

Nov 25 01:07:52 powerspec kernel: [ 2081.903151] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903153] Add. Sense: No additional sense information

Nov 25 01:07:52 powerspec kernel: [ 2081.903155] sd 2:0:0:0: [sdb] CDB:

Nov 25 01:07:52 powerspec kernel: [ 2081.903165] Read(10): 28 00 22 32 1b b1 00 00 80 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903171] end_request: I/O error, dev sdb, sector 573709233

Nov 25 01:07:52 powerspec kernel: [ 2081.903201] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903203] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Nov 25 01:07:52 powerspec kernel: [ 2081.903204] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903206] Sense Key : Aborted Command [current] [descriptor]

Nov 25 01:07:52 powerspec kernel: [ 2081.903208] Descriptor sense data with sense descriptors (in hex):

Nov 25 01:07:52 powerspec kernel: [ 2081.903210] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903219] 22 32 1b 31

Nov 25 01:07:52 powerspec kernel: [ 2081.903223] sd 2:0:0:0: [sdb]

Nov 25 01:07:52 powerspec kernel: [ 2081.903225] Add. Sense: No additional sense information

Nov 25 01:07:52 powerspec kernel: [ 2081.903227] sd 2:0:0:0: [sdb] CDB:

Nov 25 01:07:52 powerspec kernel: [ 2081.903228] Read(10): 28 00 03 c0 9e 11 00 00 08 00

Nov 25 01:07:52 powerspec kernel: [ 2081.903235] end_request: I/O error, dev sdb, sector 62955025

Nov 25 01:07:52 powerspec kernel: [ 2081.903245] ata3: EH complete

Tags (1)
0 Kudos
3 Replies
idata
Community Manager
54 Views

You can download a Windows utility which will detect whether your motherboard has the SATA bug:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20034&lang=eng Download Center

idata
Community Manager
54 Views

Thanks, but I had done so, and it does have the (potential )SATA degradation flaw.

I was wondering whether the errors I'm seeing are due to that or something else, as the flaw does not always manifest itself on all systems.

Regards,

Gary

idata
Community Manager
54 Views

You might want to run a disc diagnostic specific to your brand of hard discs. Western Digital calls theirs Data Lifeguard and Seagate calls their SeaTools, both are run from a bootable CD or possibly a bootable USB stick. I've had discs fail in the past, it usually starts with a file can't be read, longer than usual boot times, the worst is when the click of death or chattering happens.

If your board does have the B2 stepping and the SATA utility says your board is effected, probably best to just get rid of it. But 1st check to see if you just have a misbehaving disc.

http://www.intel.com/support/chipsets/6/sb/CS-032521.htm Intel� 6 Series Chipset — Chipset circuit design issue identified

Reply