[SOLVED] Seems my LVM is gone after Upgrade to new Version

S

Sgaile

New Member
Aug 11, 2025
12
0
1
Hello,

Since I am not experienced Proxmox administrator or even user I am a bit at a loss on how to proceed:

The server I am using right now uses a PERC H330 RAID controller in HBA mode, although I am aware that this might be part of the issue. I have already seen parts of other threads mentioning that.

Short summary: I had to install PX7.4 (other versions did not detect any drives). While updating from 7.4 to 8.4 nothing seemed particularily off. On reboot i got the information, that Px gave up on waiting for root file system device. Including the following line:

/dev/mapper/pve-root does not exist.

Firstly I will happy with practically any help how I can fix that, thanks in advance.
 
Hi,
can you try booting with an older installed kernel?
 
Hey,
Thanks for your reply.
I managed to boot through my rescue boot (PX 7.4 USB Stick)
I tried remount the directories to fix that. However that did not fix it. Since this server as of now serves only as a test system I quickly reinstalled 7.4 and tried the upgrade process to 8.4 again this time keeping my original lvm file. I did not get the same error message this time I got this one (see screenshot).

While reinstalling I also put the system on ZFS RAID1 volume to have it redundant. I still assume its the RCs fault since installing higher versions (than 7.4) out of the box shows me "no drives detected" although BIOS recognizes 5 drives managed by BIOS.

If I wasted your time I apologize but as of now I am more certain that my hardware is at fault and not the soft.

-> RAID-controller is DELL PERC H330 set to HBA

EDIT: To answer your question, I tried booting with the older Kernel and this worked.
 

Attachments

  • Screenshot 2025-08-12 123404.png
    Screenshot 2025-08-12 123404.png
    85.6 KB · Views: 7
Last edited:
So after some more digging i stumbled over the following when running "dmesg | grep -e DMAR -e IOMMU~"

root@pam:~# dmesg | grep -e DMAR -e IOMMU~
[ 0.007398] ACPI: DMAR 0x000000007DFD2000 000090 (v01 DELL PE_SC3 00000002 DELL 00000001)
[ 0.007414] ACPI: Reserving DMAR table memory at [mem 0x7dfd2000-0x7dfd208f]
[ 0.215761] DMAR: Host address width 39
[ 0.215762] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.215765] DMAR: dmar0: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.215767] DMAR: RMRR base: 0x0000005e7f6000 end: 0x000000667fdfff
[ 0.215768] DMAR: RMRR base: 0x000000796ca000 end: 0x000000796e9fff
[ 0.215770] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 0
[ 0.215771] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.215772] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.218734] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 0.494958] DMAR: [Firmware Bug]: RMRR entry for device 02:00.0 is broken - applying workaround
The followup then confirmed, that 02:00.0 is in fact the the hardware RAID controller:
root@pam:~# lspci -nn |grep 02:00.0
02:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] [1000:005f] (rev 02)

This is also connected to the other thread that I recently opened.

Together with the fact that I am using an unsupported version of PX im not exactly surprised. I will try changing the RC and try reinstalling with a newer version.
 
leesteken said:
No but I wanted to mention this as a work-around or fix for you in later/future versions of Proxmox.
Click to expand...
Noted, thank you! I originally tried installing the latest release, however this one did not recognize my RAID card even tho it was set to passthrough (HBA). The only version I got "working" was 7.4-3 which came then with its own troubles as you saw in the 2 threads I posted. However as mentioned I think it is mostly my hardware that is at fault for the situation.

its a DELL PERC H330 and I found some other threads talking about it and causing issues. One thread mentioned to first install Debian and then to install Proxmox over that but ngl at this pont I will probably just get a proper HBA card and not bother with further troubleshooting. They are not expensive either.
 
That's of course also fine. I just wanted to give you a work-around/fix (no more troubleshooting needed) for your current setup. Maybe it will help other people with a similar issue in the future.
 
leesteken said:
That's of course also fine. I just wanted to give you a work-around/fix (no more troubleshooting needed) for your current setup. Maybe it will help other people with a similar issue in the future.
Click to expand...
Appreciated!
I tried adding the parameter. Unfortunately my machine completely froze up again and my GUI is unreachable. I will tinker a little more and see what I can do but if I cannot fix it it is allright :)!Thank you again for helping a newbie
 
That surprises me greatly.I would have though it would be simple and painless and not induce another round of troubleshooting. Sorry about that!
 
leesteken said:
That surprises me greatly.I would have though it would be simple and painless and not induce another round of troubleshooting. Sorry about that!
Click to expand...
Maybe I made a mistake. I followed information I found on the forum:

J

Post in thread 'Where to Add Intel_IOMMU=on and IOMMU=pt?'

Hi Nollimox, i'm far from an expert, but I think this is the way:

Enabling IOMMU​

  • Access the Proxmox VE console via an external monitor or through the Shell on the web management interface
  • Type and enter: nano /etc/default/grub
  • Add intel_iommu=on to GRUB_CMDLINE_LINUX_DEFAULT=”quiet” (See the screenshot below)
  • Write Out the settings and Exit
  • Run the command update-grub to finalize changes
  • Reboot your Vault

Somehow the screenshot went missing. Here is the link from where I got it.
Protectli
  • Like

Was that the wrong approach? And no worries there is no data currently on my px so nothing of value is lost. Im just trying to tinker i guess...
 
uzumo said:
If you don't need iommu, disabling it will probably get rid of the error.

https://docs.redhat.com/en/document...linux/7/html/7.2_release_notes/virtualization

Devices that use RMRRs are now excluded from IOMMU API domains

I think it's better to buy something that doesn't cause any problems.
Click to expand...
Yes @leesteken said that as well.

However i used the steps above to disable it. so i added the parameter intel_iommu=off instead.

but as mentioned that did nothing. My mainquestion in the last post was mostly: Did I even do the disabling right?

I also found no iommu settings in the bios.
 
If disabling Intel VT-D and AMD-Vi in the BIOS doesn't work, you should probably buy a new one.

Even if it did work, I think the drawbacks of disabling it would outweigh the benefits.

Did you update grub after setting it?

Code: 
    update-initramfs -u -k all
    proxmox-boot-tool refresh
    update-grub
 
Last edited:
uzumo said:
If disabling Intel VT-D and AMD-Vi in the BIOS doesn't work, you should probably buy a new one.

Even if it did work, I think the drawbacks of disabling it would outweigh the benefits.

Did you update grub after setting it?

Code: 
    update-initramfs -u -k all
    proxmox-boot-tool refresh
    update-grub
Click to expand...
Hello,

Yes I did. 'dmesg | grep iommu' also mentioned that it is disabled. Unfortunately the issue persists.
 
You must log in or register to reply here.
Top Bottom