VMware Cloud Community
J-H
Enthusiast
Enthusiast

SCSI errors on Intel S5000PSLROMB with SATA disks

I have several SCSI related messages in /var/log/vmkernel.

Is my assumption correct that these error messages are VMkernel messages that are not specific to the SCSI commands issued on behalf of one VM guest?

Where do I find a documentation about the SCSI error codes and the format of the VMKernel error messages?

The configuration is an Intel S5000PSLROMB motherboard with the hardware RAID controller SROMBSAS18E and SATA disks, Samsung HD501LJ (SpinPoint T) , attached. I know that only my motherboard and the RAID controller is supported but it is not supported to host a VMFS on SATA disks.

I tried to update the motherboard BIOS to version 79, but I had to go back to Version 74 because otherwise the megaraid_sas driver did not load during the server boot.

Do you know if these error messages would very likely also appear with other SATA disks that are sold as “RAID edition” like Seagate ST3500630NS (Barracuda ES, RAID-Edition).

##

Aug 13 14:42:02 pc3 vmkernel: 1:03:41:06.950 cpu5:1032)LinSCSI: 3616: Aborting cmds with world 1024, originHandle 0x52032d0, originSN 410281 from vmhba0:2:0

Aug 13 14:42:02 pc3 vmkernel: 1:03:41:06.950 cpu5:1032)LinSCSI: 3632: Abort failed for cmd with serial=410281, status=bad0001, retval=bad0001

Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)SCSI: 3731: AsyncIO timeout (5000); aborting cmd w/ sn 425475, handle 5639/0x52032d0

Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)LinSCSI: 3616: Aborting cmds with world 1024, originHandle 0x52032d0, originSN 425475 from vmhba0:2:0

Aug 13 14:42:56 pc3 vmkernel: 1:03:42:00.978 cpu5:1032)LinSCSI: 3632: Abort failed for cmd with serial=425475, status=bad0001, retval=bad0001

Aug 13 14:43:45 pc3 vmkernel: 1:03:42:50.096 cpu4:1113)VSCSI: 2604: Creating Virtual Device for world 1114 vscsi0:0

Aug 13 14:43:45 pc3 vmkernel: 1:03:42:50.096 cpu4:1113)SCSI: 1271: Set shares value for world 1114 to 0x3e8

Aug 13 14:43:54 pc3 vmkernel: 1:03:42:59.681 cpu3:1114)SCSI: 215: Invalid Opcode (0xa0)

Aug 13 14:57:12 pc3 vmkernel: 1:03:56:16.917 cpu3:1114)SCSI: 169: STOP_UNIT cmd issued to virt dis

Aug 13 14:57:22 pc3 vmkernel: 1:03:56:26.861 cpu2:1114)SCSI: 215: Invalid Opcode (0xa0)

Aug 13 14:58:13 pc3 vmkernel: 1:03:57:17.922 cpu1:1081)SCSI: 215: Invalid Opcode (0xa0)

##

Thanks.

0 Kudos
0 Replies