Search results

Yes, I did update it to use UUID now. Was not aware that those were not stable. Learned something new.

Figured it out.... my usb external drive for some reason changed from /dev/sdc1 to /dev/sde1 and I had it in the /etc/fstab to mount at startup cause thats where I backup my VM's.

Updated to Proxmox 7.4-3 on 5.15 kernel. Then wanted to try 6.2 kernel since I have an Intel Arc Card. It boots into emergency mode Here's the kernel log if anyone can help. I had to reboot into 5.15 kernel to get back to operation. System is HP Z640 tower with two Intel Xeon CPU E5-2678 v3...

Question @avw , can I still use the display option inside proxmox to get to the GUI if I don't want to be using the nvidia card for the GUI?

IT WORKED!!!!!!!!!!! Thank you for the help guys! Would the 5.11 kernel still be good idea to upgrade to?

Oh dang lol I thought I had it in there. I'll try that now. Is there any issues with upgrading to 5.11 kernel? Risks? Thanks.

Yes they are in my /etc/kernel/cmdline. Here's the output. root@pve:~# cat /proc/cmdline initrd=\EFI\proxmox\5.4.128-1-pve\initrd.img-5.4.128-1-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs rootdelay=10 quiet iommu=on iommu=pt video=vesafb:off video=efifb:off Yes I ran update-initramfs -u and...

Yeah I've tried the link there. Think its a different motherboard. Nothing shows up when I run the command. On your command, I only get one IOMMU group with a long list of devices. Yeah I checked /cat/proc/cmdline and its the same as /etc/kernel/cmdline as far as arguments go. I'm not sure...

@oguz , any new thoughts or things to try?

Yes, thanks for getting me this far ;) Did that and rebooted. Still no IOMMU groups listed. And when I run the dmesg command I still see what I pasted above. Yes, I remember it was set to enable. There wasn't an AUTO option. Wonder if I need to reach out to HP and mention there's a bug with...

Yes Yes Yes This worked actually. It rebooted and came back up from web console. No video out to monitor which I assume is because the video=vesafb:off. Here's the output for this. root@pve:~# cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the...

I noticed this yesterday in the kernel logs as I was trying to find out what was happening when it would get stuck booting. Never found that but found this error repeating a bunch after the machine has booted up fine. It is doing it with the GPU and GPU audio device. Aug 2 13:43:11 pve kernel...

Yes still boots fine. Checked all that and it was set to on as before. I'm on a HP Z640 workstation with a dual socket motherboard and E5-2678 v3. And didn't mention this before but trying to pass through a Nvidia 1080 card.

Updated the BIOS to latest one for this year and still stuck on "Reading all physical volumes...". I thought maybe it was working when the cursor went away thinking that the gpu wasn't loaded like I assume it shouldn't be once booting. Verified in BIOS that VT-d is enabled. At a loss on what...

Yeah, so if I remove the IOMMU after booting into a Ubuntu 20.04 live USB and editing it (import zfs, mount partitions etc), it boots back up again. But even if I just add rootdelay=10 to the cmdline file it still hangs at that point. So I had to use 21.04 Ubuntu to be able to import the rpool...

Hey oguz, Thanks for the reply. Output for proxmox-boot-tool status just states UFEI. Doesn't mention grub or systemd-boot. I assume its systemd-boot based on what the docs state and what my boot up screen looks like. root@pve:/etc/kernel# proxmox-boot-tool status Re-executing...

Hey all, Have a HP Z640 machine and proxmox 6.4-13 installed. I installed 6.3 at first from ISO but with UEFI option so I assume I am on systemd-boot. I have been trying to get IOMMU enabled and at first I was using the guide and doing all grub commands because I was unaware that I was on...

Yes I am aware and which is why I figured it's systemd-boot, based on the screenshot it shows that's the same menu I have. But as I said, I changed things in the grub config and it took the rootdelay=10 boot argument. So unless I'm not understanding how the boot works and it still uses grub even...

Did you set your boot options in /etc/default/grub or did you do it in /etc/kernel/cmdline? From the guide, it mentioned to use the latter since it boots systemd-boot instead of grub. Whats weird is, I had to set in the grub config file rootdelay=10 for my zfs partition to load correctly. Yet it...

So mine never booted. I had to go into a ubuntu live image and reset my /etc/kernel/cmdline file back to default. I can't figure out why it is booting with systemd-boot but uses the grub config file in /etc/default/grub. I guess I will need to make a post about this and stop hijacking yours haha.