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

U

UpAndRun

New Member
Jan 9, 2025
13
0
1
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):

1759597551364.png



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

1759597826505.png



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.
 
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 :p
 
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
 
UpAndRun said:
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
...
Click to expand...
No, it isn't ;-(.

THIS is in the CODE tags:

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

And having lsblk output could help us to understand the issue, as I wrote :).
 
I thought you meant text. Now I see a code, sorry and thank you!

I only see 3 279.4G disk, what did I do wrong?

Code: 
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 279.4G  0 disk
sdb           8:16   0 279.4G  0 disk
sdc           8:32   0 279.4G  0 disk
sdd           8:48   0     0B  0 disk
sde           8:64   0 465.8G  0 disk
├─sde1        8:65   0 465.8G  0 part
└─sde9        8:73   0     8M  0 part
zd0         230:0    0     4M  0 disk
zd16        230:16   0    32G  0 disk
├─zd16p1    230:17   0     1M  0 part
└─zd16p2    230:18   0    32G  0 part
zd32        230:32   0    75G  0 disk
├─zd32p1    230:33   0   200M  0 part
├─zd32p2    230:34   0    16M  0 part
├─zd32p3    230:35   0  74.1G  0 part
└─zd32p4    230:36   0   711M  0 part
zd48        230:48   0     1M  0 disk
nvme0n1     259:0    0 238.5G  0 disk
├─nvme0n1p1 259:2    0  1007K  0 part
├─nvme0n1p2 259:3    0     1G  0 part
└─nvme0n1p3 259:4    0 237.5G  0 part
nvme1n1     259:1    0 238.5G  0 disk
├─nvme1n1p1 259:5    0  1007K  0 part
├─nvme1n1p2 259:6    0     1G  0 part
└─nvme1n1p3 259:7    0 237.5G  0 part
 
Last edited:
UpAndRun said:
sdd 8:48 0 0B 0 disk
Click to expand...
You might not doing anything wrong :) .

I wonder what is this above sdd disk sized 0 bytes...
If these four disks are connected to that LSI card, I would check if the card has any "BIOS" / setup menu that can be entered into during the bootup of the server.
And whether this fourth disk is presented in that menu.
 
Onslow said:
You might not doing anything wrong :) .

I wonder what is this above sdd disk sized 0 bytes...
If these four disks are connected to that LSI card, I would check if the card has any "BIOS" / setup menu that can be entered into during the bootup of the server.
And whether this fourth disk is presented in that menu.
Click to expand...
Thank you very much. The bios shows me the same thing: only 3 disks. I then tried swap all different cable, identified one of the cable is not working.

Really appreciate your help.
 
You must log in or register to reply here.
Top Bottom