Still unsure, if it’s just a detection issue, so this should provide a definitive answer:
$ sudo fdisk -l /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594
Disk /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SAMSUNG MZVLB512HBJQ-000L7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4DA337FE-0D65-4324-83C5-FF91F226EB8C
Device Start End Sectors Size Type
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part1 2048 1050623 1048576 512M EFI System
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part2 1050624 2549759 1499136 732M Linux filesystem
/dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part3 2549760 1000214527 997664768 475,7G Linux filesystem
You need to adjust the actual path in /dev/disk/by-id to match your device; this example output is from mine to illustrate the naming scheme. See this Redhat documentation article as to why it’s imporant to not use /dev/nvme* directly; TLDR: the names in /dev aren’t persistent across restarts.