Passing through sas drives not working [HPE]

chipbreak

New Member
Aug 7, 2021
6
0
1
25
Canada
first post, i hope Ive included enough info

system specs:
HPE dl380p gen8
ibm m5110 (9207-8i)
120gb sata sdd
2x 4tb seagate sas hdd
3tb wd black sata hdd

Goal: to pass the 2 sas hdd and 1 sata hdd through proxmox to a vm

Results : sata hdd passes through, sas hdd not found

Gui: sas device show up as device /dev/sdd/ & /dev/sde, type = unknown, smart = ok

GUi Test: zfs->create zfs: drives shows up as available.
Result: # /sbin/zpool create -o ashift=12 backups mirror /dev/disk/by-id/scsi-35000c50058fb9147 /dev/disk/by-id/scsi-35000c50058fbc697
cannot label 'sdd': failed to detect device partitions on '/dev/sdd1': 19
TASK ERROR: command '/sbin/zpool create -o 'ashift=12' backups mirror /dev/disk/by-id/scsi-35000c50058fb9147 /dev/disk/by-id/scsi-35000c50058fbc697' failed: exit code 1


Ssh test to pass through drive to vm :

apt-get install lshw the to drives
lshw -class disk -class storage

cd /dev/disk/by-id
ls -l
#results:
lrwxrwxrwx 1 root root 9 Aug 23 21:39 ata-ST3000DM001-9YN166_W1F2J0JM -> ../../sdc
lrwxrwxrwx 1 root root 10 Aug 23 21:39 ata-ST3000DM001-9YN166_W1F2J0JM-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Aug 23 21:39 ata-ST3000DM001-9YN166_W1F2J0JM-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 9 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20398D803569 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20398D803569-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20398D803569-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20398D803569-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20399C803261 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20399C803261-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20399C803261-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Aug 23 21:36 ata-WDC_WDS120G2G0A-00JH30_20399C803261-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 12 Aug 23 21:36 lvm-pv-uuid-NmRiLR-pcU5-jOdu-B8fX-JdBs-c4wo-xQAyFj -> ../../zd16p3
lrwxrwxrwx 1 root root 9 Aug 23 21:36 scsi-35000c50058fb9147 -> ../../sdd
lrwxrwxrwx 1 root root 9 Aug 23 21:36 scsi-35000c50058fbc697 -> ../../sde

lrwxrwxrwx 1 root root 9 Aug 23 21:36 usb-HP_iLO_LUN_00_Media_0_000002660A01-0:0 -> ../../sdf
lrwxrwxrwx 1 root root 10 Aug 23 21:36 usb-HP_iLO_LUN_00_Media_0_000002660A01-0:0-part1 -> ../../sdf1
lrwxrwxrwx 1 root root 9 Aug 23 21:36 wwn-0x5000c50058fb9147 -> ../../sdd
lrwxrwxrwx 1 root root 9 Aug 23 21:36 wwn-0x5000c50058fbc697 -> ../../sde
lrwxrwxrwx 1 root root 9 Aug 23 21:39 wwn-0x5000c5006002fecd -> ../../sdc
lrwxrwxrwx 1 root root 10 Aug 23 21:39 wwn-0x5000c5006002fecd-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Aug 23 21:39 wwn-0x5000c5006002fecd-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 9 Aug 23 21:36 wwn-0x5001b448bbc6452d -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6452d-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6452d-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6452d-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Aug 23 21:36 wwn-0x5001b448bbc6cbf5 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6cbf5-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6cbf5-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Aug 23 21:36 wwn-0x5001b448bbc6cbf5-part3 -> ../../sdb3

#sas drive 1 passing through to vm
qm set 526 -scsi10 /dev/disk/by-id/scsi-35000c50058fb9147
#Result:
update VM 526: -scsi10 /dev/disk/by-id/scsi-35000c50058fb9147
qemu-img: Could not open '/dev/disk/by-id/scsi-35000c50058fb9147': Could not read image for determining its format: Input/output error
could not parse qemu-img info command output for '/dev/disk/by-id/scsi-35000c50058fb9147'
volume /dev/disk/by-id/scsi-35000c50058fb9147 does not exist

#sas drive 2
qm set 526 -scsi11 /dev/disk/by-id/scsi-35000c50058fbc697

update VM 526: -scsi10 /dev/disk/by-id/scsi-35000c50058fbc697
qemu-img: Could not open '/dev/disk/by-id/scsi-35000c50058fbc697': Could not read image for determining its format: Input/output error
could not parse qemu-img info command output for '/dev/disk/by-id/scsi-35000c50058fbc697'
volume /dev/disk/by-id/scsi-35000c50058fbc697 does not exist

#wd hd
qm set 526 -scsi12 /dev/disk/by-id/ata-ST3000DM001-9YN166_W1F2J0JM
#result:
update VM 526: -scsi12 /dev/disk/by-id/ata-ST3000DM001-9YN166_W1F2J0JM



any help getting proxmox to pass through the drives and show more smart would be apricated
 
Last edited:

chipbreak

New Member
Aug 7, 2021
6
0
1
25
Canada
i reinstalled proxmox repeated steps.

i was able to pass the first sas disk through surprisingly, but the second sas drive gave the same error:

qemu-img: Could not open '/dev/disk/by-id/scsi-35000c50058fbc697': Could not read image for determining its format: Input/output error
could not parse qemu-img info command output for '/dev/disk/by-id/scsi-35000c50058fbc697'
volume /dev/disk/by-id/scsi-35000c50058fbc697 does not exist
 

neiion

Member
Apr 3, 2017
11
3
23
43
Hi
Sorry for resurrecting this old post but did you ever get it resolved? i have a simular issue going on currently. thanks
 

LnxBil

Famous Member
Feb 21, 2015
6,347
788
163
Saarland, Germany
Best solution in such scenarios is pcie passthrough the hba directly (so you need an extra HBA if you share the HBA with other disks).
 

neiion

Member
Apr 3, 2017
11
3
23
43
@LnxBil thanks for the reply, unfortunately i am going in the other direction , i am migrating my drives from external netapp disk shelf (with HBA connection attached to truenas vm) into truenas vm with disks directly passed through, i am aware of the downsides of doing this ,SMART issues etc if i get a fix for my issue i will post it here. thanks
 

leesteken

Famous Member
May 31, 2020
1,744
355
88
qm help states that the command is qm set -scsi[n] <volume>, but the Wiki, the manual and man qm state that the command is qm set --scsi[n] <volume> with two minus symbols. Can you try qm set 526 --scsi10 /dev/disk/by-id/scsi-35000c50058fb9147 instead of your original command?
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!