I have a big problem. My backup nas (a very old ML350 G6) is running 3 hours at night, gets turned on with a wake packet and shuts down automatically 3 hours later. Or so I thought…
I noticed that since upgrading to Electric Eel, it is not shutting down. Dmesg was full of DMAR errors. So I figured it must be iommu. This nas does not require virtualization, and only wakes up to sync with the main one. However, the iommu cannot be disabled in bios. I noticed in Electric Eel the kernel parameter intel_iommu=on is added by default. Once I removed this parameter, all the problems were gone. But I cannot find any method to make this permanent. No matter what I do, on the next boot it comes back. Any idea how I can remove this pesky problem?
Having owned one of these in the distant past, I believe you can. Check for “Intel VT-d” under the System Settings → Advanced menu here and disable it there.
Failing that, I’ll look to see if we can find a way to adjust the default boot parameters specifically.
It is disabled, but it makes no difference. Iommu on that server is extremely buggy. The only solution I have found is to turn it off via the kernel parameter.
I had similar problems with a DL380 G6 after upgrading to Fangtooth recently.
I used:
midclt call system.advanced.update '{"kernel_extra_options": "intel_iommu=off"}'
…to add the intel_iommu=off kernel parameter. When the systems boots you can see that the kernel parameters include both intel_iommu=on and intel_iommu=off, the latter overriding the former.
FWIW, I also turned off Intel VT-d in the BIOS, just in case the kernel parameters ever get reset/overridden by an upgrade.
2 Likes
Thanks! That did the trick. There doesn’t seem to be a ui equivalent to this setting.
1 Like
