Repost: Proxmox 8.4.13 disk mount question, LSI 9300-16i

[UpAndRun]

I am still new to this site, I posted this to the wrong thread.

I need some help for storage and disk id, hope some one could help me.

I have an old motherbiard: msi z270 sli plus. The motherboard bios is locked for gaming performance I can not do pci device passthrough.

I have an LSI 9300-16i card in it mode, I have one sata 500gb drive, 2 nvme 256GB installed on the motherboard , 4 sas disk connected to the LSI card.

When I start up, I see this in proxmox GUI (on 300GB sas drive is missing):

my "ls /dev/disk/by-id" shows this (scsi-35000c5008fbe8663 not showing up in the above picture):

Is there something wrong? Can I still passthrough the disk to truenas if I want to?

Thank you for taking time looking at my questions.

 

[Onslow]

Please post the output of lsblk in "CODE" or "SPOILER" tags - to preserve the formatting.

 

[UpAndRun]

Please post the output of lsblk in "CODE" or "SPOILER" tags - to preserve the formatting.

I am still new to this forum, are you asking for no screenshots?

Thanks.

 

[Onslow]

Screenshots sometimes are necessary, like when someone describes an issue of the GUI.

For textual data - text is better, so that we can search for errors / details, copy & paste them and to quote particular details.
For instance: if I'd have to read these long strings of characters and numbers on your screenshots - to type them in a response, I would give up

 

[UpAndRun]

That makes sense. Here is my "code":

root@proxomox:~# ls /dev/disk/by-id/
ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part3
ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part2 scsi-35000c5008ebc0c57
ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777-part9 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part3 scsi-35000c5008fbe8663
nvme-eui.0000000001000000e4d25c7dba9b4d01 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D-part1 scsi-35000c50095893543
nvme-eui.0000000001000000e4d25c7dba9b4d01-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D-part2 scsi-35000c50095aea9d3
nvme-eui.0000000001000000e4d25c7dba9b4d01-part2 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D-part3 wwn-0x5000c5008ebc0c57
nvme-eui.0000000001000000e4d25c7dba9b4d01-part3 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D wwn-0x5000c5008fbe8663
nvme-eui.0000000001000000e4d25ce7579f4d01 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D_1 wwn-0x5000c50095893543
nvme-eui.0000000001000000e4d25ce7579f4d01-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D_1-part1 wwn-0x5000c50095aea9d3
nvme-eui.0000000001000000e4d25ce7579f4d01-part2 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D_1-part2 wwn-0x50014ee2ab8117e4
nvme-eui.0000000001000000e4d25ce7579f4d01-part3 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D_1-part3 wwn-0x50014ee2ab8117e4-part1
nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part1 wwn-0x50014ee2ab8117e4-part9
nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part2

 

[Onslow]

That makes sense. Here is my "code":

root@proxomox:~# ls /dev/disk/by-id/
ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part3
...

No, it isn't ;-(.

THIS is in the CODE tags:

root@proxomox:~# ls /dev/disk/by-id/
ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777        nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part3

And having lsblk output could help us to understand the issue, as I wrote .