SOLVED Struggling with boot loader tunables

[Master-DXT]

Dear community,

I have been a long time lurker, and mostly found solutions here but this time I am at a loss, well not entirely but I prefer not to brick my server.

First a list of hardware I use.

Mobo; Asus Prime Z690-A
Mem; 128GB DDR5
CPU; i5 12500
HBA; LSI SAS9300-16i (Firmware 16.0.12.0)

The system is running truenas scale 22.02 and everything runs well for the moment, but that was never the case because truenas had a fight with my HBA, spewing out “PICe Bus Error: Severity=Corrected”. To remedy this, I used the following command, “midclt call system.advanced.update '{ "kernel_extra_options": "pcie_aspm=off" }'”, and that resolved the issue. Now I also want to use my Alder Lake IGPU, which requires the following, “midclt call system.advanced.update '{"kernel_extra_options": "i915.force_probe=4690" }'”. But whenever I use the tuneable setting it will overwrite the previous one, leaving me with PICe Bus Error: Severity=Corrected messages. How annoying!

My question, how do I combine the two, I have a hunch, but again, I do not want to brick anything. :)

 

[sretalla]

midclt call system.advanced.update '{"kernel_extra_options": "firstoption=value secondoption=value thirdoption=value"}

credit to https://www.truenas.com/community/t...tions-from-grub_cmdline_linux_default.100665/

 

[Master-DXT]

midclt call system.advanced.update '{"kernel_extra_options": "firstoption=value secondoption=value thirdoption=value"}

credit to https://www.truenas.com/community/t...tions-from-grub_cmdline_linux_default.100665/

Just to be absolutely sure. That would be midclt call system.advanced.update '{"kernel_extra_options": "i915.force_probe=4690 pcie_aspm=off"}'correct?

Further more, would it presist during future truenas updates? :)

Thank you very much!

 

[sretalla]

midclt call system.advanced.update '{"kernel_extra_options": "i915.force_probe=4690 pcie_aspm=off"}'

Looks good.

would it presist during future truenas updates? :)

Yes, that call stores the value in the config DB, which survives an update.

 

[Master-DXT]

Looks good.


Yes, that call stores the value in the config DB, which survives an update.

And it appears everything is working as it should. Thank you so much for your support.