So, not long ago my pi crashed and I had to completely rebuild the server. I elected to use my NVMe drive which is 1TB. I thought I'd partitioned it in a way where I set up 32GB for `/` but in my haste to get the server back up and running apparently I didn't. Ouch. Now it's its all set up and settled in. I need to back it up. Since the NVMe is 1TB I can't simply image the entire device. So, I elected to image the individual partitions.
The SD card was initially created with the imager and booted to so that I could image the partitions on the NVMe device. I then booted from the NVMe device and wrote the partition images back onto the SD card. The problem I am having now is that no matter what I do in `raspi-config` the boot device is _always_ the NVMe device. I can clearly see that the boot order is changing from `BOOT_ORDER=0xf146` to `BOOT_ORDER=0xf461`. How can I fix this so that the SD card boot disk doesnt still load the NVMe drive? Im guessing that the overwritten boot partition has something to do with it but I would have expected that raspi-config writing to the eeprom would make it not matter, if that makes sense? Should I recreate the default boot profile and just use that?
Edit 1: Just had a thought, would the device ID get copied over in the image? Maybe that has something to do with it?
Edit 2: Can confirm that the UUID is copied over
Since this is simply a backup device, do I really need to have unique UUID on the image? I am thinking no.
Code:
mmcblk0 179:0 0 58.2G 0 disk |-mmcblk0p1 179:1 0 512M 0 part /media/addohm/bootfs`-mmcblk0p2 179:2 0 57.7G 0 part nvme0n1 259:0 0 931.5G 0 disk |-nvme0n1p1 259:1 0 512M 0 part /boot/firmware`-nvme0n1p2 259:2 0 57.7G 0 part /Edit 1: Just had a thought, would the device ID get copied over in the image? Maybe that has something to do with it?
Edit 2: Can confirm that the UUID is copied over
Since this is simply a backup device, do I really need to have unique UUID on the image? I am thinking no.
Statistics: Posted by addohm — Fri Jan 24, 2025 1:43 am