framps / raspiBackup

Create and keep multiple backup versions of your running Raspberries
https://raspibackup.linux-tips-and-tricks.de
GNU General Public License v3.0
787 stars 76 forks source link

Restore on Raspberry Pi 5 Bookworm - /boot/firmware/ empty #735

Closed p1r473 closed 7 months ago

p1r473 commented 7 months ago

Hi Framp! I have just built 2 new Raspberry Pi x64 Bookworm. I completed the first one, then went to clone the SD card via raspibackup restore and find that /boot/firmware/ is empty

After the restore I mounted the SD card I restored to and checked both SD cards The card I am running on has /boot/firmware/ The card I restored to has en empty /boot/firmware/

❯ mount /dev/sdb2 /mnt/temp    
❯ ls /boot/firmware
 bcm2710-rpi-2-b.dtb        bcm2711-rpi-400.dtb      bootcode.bin   fixup4x.dat      initramfs8         start4cd.elf   start.elf
 bcm2710-rpi-3-b.dtb        bcm2711-rpi-4-b.dtb      cmdline.txt    fixup_cd.dat     issue.txt          start4db.elf   start_x.elf
 bcm2710-rpi-3-b-plus.dtb   bcm2711-rpi-cm4.dtb      config.txt     fixup.dat        kernel_2712.img    start4.elf    'System Volume Information'
 bcm2710-rpi-cm3.dtb        bcm2711-rpi-cm4-io.dtb   fixup4cd.dat   fixup_db.dat     kernel8.img        start4x.elf
 bcm2710-rpi-zero-2.dtb     bcm2711-rpi-cm4s.dtb     fixup4.dat     fixup_x.dat      LICENCE.broadcom   start_cd.elf
 bcm2710-rpi-zero-2-w.dtb   bcm2712-rpi-5-b.dtb      fixup4db.dat   initramfs_2712   overlays           start_db.elf                                      21ms
❯ ls /mnt/temp/boot/firmware

I dont have any /boot/ exclusions in my config so Im not sure why the restore isnt resorting the boot partition properly raspiBackup.log

p1r473 commented 7 months ago

Well it seems to boot fine so perhaps a problem with my testing methodology?

framps commented 7 months ago

There are a lot of changes in Bookworm. Note the bootpartition is no longer mounted on /boot but on /boot/firmware and the mount will only exist on a running system.

p1r473 commented 7 months ago

Yep, that's definitely the issue. Had to boot the machine to see the mount