I have a raspberry pi running with an SD card and a USB stick. Both run 32 bit lite, but the SD has bullseye while the USB is running bookworm. As long as I have this raspberry pi connected to our corporate lan, I can switch back and forth between these 2 boot drives with no issue. It works flawlessly every time! However, if I instead place the devices on a private ethernet segment with my own DHCP server (dualserver on windows) the switch-over often fails. I still boot up on the boot media properly, but when I try to flip to the other drive, I'm often "stuck" on the current drive. I'm flipping by using this commands:
sudo -E rpi-eeprom-config --edit
After which, I edit the boot order parameter and change from F14 to F41 or vice versa.
BOOT_ORDER=0xF14
Again, this works perfectly while I have corporate access with corporate services and internet access. The isolated ethernet segment cannot consistently switch (although occasionally it does work). Is there some kind of requirement here for the device to have access to some service or some internet server to be successful with this boot switch?
sudo -E rpi-eeprom-config --edit
After which, I edit the boot order parameter and change from F14 to F41 or vice versa.
BOOT_ORDER=0xF14
Again, this works perfectly while I have corporate access with corporate services and internet access. The isolated ethernet segment cannot consistently switch (although occasionally it does work). Is there some kind of requirement here for the device to have access to some service or some internet server to be successful with this boot switch?
Statistics: Posted by frickaline — Thu Apr 18, 2024 7:18 pm