-
-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Hi,
I was wondering why I was not able to mount an img made from last raspbian version last week and I finally found the solution today.
The error message at boot time is "firmware not found"
/boot now contains two symlink to files in /boot/firmware.
As /boot is a FAT32 when done actually, the symlinks aren't created. By the way, the fstab will mount it incorrectly in the case it boots.
I've made a local modification to my milliways-image-backup script replacing "boot/" occurences by "boot/firmware/". I guess a sed could do it.
I guess this is not acceptable as a generic solution. It should instead use the current mount point from the source Pi the script is imaging, probably capturing it from a df output.
Many thanks in any case for your work even if I raised this issue it allowed my to do the job I was looking for.
BTW, I wish you an happy new year
Regards