Hi. Noob here.
Thought I'd try out Proxmox for my home server, mainly PLEX and Samba. When the machine isn't doing anything else, it runs Folding@Home jobs. The wrinkle is the NVIDIA card needed by PLEX, F@H, and ffmpeg. I have all this running on an Ubuntu system. I wanted a machine with the AES instructions, so I picked up an HP ProLiant ml350e Gen 8 v2. This is the target. I'm following these directions to install the NVIDIA card. The upshot is I edit /etc/default/grub.cfg to pass some kernel parameters; I don't think anything else here is important right now.
The ProLiant system does not support EFI. The Proxmox installer ran and the system boots, presumably using GRUB. I *guess* some magic in the MBR to points the system at the GRUB that lives down the /dev/sda2/EFI/BOOT directory tree the installer made. But it's just a guess. It's also a bit confusing, but noob.
It goes sideways here:
The directory structure on the /boot partition evidently doesn't match what the update-grub script is expecting.
So I went hunting to see if there was some tool other than update-grub I should be using. I found this in the Proxmox wiki leading me to believe update-grub should work.
What have I missed?
Thought I'd try out Proxmox for my home server, mainly PLEX and Samba. When the machine isn't doing anything else, it runs Folding@Home jobs. The wrinkle is the NVIDIA card needed by PLEX, F@H, and ffmpeg. I have all this running on an Ubuntu system. I wanted a machine with the AES instructions, so I picked up an HP ProLiant ml350e Gen 8 v2. This is the target. I'm following these directions to install the NVIDIA card. The upshot is I edit /etc/default/grub.cfg to pass some kernel parameters; I don't think anything else here is important right now.
Preliminaries
The ProLiant system does not support EFI. The Proxmox installer ran and the system boots, presumably using GRUB. I *guess* some magic in the MBR to points the system at the GRUB that lives down the /dev/sda2/EFI/BOOT directory tree the installer made. But it's just a guess. It's also a bit confusing, but noob.
Code:
root@homeserver:~# pveversion
pve-manager/8.2.2/9355359cd7afbae4 (running kernel: 6.8.4-2-pve)
root@homeserver:~# efibootmgr -v
EFI variables are not supported on this system.
root@homeserver:~# lsblk --output NAME,TYPE,FSTYPE,LABEL,SIZE
NAME TYPE FSTYPE LABEL SIZE
sda disk 465.8G
├─sda1 part 1007K
├─sda2 part vfat 1G
└─sda3 part LVM2_member 464.8G
├─pve-swap lvm swap 8G
├─pve-root lvm ext4 96G
├─pve-data_tmeta lvm 3.4G
│ └─pve-data lvm 337.9G
└─pve-data_tdata lvm 337.9G
└─pve-data lvm 337.9G
root@homeserver:~# pveversion
pve-manager/8.2.2/9355359cd7afbae4 (running kernel: 6.8.4-2-pve)[
root@homeserver:~# mount /dev/sda2 /boot
root@homeserver:~# ls -la /boot
total 12
drwxr-xr-x 3 root root 4096 Dec 31 1969 .
drwxr-xr-x 18 root root 4096 Nov 12 02:57 ..
drwxr-xr-x 4 root root 4096 Nov 12 02:57 EFIIt goes sideways here:
Code:
root@homeserver:~# update-grub
/usr/sbin/grub-mkconfig: 270: cannot create /boot/grub/grub.cfg.new: Directory nonexistentThe directory structure on the /boot partition evidently doesn't match what the update-grub script is expecting.
So I went hunting to see if there was some tool other than update-grub I should be using. I found this in the Proxmox wiki leading me to believe update-grub should work.
What have I missed?