Advanced users • Re: Image File Utilities

I'd misread the first question, 'Use SD card to boot the USB device?'.  I took it's meaning as using the SD card to create the boot-able usb device, or in this case the nvme drive.  No, giving one the option to select another source device.   
...

Code:

/mnt/rootfs/boot $ ls cmdline.txt                  config.txt       initrd.img-6.1.0-rpi8-rpi-2712   overlays                         vmlinuz-6.1.0-rpi8-rpi-2712 config-6.1.0-rpi8-rpi-2712   firmware         initrd.img-6.1.0-rpi8-rpi-v8     System.map-6.1.0-rpi8-rpi-2712   vmlinuz-6.1.0-rpi8-rpi-v8 config-6.1.0-rpi8-rpi-v8    'firmware'$'\n'   issue.txt                        System.map-6.1.0-rpi8-rpi-v8

Code:

drwxr-xr-x  3 root root     4096 Mar 11 08:39 'firmware'$'\n'

There's no option to select another source device because usb-boot is intended to replicate the running system onto a USB/NVMe device.

Have you confirmed that the 'firmware'$'\n' directory is NOT present on the SD card that you're replicating with usb-boot? I have a suspicion the source of your problem may be on the SD card and usb-boot is simply faithfully replicating it. The problem then resides on the NVMe device in addition to the SD card. This would explain why no one else is having the problem.

Put a fresh copy of Raspberry Pi OS on a different SD card and use usb-boot to replicate it to the NVMe device. If you no longer have problems using image-backup, that will prove you're replicating a bad directory from the original SD card.

Statistics: Posted by RonR — Tue Mar 12, 2024 2:09 am

---