FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s

[andrewchk]

Dear Mox expers,

I am a newbie setting up and trying Proxmox in my home lab with a Dell 730 / 256GB RAM / All SATA disks 1TB and 2TB.

I just took a look at the syslog and found some FAILED items in the list, however I have no idea what these mean? Any help will be appreciated.

---
Oct 23 01:10:31 pve kernel: scsi_io_completion_action: 4 callbacks suppressed
Oct 23 01:10:31 pve kernel: sd 0:0:5:0: [sdf] tag#89 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:31 pve kernel: sd 0:0:5:0: [sdf] tag#89 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:32 pve kernel: sd 0:0:14:0: [sdo] tag#186 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:32 pve kernel: sd 0:0:14:0: [sdo] tag#186 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:32 pve kernel: sd 0:0:3:0: [sdd] tag#95 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:32 pve kernel: sd 0:0:3:0: [sdd] tag#95 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:32 pve kernel: sd 0:0:12:0: [sdm] tag#65 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:32 pve kernel: sd 0:0:12:0: [sdm] tag#65 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:33 pve kernel: sd 0:0:10:0: [sdk] tag#131 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:33 pve kernel: sd 0:0:10:0: [sdk] tag#131 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:33 pve kernel: sd 0:0:8:0: [sdi] tag#137 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:33 pve kernel: sd 0:0:8:0: [sdi] tag#137 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:33 pve kernel: sd 0:0:6:0: [sdg] tag#82 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:33 pve kernel: sd 0:0:6:0: [sdg] tag#82 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:33 pve kernel: sd 0:0:4:0: [sde] tag#143 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:33 pve kernel: sd 0:0:4:0: [sde] tag#143 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:34 pve kernel: sd 0:0:13:0: [sdn] tag#88 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:34 pve kernel: sd 0:0:13:0: [sdn] tag#88 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:34 pve kernel: sd 0:0:2:0: [sdc] tag#169 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:34 pve kernel: sd 0:0:2:0: [sdc] tag#169 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:10:54 pve kernel: scsi_io_completion_action: 4 callbacks suppressed
Oct 23 01:10:54 pve kernel: sd 0:0:2:0: [sdc] tag#109 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:10:54 pve kernel: sd 0:0:2:0: [sdc] tag#109 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Oct 23 01:11:13 pve kernel: sd 0:0:3:0: [sdd] tag#86 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Oct 23 01:11:13 pve kernel: sd 0:0:3:0: [sdd] tag#86 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00

 

[bbgeek17]

I just took a look at the syslog and found some FAILED items in the list, however I have no idea what these mean? Any help will be appreciated.

PVE uses Debian with Ubuntu derived kernel as underlying OS/Kernel. These messages are generated at Kernel level, i.e. they are not PVE specific.
Plug them into google and review the results and suggested solutions.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[andrewchk]

PVE uses Debian with Ubuntu derived kernel as underlying OS/Kernel. These messages are generated at Kernel level, i.e. they are not PVE specific.
Plug them into google and review the results and suggested solutions.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

@bbgeek17 Thank you for your prompt feedback. I've been searching over Google and found a long list, however, most of them also included some ERROR underneath and I found no one mentioned this Failed message/statement.

 

[kuroiookami]

Same Dell 730xd and same messages. The disks are fine, smartctl -t runs without errors. Appears if you go to the disks tab in the web interface.

Jun 26 12:59:03 pbs1 kernel: sd 0:0:5:0: [sdf] tag#688 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:5:0: [sdf] tag#688 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:3:0: [sdd] tag#694 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:3:0: [sdd] tag#694 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:1:0: [sdb] tag#700 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:1:0: [sdb] tag#700 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:13:0: [sdi] tag#715 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:13:0: [sdi] tag#715 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:6:0: [sdg] tag#642 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:6:0: [sdg] tag#642 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:4:0: [sde] tag#648 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:4:0: [sde] tag#648 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:2:0: [sdc] tag#609 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:2:0: [sdc] tag#609 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:0:0: [sda] tag#721 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:0:0: [sda] tag#721 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Jun 26 12:59:03 pbs1 kernel: sd 0:0:12:0: [sdh] tag#654 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Jun 26 12:59:03 pbs1 kernel: sd 0:0:12:0: [sdh] tag#654 CDB: ATA command pass through(16) 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00

 

[kuroiookami]

I solved the problem.
If anyone else encounters this, update the firmware of the RAID controller (in my case it is PERC H730 Mini (Embedded))
After updating the BIOS to 2.19.0 and H730 to 25.5.9.0001, the messages no longer appear!

 

[Andreaux]

I solved the problem.
If anyone else encounters this, update the firmware of the RAID controller (in my case it is PERC H730 Mini (Embedded))
After updating the BIOS to 2.19.0 and H730 to 25.5.9.0001, the messages no longer appear!

Thanks for the tip!!!!
I'm having the exact same issue, also with a DELL R730XD (not running Proxmox, but TrueNAS Scale... my other nodes have Proxmox though ).
My BIOS and Controller FW are not recent as well.
Currently updating them, I'll check back after a while with how it went.

EDIT: I see no errors so far since I updated both the BIOS and the Controller Firmware yesterday. Fingers crossed it stays this way.