Hi, Robert Moskowitz wrote: > sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK This is a command transport failure of the lowlevel driver. I know such effects from dying USB boxes with optical drives (having SATA controllers). https://www.tldp.org/HOWTO/archived/SCSI-Programming-HOWTO/SCSI-Programming-HOWTO-21.html "21.4 Host codes The following host codes are defined in drivers/scsi/scsi.h. They are set by the kernel driver. [...] 0x01 | DID_NO_CONNECT | Couldn't connect before timeout period 0x02 | DID_BUS_BUSY | BUS stayed busy through time out period 0x03 | DID_TIME_OUT | TIMED OUT for other reason [...] 21.5 Driver codes The midlevel driver categorizes the returned status from the lowlevel driver based on the sense key from the device. [...] [...] 0x00 | DRIVER_OK | No error " There is no "sense key from the device", because the SCSI command could not be transferred, according to hostbyte. Despite the archived state of the SCSI HOWTO, this aspect is still very present in the kernel: https://elixir.bootlin.com/linux/v5.6/ident/DID_NO_CONNECT Clicking on some of the links there leads to bail-out code of drivers. Have a nice day :) Thomas _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
