@cleverca22, that's super helpful. I didn't even notice that the UUIDs were duplicated. That exact problem was indeed causing frustrating intermittent boot failures.
It would be really great if rpi-imager had an option to randomize the UUIDs.
---
For anyone who runs into this issue and who cannot change the predefined UUIDs using a tool before imaging, here's what I did to fix the issue after imaging. Please note that this needs to be done with the disks in an unmounted state (I.e. after flashing, but before mounting or rebooting onto the newly-flashed media).
Be sure to replace /dev/nvme0n1p# with /dev/sda# or /dev/mmcblk0p# if updating the USB drive or the eMMC/SD accordingly.
To randomize the UUID on the vfat (FAT32) boot partition:
sudo apt install mtools
sudo mlabel -n :: -i /dev/nvme0n1p1
To randomize the UUID on the ext4 partition:
sudo tune2fs -U random /dev/nvme0n1p2
...
NOTE: tune2fs may require that the partition be e2fsck'd first:
sudo e2fsck -f /dev/nvme0n1p2
---
This exercise also made me double-check the BOOT_ORDER documentation, and I realized that there are effectively two USB MSD boot options for the RP4 -- and that I needed boot option # 5 ("USB C MSD") in lowest-nibble position for this carrier board--instead of boot option # 4.
So now I've simplified down to the following (and can swap to 0xf615 if I ever want to swap the boot order between eMMC and NVMe):
BOOT_ORDER=0xf165
Everything seems to be working properly now. Thanks again @cleverca22.
It would be really great if rpi-imager had an option to randomize the UUIDs.
---
For anyone who runs into this issue and who cannot change the predefined UUIDs using a tool before imaging, here's what I did to fix the issue after imaging. Please note that this needs to be done with the disks in an unmounted state (I.e. after flashing, but before mounting or rebooting onto the newly-flashed media).
Be sure to replace /dev/nvme0n1p# with /dev/sda# or /dev/mmcblk0p# if updating the USB drive or the eMMC/SD accordingly.
To randomize the UUID on the vfat (FAT32) boot partition:
sudo apt install mtools
sudo mlabel -n :: -i /dev/nvme0n1p1
To randomize the UUID on the ext4 partition:
sudo tune2fs -U random /dev/nvme0n1p2
...
NOTE: tune2fs may require that the partition be e2fsck'd first:
sudo e2fsck -f /dev/nvme0n1p2
---
This exercise also made me double-check the BOOT_ORDER documentation, and I realized that there are effectively two USB MSD boot options for the RP4 -- and that I needed boot option # 5 ("USB C MSD") in lowest-nibble position for this carrier board--instead of boot option # 4.
So now I've simplified down to the following (and can swap to 0xf615 if I ever want to swap the boot order between eMMC and NVMe):
BOOT_ORDER=0xf165
Everything seems to be working properly now. Thanks again @cleverca22.
Statistics: Posted by tako — Sat Oct 12, 2024 12:21 am