
Of course the BIOS is pretty old, so it doesn't recognize the NVMe drive, but Ubuntu installation from a USB drive does.
#Sccm samsung nvme driver boot image plus#
I have used Ubuntu Server 20.04.3 LTS on HP Z800 Workstation (similar to HP Z400 Workstation and HP Z600 Workstation) with INTEL SSDSC2KW24 SATA SSD and Samsung NVMe M.2 970 EVO Plus mounted to PCIe Asus Hyper M.2 X4 Mini. the first is mounted as /home, the second is mounted as / for the OS. Make sure that the SATA drive is the boot device. Set a partition on the NVME device as /, and /dev/sdb3 set to /boot again. Run the installer again, with the same settings as the first time.Optionally set up another partition (could even be on the NVME device) for /home.This system directory is here mainly as a backup in case the NVME drive dies. In the installer set up to boot from the SATA drive (creates the bios_grub & EFI partitions), then create a 500MB (maybe less?) partition for /boot, and another partition for the OS.If there's already an EFI partition on any device, delete it.With GPartEd erase the SATA drive and create a GPT partition table on it.
#Sccm samsung nvme driver boot image install#
During install you must choose to do "SOMETHING ELSE" when installing and tell the installer to mount your previously defined /boot partition and to install grub onto that same drive.Īfter a couple of weeks of screwing around (make sure you are booting off the right device!), I found the following worked for me: Your NVMe drive mus be GPT partitioned as well. You MUST include the legacy_boot on the /boot partition (partition 1), and bios_grub on the unknown partition 2. Number Start End Size File system Name Flags Sector size (logical/physical): 512B/512B The "boot" drive is SATA and obviously seen and bootable through BIOS with a GPT Partition and scheme like so: Model: ATA Samsung SSD 850 (scsi) I'll briefly explain, while the exact and thorough steps can be found below via link to the official ubuntu forums.īasically you have to locate your /boot on a seperate drive along with installing grub to the same drive. It was found that the fix required multiple steps to get working correctly.
