Getting error: SCSI error: "failed: Result: hostbyte=DID_NO_CONNECT ..."
Issue
-
Getting error:
kernel: sd h:c:t:l: [sdX] <scsi-command-name> failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 24 01:00:35 hostname kernel: sd 0:0:1:0: [sdb] Read(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
-
SAN access issue reported on RHEL server, observed following messages in
/var/log/messages
May 5 04:15:00 localhost kernel: sd 3:0:1:42: Unhandled error code May 5 04:15:00 localhost kernel: sd 3:0:1:42: SCSI error: return code = 0x00010000 May 5 04:15:00 localhost kernel: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
-
Getting error:
kernel: sd h:c:t:l: SCSI error: return code = 0x00010000
on RHEL 5:May 22 23:50:10 hostname kernel: Device sdb not ready. May 22 23:50:10 hostname kernel: end_request: I/O error, dev sdb, sector 0 May 22 23:50:10 hostname kernel: SCSI error : <0 0 2 14> return code = 0x10000
-
In device mapper multipath, some path fails and going down. Logs have many events logged for
tur checker reports path is down
andmultipath -ll
output show paths infailed/faulty
state:# multipath -ll sdb: checker msg is "tur checker reports path is down" mpath0 (2001738006296000b) dm-8 IBM,2810XIV [size=200G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=3][active] \_ 2:0:0:1 sda 8:0 [active][ready] \_ 2:0:1:1 sdb 8:16 [failed][faulty] <-- \_ 4:0:8:1 sdc 8:32 [active][ready] \_ 4:0:9:1 sdd 8:48 [active][ready]
-
We had A SAN director failure and the system got panicked due to
lpfc
lost devices.
Environment
- Red Hat Enterprise Linux (RHEL) 9
- Red Hat Enterprise Linux (RHEL) 8
- Red Hat Enterprise Linux (RHEL) 7
- Red Hat Enterprise Linux (RHEL) 6
- Red Hat Enterprise Linux (RHEL) 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.