This makes a lot of sense if you have many systems that you want to backup, but for one or two the use of 32 GB is not too bad in today's world of storage. Good to know it can be done and thanks for taking the time to post this.
It is a very, very, bad idea to suggest updating everything as a pre-backup step, for most people that is going to leave the system in an unusable state where the MCU firmware versions mismatch, and that is one of the biggest reasons why MOST people should backup their stuff in the first place, if they find out their MCU's need to be updated and, oh gosh, I forgot how to do it and now my printer is down until I figure it out...if only I could restore from a backup. I understand the logic here but it's super dangerous not to tell people "only update if you are fairly recent and SURE you wont need to flash your MCU's".
@@ChrisRileyI would agree that the recommendation should be to NOT update before the backup, so it is in a known good working state. Then update after you reimage. If the newest update doesn't work right, restore to your known good config before the update
This makes a lot of sense if you have many systems that you want to backup, but for one or two the use of 32 GB is not too bad in today's world of storage. Good to know it can be done and thanks for taking the time to post this.
Good point Dave. Someone actually asked me this because they wanted to share the image as part of their github project.
@@ChrisRiley That makes a lot of sense, to shrink for sharing.
Just plug a USB drive at least as large as your SD card into the PI. Then use dd to clone it. Job done.
I will have to give that a try.
Great tool. Thank
You bet!
Helpful! You think pi-shrink would work under Cygwin too?
Hey Gcerchio, I would think it would, but I have never tried it.
It is a very, very, bad idea to suggest updating everything as a pre-backup step, for most people that is going to leave the system in an unusable state where the MCU firmware versions mismatch, and that is one of the biggest reasons why MOST people should backup their stuff in the first place, if they find out their MCU's need to be updated and, oh gosh, I forgot how to do it and now my printer is down until I figure it out...if only I could restore from a backup. I understand the logic here but it's super dangerous not to tell people "only update if you are fairly recent and SURE you wont need to flash your MCU's".
This is true, update can break a lot of stuff. I should have included make sure everything works before the backup.
@@ChrisRileyI would agree that the recommendation should be to NOT update before the backup, so it is in a known good working state. Then update after you reimage. If the newest update doesn't work right, restore to your known good config before the update
Second video about shrinkage..i can relate! 🫣🤭🤣
😅