Pi update chronicles

[Mr.Shaky]

[EDIT: this is not a step-by-step guide!  I'm logging information as I encounter issues, so it's best to take this body of information as a whole for comprehension before extracting what you need.  YMMV  ]

Back when I built my Voron, I did so with a 3B+ and Bullseye 32bit. LTS support is ending in August 2026 (soonTM) and I had a Pi4 that was freed up, so I'm going through a device migration process to Trixie 64bit.  I figured I'd catalog what I'm doing for anyone else that might be considering doing the same, and there's a lot here that can be cribbed for general backup purposes...

• used Raspberry Pi Imager to write Trixie 64bit (lite) with the appropriate net/locale customizations to new sd card for Pi4 (new system name)
• install apt updates, install git, KIAUH (Klipper, Moonraker, Mainsail, Crowsnest, KlipperScreen, Autotune), reptyr, KAMP, Shake&Tune, Cartographer probe
• My preferred cloud backup method is in the official docs--https://docs.vorondesign.com/community/howto/EricZimmerman/BackupConfigToGithub.html
• My local backups are handled with UrBackup

Since I'm able to have both Pi online at the same time, transferring data is very straightforward with WinSCP

I installed all the packages listed earlier with defaults, setup the github backup and performed the initial backup of ~/printer_data/config/ before overwriting with files from the original setup

• Connect to each Pi with the same user you would for SSH
• for good measure, on the original Pi, copy the entire ~/ directory to your PC if you'd like (Mainsail has a lock file or 2 that can't be copied and can be skipped) note that ~/ is a shortcut to the base home-directory of the logged-in user
• If you want to have all your old gcode on the new Pi, you can copy over the full contents of ~/printer_data/gcodes/
• printing history is in ~/printer_data/database/  note that there may be multiple other files in the original location (*.mdb) but the new install only needs the moonraker-sql.db file

Next step is to deal with the hardware (Pi or sd swap)

 

 

(getting what's in my head written down now; as soon as I'm able to pull my printer onto the workbench and take care of the swap, I'll update this post)

 

 

.

Edited April 16 by Mr.Shaky
add disclaimer

[Mr.Shaky]

...so the hardware has been swapped.

For anyone looking at this, it should be noted that this is very likely *NOT* "the perfect time" to add hardware to your build, especially something like a Cartographer 3D sensor.  Klipper updates will frequently break carto function, necessitating a Klipper version rollback. Get the Klipper version hash from the working install so the new setup can be at that version as well.

• I had the Pi set up as a secondary mcu which requires additional configuration (mainly for temp monitoring as carto is pulling accelerometer duty now)

I'm now discovering that there were multiple Cartographer updates that weren't part of what Moonraker can manage (new firmware & software plugin.)  Their announcements are done quietly in their discord, so attention needs to be paid.  My post-upgrade issues have revolved around just this, and I needed to do a Z calibration as a result.

While the imported history database was recognized immediately, all the copied gcode wasn't even listed in the manager until the manager's refresh button was pressed.

This is where I shut everything down and moved the printer off the bench.  Anything new will be edited-in after this...