[Bug 409639] Re: sata hard drive connection fails with link is slow to respond, please be patient (ready=0) ; SRST failed (errno=-16) ; hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

LimCore user.ubuntu at limcore.com
Thu Aug 6 01:28:18 UTC 2009


More info:

I did run badblok -w  and so on  after the errors, all is fine.
There are tons of this I/O errors - always after the device fails it totally stops working, and after reboot it works fully.
If the device do not die in between, I can write/read entire hard-drive till last sector without any problems.

Therefore it is NOT a device-media / surface problem, must be SATA
link/driver/etc problem.


more examples of reports from logs:


Aug  5 15:05:18 lcwood kernel: [75189.807205] ata3: hard resetting link
Aug  5 15:05:28 lcwood kernel: [75199.816547] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug  5 15:05:33 lcwood kernel: [75204.816528] ata3.00: qc timeout (cmd 0xec)
Aug  5 15:05:33 lcwood kernel: [75204.816547] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aug  5 15:05:33 lcwood kernel: [75204.816555] ata3: hard resetting link
Aug  5 15:05:43 lcwood kernel: [75214.820531] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug  5 15:05:53 lcwood kernel: [75224.820525] ata3.00: qc timeout (cmd 0xec)
Aug  5 15:05:53 lcwood kernel: [75224.820539] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aug  5 15:05:53 lcwood kernel: [75224.820547] ata3: limiting SATA link speed to 1.5 Gbps
Aug  5 15:05:53 lcwood kernel: [75224.820551] ata3: hard resetting link
Aug  5 15:06:03 lcwood kernel: [75234.828041] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug  5 15:06:33 lcwood kernel: [75264.828042] ata3.00: qc timeout (cmd 0xec)
Aug  5 15:06:33 lcwood kernel: [75264.828062] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aug  5 15:06:33 lcwood kernel: [75264.828074] ata3.00: disabled
Aug  5 15:06:33 lcwood kernel: [75264.828215] ata3: hard resetting link
Aug  5 15:06:43 lcwood kernel: [75274.872552] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug  5 15:06:43 lcwood kernel: [75274.872617] ata3: EH complete
Aug  5 15:06:43 lcwood kernel: [75274.872683] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.872704] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872722] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872732] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872741] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872750] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872759] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872768] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872777] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872787] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.872796] lost page write due to I/O error on sdc
Aug  5 15:06:43 lcwood kernel: [75274.873139] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.873511] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.873828] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.874278] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.874597] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.874952] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.875314] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.875810] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.876152] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:43 lcwood kernel: [75274.876542] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

Ok and what is that???
Look at the "typos"! This is vebatim copy/paste from /var/log/messages (and this is on filessystem on sda, that works without problems)

Aug  5 15:06:45 lcwood kernel: [75275.941054] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.941340] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.941590] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.941606] sd 2:00:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.944849] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: 0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.947955] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.949694] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.949966] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.950244] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.950540] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.950555] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.952835] sd 2:0:0:0: [sdc] Result: hostbyte=DI0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.955356] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: 0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.957621] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.957894] sd 2:00:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.960028] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.960307] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BA0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.963390] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: 0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.966428] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: 0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.978487] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.978784] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.979060] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK


There is a line with "typo" "sd 2:00:" instead "sd 2:0:" .... strange:
Aug  5 15:06:45 lcwood kernel: [75275.941590] sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug  5 15:06:45 lcwood kernel: [75275.941606] sd 2:00:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK



And this is normal bootup,  sdc is the new 1 TB driver that fails:
Aug  4 14:33:54 lcwood kernel: [    4.424310] sd 0:0:0:0: [sda] Write Protect is off
Aug  4 14:33:54 lcwood kernel: [    4.424330] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug  4 14:33:54 lcwood kernel: [    4.424334]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 sda16 sda17 >
Aug  4 14:33:54 lcwood kernel: [    4.656665] sd 0:0:0:0: [sda] Attached SCSI disk
Aug  4 14:33:54 lcwood kernel: [    4.656715] sd 0:0:0:0: Attached scsi generic sg0 type 0
Aug  4 14:33:54 lcwood kernel: [    4.656768] scsi 1:0:0:0: Direct-Access     ATA      WDC WD7500AAKS-0 30.0 PQ: 0 ANSI: 5
Aug  4 14:33:54 lcwood kernel: [    4.656843] sd 1:0:0:0: [sdb] 1465149168 512-byte hardware sectors: (750 GB/698 GiB)
Aug  4 14:33:54 lcwood kernel: [    4.656855] sd 1:0:0:0: [sdb] Write Protect is off
Aug  4 14:33:54 lcwood kernel: [    4.656876] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug  4 14:33:54 lcwood kernel: [    4.656916] sd 1:0:0:0: [sdb] 1465149168 512-byte hardware sectors: (750 GB/698 GiB)
Aug  4 14:33:54 lcwood kernel: [    4.656927] sd 1:0:0:0: [sdb] Write Protect is off
Aug  4 14:33:54 lcwood kernel: [    4.656948] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug  4 14:33:54 lcwood kernel: [    4.656951]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 >
Aug  4 14:33:54 lcwood kernel: [    4.790069] sd 1:0:0:0: [sdb] Attached SCSI disk
Aug  4 14:33:54 lcwood kernel: [    4.790098] sd 1:0:0:0: Attached scsi generic sg1 type 0
Aug  4 14:33:54 lcwood kernel: [    4.790149] scsi 2:0:0:0: Direct-Access     ATA      SAMSUNG HD103UJ  1AA0 PQ: 0 ANSI: 5
Aug  4 14:33:54 lcwood kernel: [    4.790214] sd 2:0:0:0: [sdc] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
Aug  4 14:33:54 lcwood kernel: [    4.790226] sd 2:0:0:0: [sdc] Write Protect is off
Aug  4 14:33:54 lcwood kernel: [    4.790246] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug  4 14:33:54 lcwood kernel: [    4.790288] sd 2:0:0:0: [sdc] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
Aug  4 14:33:54 lcwood kernel: [    4.790299] sd 2:0:0:0: [sdc] Write Protect is off
Aug  4 14:33:54 lcwood kernel: [    4.790319] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug  4 14:33:54 lcwood kernel: [    4.790322]  sdc: unknown partition table
Aug  4 14:33:54 lcwood kernel: [    4.794899] sd 2:0:0:0: [sdc] Attached SCSI disk
Aug  4 14:33:54 lcwood kernel: [    4.794932] sd 2:0:0:0: Attached scsi generic sg2 type 0
Aug  4 14:33:54 lcwood kernel: [    4.795167] pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  4 14:33:54 lcwood kernel: [    4.795309] scsi4 : pata_atiixp
Aug  4 14:33:54 lcwood kernel: [    4.795373] scsi5 : pata_atiixp
Aug  4 14:33:54 lcwood kernel: [    4.796309] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00 irq 14
Aug  4 14:33:54 lcwood kernel: [    4.796311] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08 irq 15
Aug  4 14:33:54 lcwood kernel: [    4.964530] ata5.01: ATAPI: DVDR   PX-750A, 1.02, max UDMA/66
Aug  4 14:33:54 lcwood kernel: [    4.980556] ata5.01: configured for UDMA/66

-- 
sata hard drive connection fails with link is slow to respond, please be patient (ready=0) ; SRST failed (errno=-16) ; hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
https://bugs.launchpad.net/bugs/409639
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.




More information about the kernel-bugs mailing list