search for: did_bad_target

...lding a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168487.543576] sd...

...ive I pulled >> from my notebook (when I had to upgrade to a 500GB SSD drive). Centos >> install went fine and ran for a couple days then got errors on the >> console. Here is an example: >> >> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK >> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 >> 00 00 08 00 >> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 >> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: >> hostbyte=DID_BAD_TAR...

...7.210727] ata7.00: detaching (SCSI 6:0:0:0) Mar  9 23:57:43 ftp2 kernel: [121567.240037] ata8: failed to resume link (SControl 45) Mar  9 23:57:43 ftp2 kernel: [121567.250170] sd 6:0:0:0: [sdc] Synchronizing SCSI cache Mar  9 23:57:43 ftp2 kernel: [121567.250220] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Mar  9 23:57:43 ftp2 kernel: [121567.250227] sd 6:0:0:0: [sdc] Stopping disk Mar  9 23:57:43 ftp2 kernel: [121567.250249] sd 6:0:0:0: [sdc] START_STOP FAILED Mar  9 23:57:43 ftp2 kernel: [121567.250252] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Mar...

...I pulled >> from my notebook (when I had to upgrade to a 500GB SSD drive). >> Centos install went fine and ran for a couple days then got errors on >> the console. Here is an example: >> >> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK >> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 >> b0 00 00 08 00 >> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 >> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: >> hostbyte=DID_BAD_T...

...r problem, you'd write to sector 17066160 and see if the drive complies or spits back a write error. It looks like a bad sector in that the same LBA is reported each time but I've only ever seen this with both a read error and a UNC error. So I'm not sure it's a bad sector. What is DID_BAD_TARGET? And what do you get for smartctl -x <dev> Chris Murphy On Wed, Aug 9, 2017, 8:03 AM Robert Moskowitz <rgm at htt-consult.com> wrote: > I am building a new system using an Kingston 240GB SSD drive I pulled > from my notebook (when I had to upgrade to a 500GB SSD drive). Cento...

virtio-scsi currently has limit of 8 outstanding notifications so when more that 8 LUNs are unplugged, some are missed. Commit 5ff843721467 ("scsi: virtio_scsi: unplug LUNs when events missed") Fixed this by checking the 'event overflow' bit and manually scanned the bus to see which LUNs are still there. However there is a corner case when all LUNs are unplugged. In this case

...te to sector 17066160 and see if the > drive complies or spits back a write error. It looks like a bad sector in > that the same LBA is reported each time but I've only ever seen this with > both a read error and a UNC error. So I'm not sure it's a bad sector. > > What is DID_BAD_TARGET? I have no experience on how to force a write to a specific sector and not cause other problems. I suspect that this sector is in the / partition: Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 51...

...a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: > > [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 > [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 > [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK >...

...lding a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 00 00 08 00 [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168487.543576] sd...

...ingston 240GB SSD drive I pulled > from my notebook (when I had to upgrade to a 500GB SSD drive). Centos > install went fine and ran for a couple days then got errors on the > console. Here is an example: > > [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: > hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 > 00 00 08 00 > [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 > [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: > hostbyte=DID_BAD_TARGET driverbyte=DRI...

...ive I pulled >> from my notebook (when I had to upgrade to a 500GB SSD drive). Centos >> install went fine and ran for a couple days then got errors on the >> console. Here is an example: >> >> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK >> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 >> 00 00 08 00 >> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 >> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: >> hostbyte=DID_BAD_TAR...

...m my notebook (when I had to upgrade to a 500GB SSD drive). Centos > >> install went fine and ran for a couple days then got errors on the > >> console. Here is an example: > >> > >> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: > >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > >> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 > >> 00 00 08 00 > >> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160 > >> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: > >...

Commit 5ff843721467 ("scsi: virtio_scsi: unplug LUNs when events missed"), almost fixed the case of mass unpluging of LUNs, but it missed a corner case in which all the LUNs are unplugged at the same time. In this case INQUIRY ends with DID_BAD_TARGET. Detect this and unplug the LUN. Signed-off-by: Maxim Levitsky <mlevitsk at redhat.com> --- drivers/scsi/virtio_scsi.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c index 0e0910c5b9424..c7f0c22b6f11d 100644 --- a/driv...

...;>> drive complies or spits back a write error. It looks like a bad sector in >>> that the same LBA is reported each time but I've only ever seen this with >>> both a read error and a UNC error. So I'm not sure it's a bad sector. >>> >>> What is DID_BAD_TARGET? >> >> I have no experience on how to force a write to a specific sector and >> not cause other problems. I suspect that this sector is in the / >> partition: >> >> Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors >> Units = sectors of 1 * 51...

Ok, got a quickie. I have an eSATA drive, a 750GB Seagate in an eSATA external enclosure, and a Silicon Image sil3132 ExpressCard controller for my laptop. The disk and controller work great in CentOS 5 (or F7, for that matter), if I specifically mount it. This is not how I want to have to use this drive, however. I want to hotplug it; that is, plug the controller into the laptop, and then

...or. It looks like a bad sector >>>> in >>>> that the same LBA is reported each time but I've only ever seen this >>>> with >>>> both a read error and a UNC error. So I'm not sure it's a bad sector. >>>> >>>> What is DID_BAD_TARGET? >>> >>> >>> I have no experience on how to force a write to a specific sector and >>> not cause other problems. I suspect that this sector is in the / >>> partition: >>> >>> Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 secto...

...if > the > > drive complies or spits back a write error. It looks like a bad sector in > > that the same LBA is reported each time but I've only ever seen this with > > both a read error and a UNC error. So I'm not sure it's a bad sector. > > > > What is DID_BAD_TARGET? > > I have no experience on how to force a write to a specific sector and > not cause other problems. I suspect that this sector is in the / > partition: > > Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector si...

...ta2: failed due to HW bug, retry pmp=0 Apr 11 04:24:44 xenserver kernel: [277248.753334] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 11 04:24:44 xenserver kernel: [277248.753366] ata2: EH complete Apr 11 04:24:44 xenserver kernel: [277248.753384] sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK Apr 11 04:24:44 xenserver kernel: [277248.753399] end_request: I/O error, dev sdb, sector 1953519935 Apr 11 04:24:44 xenserver kernel: [277248.753410] end_request: I/O error, dev sdb, sector 1953519935 Apr 11 04:24:44 xenserver kernel: [277248.753421] md: super_wri...

...sector >>>>> in >>>>> that the same LBA is reported each time but I've only ever seen this >>>>> with >>>>> both a read error and a UNC error. So I'm not sure it's a bad sector. >>>>> >>>>> What is DID_BAD_TARGET? >>>> >>>> >>>> I have no experience on how to force a write to a specific sector and >>>> not cause other problems. I suspect that this sector is in the / >>>> partition: >>>> >>>> Disk /dev/sda: 240.1 GB, 2400574...

....577318] ata2: SATA link down (SStatus 0 SControl 310) [32021.577325] ata2.00: disabled [32021.577413] ata2.00: detaching (SCSI 1:0:0:0) [32021.577507] sd 1:0:0:0: [sdb] Starting disk [32021.577526] sd 1:0:0:0: [sdb] START_STOP FAILED [32021.577527] sd 1:0:0:0: [sdb] [32021.577527] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [32021.577531] dpm_run_callback(): scsi_bus_resume_common+0x0/0x90 returns 262144 [32021.577534] PM: Device 1:0:0:0 failed to resume async: error 262144 [32021.580630] PM: resume of devices complete after 10931.128 msecs [32021.580720] PM: Finishing wakeup. [32021.583417] sd 1:...