Proxmox not detecting second M2 SSD

Payee6908

New Member
Jan 14, 2024
11
0
1
Hi all,

I'm having an issue with Proxmox reading a second 2TB SSD.

I have 2 M2 drives:
  • 1 x 2tb Crucial SSD and
  • 1 x 2tb SanDisk Extreme SSD
Proxmox is installed on the Crucial SSD and boots fine.

When i run command below, it seems Proxmox isn't recognizing the new hardware.
The BIOS recognizes the new hard drive fine.

lsblk |awk 'NR==1{print $0" DEVICE-ID(S)"}NR>1{dev=$1;printf $0" ";system("find /dev/disk/by-id -lname \"*"dev"\" -printf \" %p\"");print "";}'|grep -v -E 'part|lvm'


I have read a few forums, but none have really solved my issue.
I basically want to create a new VM and use this entire drive for this purpose.

Any assistance appreciated
 

Attachments

  • 2024-08-19_17-02-38.png
    2024-08-19_17-02-38.png
    40.2 KB · Views: 13
Running lsblk returns the below.
These are mostly VM HD space that are running.



root@proxmox:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part /boot/efi
└─nvme0n1p3 259:3 0 1.8T 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 15.9G 0 lvm
│ └─pve-data-tpool 252:4 0 1.7T 0 lvm
│ ├─pve-data 252:5 0 1.7T 1 lvm
│ ├─pve-vm--100--disk--0 252:6 0 200G 0 lvm
│ ├─pve-vm--101--disk--0 252:7 0 4M 0 lvm
│ ├─pve-vm--101--disk--1 252:8 0 200G 0 lvm
│ ├─pve-vm--101--disk--2 252:9 0 4M 0 lvm
│ ├─pve-vm--102--disk--0 252:10 0 200G 0 lvm
│ ├─pve-vm--103--disk--0 252:11 0 200G 0 lvm
│ ├─pve-vm--108--disk--0 252:12 0 4M 0 lvm
│ ├─pve-vm--108--disk--1 252:13 0 500G 0 lvm
│ ├─pve-vm--108--disk--2 252:14 0 4M 0 lvm
│ ├─pve-vm--107--disk--0 252:15 0 4M 0 lvm
│ ├─pve-vm--107--disk--1 252:16 0 100G 0 lvm
│ ├─pve-vm--107--disk--2 252:17 0 4M 0 lvm
│ ├─pve-vm--109--disk--0 252:18 0 100G 0 lvm
│ ├─pve-vm--109--disk--1 252:19 0 4M 0 lvm
│ ├─pve-vm--110--disk--0 252:20 0 4M 0 lvm
│ ├─pve-vm--110--disk--1 252:21 0 100G 0 lvm
│ ├─pve-vm--110--disk--2 252:22 0 4M 0 lvm
│ ├─pve-vm--111--disk--0 252:23 0 100G 0 lvm
│ ├─pve-vm--105--disk--0 252:24 0 100G 0 lvm
│ ├─pve-vm--104--disk--0 252:25 0 100G 0 lvm
│ ├─pve-vm--112--disk--0 252:26 0 100G 0 lvm
│ ├─pve-vm--113--disk--0 252:27 0 4M 0 lvm
│ ├─pve-vm--113--disk--1 252:28 0 100G 0 lvm
│ ├─pve-vm--113--disk--2 252:29 0 4M 0 lvm
│ ├─pve-vm--116--disk--0 252:30 0 100G 0 lvm
│ └─pve-vm--114--disk--0 252:31 0 200G 0 lvm
└─pve-data_tdata 252:3 0 1.7T 0 lvm
└─pve-data-tpool 252:4 0 1.7T 0 lvm
├─pve-data 252:5 0 1.7T 1 lvm
├─pve-vm--100--disk--0 252:6 0 200G 0 lvm
├─pve-vm--101--disk--0 252:7 0 4M 0 lvm
├─pve-vm--101--disk--1 252:8 0 200G 0 lvm
├─pve-vm--101--disk--2 252:9 0 4M 0 lvm
├─pve-vm--102--disk--0 252:10 0 200G 0 lvm
├─pve-vm--103--disk--0 252:11 0 200G 0 lvm
├─pve-vm--108--disk--0 252:12 0 4M 0 lvm
├─pve-vm--108--disk--1 252:13 0 500G 0 lvm
├─pve-vm--108--disk--2 252:14 0 4M 0 lvm
├─pve-vm--107--disk--0 252:15 0 4M 0 lvm
├─pve-vm--107--disk--1 252:16 0 100G 0 lvm
├─pve-vm--107--disk--2 252:17 0 4M 0 lvm
├─pve-vm--109--disk--0 252:18 0 100G 0 lvm
├─pve-vm--109--disk--1 252:19 0 4M 0 lvm
├─pve-vm--110--disk--0 252:20 0 4M 0 lvm
├─pve-vm--110--disk--1 252:21 0 100G 0 lvm
├─pve-vm--110--disk--2 252:22 0 4M 0 lvm
├─pve-vm--111--disk--0 252:23 0 100G 0 lvm
├─pve-vm--105--disk--0 252:24 0 100G 0 lvm
├─pve-vm--104--disk--0 252:25 0 100G 0 lvm
├─pve-vm--112--disk--0 252:26 0 100G 0 lvm
├─pve-vm--113--disk--0 252:27 0 4M 0 lvm
├─pve-vm--113--disk--1 252:28 0 100G 0 lvm
├─pve-vm--113--disk--2 252:29 0 4M 0 lvm
├─pve-vm--116--disk--0 252:30 0 100G 0 lvm
└─pve-vm--114--disk--0 252:31 0 200G 0 lvm
 
Nope, no SATA, only the 2 M2 drives

The motherboard is recognizing both drives, so the motherboard is fine.
I cant see the second M2 in promox at all
 
I cant see the second M2 in promox at all
Live boot the system with another plain Linux USB & see if it shows up in lsblk .

You don't provide HW details - but maybe somethings up with those PCI lanes. How do both m.2/s compare gen wise. Have you got other PCI(e) devices on the system? Have you (ever) tested that m.2 drive on another system.