I’m encountering an issue with OpenBMC where I’m setting a variable using the fw_setenv command, but it disappears after a reboot. Strangely, other variables I set using the same method persist across reboots.

For example, I’m setting a variable openbmconce with the value factory-reset using the command:

fw_setenv openbmconce factory-reset;

However, upon reboot, this variable seems to vanish.

It’s worth noting that OpenBMC’s factory reset functionality typically involves deleting the read-write layer. However, I’ve modified its behavior at the code level to do nothing. Despite this, the openbmconce variable still disappears after reboot.

I’ve noticed that certain variables might be intentionally designed to reset upon reboot for security or temporary configuration purposes, but I couldn’t find any documentation specifying this behavior for openbmconce.

Could anyone provide insights or guidance on how to configure other variables in OpenBMC to exhibit this behavior, similar to openbmconce?

Any insights or suggestions would be greatly appreciated!