Updated to 8.2 - DMA error

I had a similar error dmar error dma pte for vpfn 0xcf4de already set,
Saw another article on https://forum.openmediavault.org/ by searching just that it was the 3rd hit on Google.
Saw about disabling virtualization. I can't believe that actually worked.
Nothing in that error would have caused me to believe that virtualization was the issue.
If anyone else has insight on that, please enlighten me.
 
I had a similar error when installing Proxmox Backup Server on a Dell PowerEdge r410
dmar error dma pte for vpfn 0xcf4de already set,
Saw another article on https://forum.openmediavault.org/ by searching just that and it was the 3rd hit on Google.
Said about disabling virtualization. I can't believe that actually worked.
Nothing in that error would have caused me to believe that virtualization was the issue.
If anyone else has insight on that, please enlighten me.
 
Hi,

did you already try disabling the intel_iommu setting on the kernel commandline? The default for the setting changed in kernel 6.8 and your backtrace mentions IOMMU: https://pve.proxmox.com/wiki/Roadmap#8.2-known-issues
I had the exact same issue (DMAR ERROR) installing 8.3.1 on a 12 year old Dell R710.
Adding "nomodeset intel_iommu=off" to the installer kernel command line solved it for me.
https://pve.proxmox.com/wiki/Installation#nomodeset_kernel_param
Thanks for the hints. Now it is running like a charm :)
 
  • Like
Reactions: Gavino
I'm installing on an old Dell R710 as well. Thanks for the info! I selected "Install Proxmox Backup Server (Console)" and hit "e" to edit. At the line starting with "linux" I appended "nomodeset intel_iommu=off" to the end. Then Ctrl-x and I'm good. :) When editing the GRUB file, it's best to go to the line below the one that starts with "linux" and step backwards - otherwise it takes forever to step through the whole line.
 
  • Like
Reactions: Stefan Radman
This made it possible to install on my T410's without issue until I can replace them. So thankyou very much!
I'm installing on an old Dell R710 as well. Thanks for the info! I selected "Install Proxmox Backup Server (Console)" and hit "e" to edit. At the line starting with "linux" I appended "nomodeset intel_iommu=off" to the end. Then Ctrl-x and I'm good. :) When editing the GRUB file, it's best to go to the line below the one that starts with "linux" and step backwards - otherwise it takes forever to step through the whole line.
FYI, you can press the END key on your keyboard to jump directly to the end of the line instead of moving char by char
 
  • Like
Reactions: Gavino
I just upgrded HPE Microserver gen8 to new version (8.2), and got this after while with system stuck:

View attachment 67053


Any ideas?
I wanted to share a fix for the Proxmox Backup Server error encountered above

I’m running Proxmox Backup Server on a Dell PowerEdge R710, and I managed to resolve the issue by doing the following:

Add kernel parameters to GRUB
1. Open terminal and run:
nano /etc/default/grub

2. Find the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

3. Change it to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt intremap=off"

4. Save and exit

5. Run:
update-grub

6. Reboot:
reboot
 
Last edited:
  • Like
Reactions: Gavino
I also have an HPE ProLiant MicroServer Gen8 (with E3-1220L V2): it's not running Proxmox (yet) but I've been testing this hardware using vanilla Debian 12.11 (kernel v6.1.140-1).

OS is installed on a dedicated HDD connected to the B120i internal card with extra SFF-8087 cables, the four data HDDs are connected to a PCI Express SAS card: INSPUR 9211-8i (Avago BIOS v7.39.00.00).

In idling, the System was stable for days but the moment I've created an mdadm RAID1 over the 4 HDDs I've got multiple errors (full log attached):

kernel: DMAR: ERROR: DMA PTE for vPFN 0xf1f80 already set (to f1f80003 not 120d5c001)
Maybe it's the CPU operation (system was clearly idling before this RAID test), maybe it's the disk I/O.

I'm not attempting to highjack this thread, but I wanted to share that kernel 6.1 also has the issue on this hardware.

I'll try stressing the CPU without RAID to see if it triggers the issue or not.

I'll also try Debian 13 with kernel 6.12 and PVE 9 with kernel 6.14 to see how it performs.
 

Attachments

  • Like
Reactions: Kurgan
I am running the gen 8 with HP P420 HBA, with proxmox 9 (Debian 13 Trixie). I just came across this because i was getting same error. I did the grub changes suggested above, and have not seen the issue so far within 1 hour and over 3 terabytes of data transferred. Prior to disabling iommu, i had a lot of trouble setting up zfs pool, and could not reliably transfer even small amounts of data.
 
  • Like
Reactions: Kurgan
This is interesting indeed, please keep us informed. Did it run smoothly on Debian 11?
Sorry, I did not tried Debian 11: this is a new setup initiated with Debian 12.

I am running the gen 8 with HP P420 HBA, with proxmox 9 (Debian 13 Trixie). I just came across this because i was getting same error. I did the grub changes suggested above, and have not seen the issue so far within 1 hour and over 3 terabytes of data transferred. Prior to disabling iommu, i had a lot of trouble setting up zfs pool, and could not reliably transfer even small amounts of data.
Interesting, it (sadly) looks like I'm gonna have the same issue without disabling iommu :'(
 
Hello everyone,

I had an issue when trying to install Proxmox VE 8.4.1 on a Dell PowerEdge R610 (with PERC 6/i RAID controller).
During the installer boot, the screen was flooded with: "DMAR: ERROR: DMA PTE for vPFN ..."

The system still loaded, but these errors are related to Intel VT-d (IOMMU).
The R610 is quite old, and its BIOS/firmware implementation of VT-d is incomplete/buggy, which causes problems with modern Linux kernels.

Fix that worked for me​

  1. Boot the Proxmox installer from USB.
  2. On the first boot screen, highlight “Install Proxmox VE”.
  3. Press e to edit.
  4. On the line starting with: "linux /boot/linux26 root=... quiet" I add "intel_iommu=off"
  5. Press F10 (or Ctrl+X) to boot
This allowed me to install Proxmox without the DMAR errors.

Make it permanent after installation​

Edit the GRUB configuration "nano /etc/default/grub" and change the line: "GRUB_CMDLINE_LINUX_DEFAULT="quiet"" to "GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off""

Then update GRUB:
update-grub or
proxmox-boot-tool refresh
 
Last edited:
  • Like
Reactions: Supaman
Same console error in my Microserver Gen8 - Xeon 1265L - Proxmox version 9.0.3 - No hw controller - AHCI passthr. and ZFS.

:confused: