If the 'Buster Pi' is a Pi4 with default boot device sequence priority (first try SD-card, then USB, reset and try again if both fail) most people would stick the new Bookworm SD-card in the card-slot and use a USB-SD-card adapter where you put the old Buster SD-card.What I need is a strategy for changing boot drives. I could just plug it in and reboot. But, there is a bunch of stuff (webcam photos and more) that really should be moved to the new drive. Will I be able to boot from the new Bookworm drive and then mount the old Buster drive and copy stuff from old to new? I've never tried anything like that before.
How would I actually go about mounting a volume from the Buster boot drive?
You can test upfront at home by mounting a backup SD-card of your remote Pi in your spare/test Pi4.
Ad-hoc mount is then something like:
Code:
sudo mkdir -pv /home/_tmp/buster_p1sudo mkdir -pv /home/_tmp/buster_p2sudo mount -v /dev/sda1 /home/_tmp/buster_p1sudo mount -v /dev/sda2 /home/_tmp/buster_p2Partition 1 (/dev/sda1 ) is maybe not needed, but you never know. You might need to compare different config.txt and cmdline.txt versions in worst case.
You can use the good old MS-DOS Norton Commander clone (mc in Linux) to copy various stuff. That also works remote and via CLI.
But I would not go for 2 storage devices option. I would copy the whole Buster card contents (all files you need at least) to the Bookworm card already upfront. It might need ad-hoc copying files from the remote Pi to your home so you get the (almost) latest state. I always had nightly replication, so had latest files already locally at home.
It is just planning and making a list what is needed. At least when on remote location, keep the Buster card as is as much as possible, so if after an hour or so it doesn't work, you could go back to what worked an try later after new year or so.
Statistics: Posted by redvli — Sun Nov 17, 2024 12:26 pm