search for: driverbyt

...tem 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 0:0:0:0:...

...Dec 15 01:57:53 test.example.com multipathd: 360000970000196801239533037303434: Recovered to normal mode Dec 15 01:57:53 test.example.com multipathd: 360000970000196801239533037303434: remaining active paths: 1 Dec 15 01:57:53 test.example.com kernel: sd 1:0:2:20: [sdeu] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [root at test log]# multipath -ll |grep -i fail |- 1:0:0:15 sdq 65:0 failed ready running - 3:0:0:15 sdai 66:32 failed ready running We are using default multipath.conf HBA driver version 8.07.00.26.06.8-k HBA model QLogic Corp. ISP8324-based 16Gb Fibre Channel to PCI Expres...

...l: [121567.210047] ata7: failed to resume link (SControl 1) Mar  9 23:57:43 ftp2 kernel: [121567.210068] ata7: SATA link down (SStatus 0 SControl 1) Mar  9 23:57:43 ftp2 kernel: [121567.210080] ata7.00: disabled Mar  9 23:57:43 ftp2 kernel: [121567.210103] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar  9 23:57:43 ftp2 kernel: [121567.210109] sd 6:0:0:0: [sdc]  Sense Key : Aborted Command [current] [descriptor] Mar  9 23:57:43 ftp2 kernel: [121567.210117] Descriptor sense data with sense descriptors (in hex): Mar  9 23:57:43 ftp2 kernel: [121567.210120]         72 0b 00 00 00 00...

> On Jan 3, 2017, at 2:59 PM, lakhera2017 <plakhera at salesforce.com> wrote: > > |- 1:0:0:15 sdq 65:0 failed ready running > - 3:0:0:15 sdai 66:32 failed ready running Does the same SAN target fail each time? What brand/model/firmware SAN switch is between initiator and target? Does the HBA show any SCSI aborts?

...scsid: Kernel reported iSCSI connection 2:0 error (1022 - Invalid or unknown error code) state (3) Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery (1 attempts) Repeated a few times, until eventually Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK Apr 4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB: Apr 4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00 Apr 4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, sector 31442920 Apr 4 11:19:44 funk kernel: [ 658.127596] sd 7:0:0:1: [sdd] Apr 4 11:19:44 fu...

...t;> 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 driver...

...gt; 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 driv...

...or unknown error code) state (3) >> Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery (1 >> attempts) >> >> Repeated a few times, until eventually >> >> >> Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> Apr 4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB: >> Apr 4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00 >> Apr 4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, sector >> 31442920 >> Apr 4 11:19:44 funk kernel: [ 658....

...[ 39.024284] journal commit I/O error [ 39.024330] journal commit I/O error [ 39.024358] journal commit I/O error [ 39.024384] journal commit I/O error [ 39.024432] journal commit I/O error [ 39.024481] journal commit I/O error [ 45.749997] sd 0:0:0:0: [sda] Result: hostbyte=3DDID_OK driverbyte=3DD= RIVER_SENSE,SUGGEST_OK [ 45.750008] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]=20 [ 45.750012] sd 0:0:0:0: [sda] Add. Sense: Internal target failure [ 45.750017] end_request: I/O error, dev sda, sector 721945599 [ 45.750079] Buffer I/O error on device dm-0, logical block 9...

...2:0 error > (1022 - Invalid or unknown error code) state (3) > Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery (1 > attempts) > > Repeated a few times, until eventually > > > Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > Apr 4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB: > Apr 4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00 > Apr 4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, sector > 31442920 > Apr 4 11:19:44 funk kernel: [ 658.127596] sd 7:0:0:1:...

...kernel: [25786.227670] (ocfs2rec,14787,13):__ocfs2_recovery_thread:1359 ERROR: Volume requires unmount. Oct 30 02:01:01 server177 kernel: [25786.227696] sd 4:0:0:0: [sdc] Unhandled error code Oct 30 02:01:01 server177 kernel: [25786.227707] sd 4:0:0:0: [sdc] Result: hostbyte=DID_TRANSPORT_FAILFAST driverbyte=DRIVER_OK Oct 30 02:01:01 server177 kernel: [25786.227726] sd 4:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 13 40 00 00 08 00 Oct 30 02:01:01 server177 kernel: [25786.227792] end_request: recoverable transport error, dev sdc, sector 4928 Oct 30 02:01:01 server177 kernel: [25786.227812] (ocfs2rec,14787...

...sing 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.54...

...tem 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 0:0:0:0:...

...GB 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 >...

...SD 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 &gt...

...Apr 4 11:18:44 funk iscsid: connection2:0 is operational after >>> recovery (1 >>> attempts) >>> >>> Repeated a few times, until eventually >>> >>> >>> Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED >>> driverbyte=DRIVER_OK >>> Apr 4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB: >>> Apr 4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00 >>> Apr 4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, >>> sector >>> 31442920 >>> Ap...

...t;> 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 driver...

...2:0 error > (1022 - Invalid or unknown error code) state (3) > Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery > (1 attempts) > > Repeated a few times, until eventually > > > Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > Apr 4 11:19:44 funk kernel: sd 7:0:0:1: [sdd] CDB: > Apr 4 11:19:44 funk kernel: Write(10): 2a 00 01 df c7 e8 00 00 18 00 > Apr 4 11:19:44 funk kernel: blk_update_request: I/O error, dev sdd, > sector 31442920 > Apr 4 11:19:44 funk kernel: [ 658.127596] sd 7:0:0:1:...

...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: > >> hostb...

...s version v0.19 Write is done through an LVS volume formated with BTRFS of course; Mount options are : rw,noatime,nodiratime,compress=lzo,nospace_cache Dmesg gives me following error : [370517.203926] sd 0:0:15:0: [sdo] Device not ready [370517.203930] sd 0:0:15:0: [sdo]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [370517.203935] sd 0:0:15:0: [sdo]  Sense Key : Not Ready [current] [370517.203940] sd 0:0:15:0: [sdo]  ASC=0x4 <<vendor>> ASCQ=0xf2 [370517.203946] sd 0:0:15:0: [sdo] CDB: Write(10): 2a 00 00 00 6a 00 00 00 80 00 [370517.203955] end_request: I/O error, dev sdo, sector 271...