ApplePi-Baker Version: 2.2.3 (Build 1) (Helper Tool version 1.8.2)
OS Info: macOS Version 10.14.6 (Build 18G9028) x86-64 (64 bit application)
I have a raspeberry pi 3 with 128GB microsd card which after installing raspbian buster on I have shrunk the root filesystem down to 11GB:- Filesystem Size Used Avail Use% Mounted on /dev/root 11G 3.5G 6.4G 35% /
I have then created a ext4 partition in the free space of about 107GB which has had no data writen to it Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p3 107G 61M 102G 1% /media/pi/DATA
so there is about 4GB of data in total on the drive, after running ApplePi-Baker using the option to shrink to minimum size I have a zip file that is 98GB in size.
I have used ApplePi-Baker to create a backup of a 8GB microsd card (no partition changes) with buster installed and it produces a backup zip file that is 1.65GB in size which I have been able to recover without any problems; I noticed that during the recovery that it appears to create a full image to be written to the media whereas pi shrink recovers the shrunken image and relies on the pi to expand the filesystem on boot, this is a significant time saver when using when recovering to large capacity media.
I have not tried a recovery of the 128GB backup.
My main use of ApplePi-Baker is to backup the root filesystem, the seperate partition for data is for torrents which can be recovered from other sources.
As I said in the description, I created an extra partition; only copying the first partition it finds is ok; it would be good if the app could ignore any subsequent partitions and issue a warning.
Fairly easy to reproduce, just reduce the root partition down in size and create and extra ext4 partition in the free space (no need to put data into it), if you are going to do this I would suggest that you do it on an 8GB sd card as it takes hours on 128GB :)
deleting the extra partition prior to backup and the backup performs as expected.
Great app just what I was looking for; when there are problems and in a hurry, then recovering the image is a lot quicker than debugging what went wrong.
Partition table below as requested:-
/dev/disk6: Apple SDXC Reader Media (129 GB) Read/Write Internal Drive (Secure Digital) Apple Built In SDXC Reader Partitions: ▹ /dev/disk6s1 "boot" 268 MB Windows FAT32 ▹ /dev/disk6s2 "Untitled 2" 11 GB Linux (Ext2/Ext3/Ext4) ▹ /dev/disk6s3 "Untitled 3" 117 GB Linux (Ext2/Ext3/Ext4)
The problem with some images is that they use Extended Partitions (which APB cannot resize), so I wasn't sure if that was the case or if you had 2 EXT4 partitions. 😉
On that note: I think you selected the wrong option haha, you picked "Copy Structure to Clipboard" instead of "Copy partition table info from selected disk" (I typed it wrong as well). The partition info would show what type of partition would have been used (MBR, Extended Partition, etc).
Anyhoo ... neither here nor there 😉
I have been struggling with what partition to select in the past. The downside of removing the partition is that when doing a restore (with resize), then the first partition would expand to max capacity, which would be undesired in your situation, since you would still need room for the 2nd EXT partition.
I'll try to pick this up as an idea (time and life does get in the way sometimes): When more than one EXT partition is found, ask the user which one to shrink/expand - which could be a challenge for certain users, but it would help cases like this. Not sure if you'd do an expand on restore though. So I'm adding this to my "To-Do" list. 👍
Note: I did a quick look to see if I could easily implement this, but alas, it will take quite a bit to do this. Still on my To-Do list ... maybe time for APB v3? 😉 (it takes a lot of work though)
"The downside of removing the partition is that when doing a restore (with resize), then the first partition would expand to max capacity, which would be undesired in your situation, since you would still need room for the 2nd EXT partition."
is not a problem for me as I discovered I can use Balena Etcher to write the image from the APB backup zip; I then have two options, one is to use gparted to change the partition sizes to what I want and if I am not adding partitions I can boot the sdcard on the pi and then use raspi-config to increase the root partition to the size of the sdcard which is what it does when from the distribution image for the first time; this is a lot quicker than expanding the backup on the mac to the size of the sdcard and then writing this to the sdcard especially with a 128GB sd card.
Just a note for any followers of this topic, if you are going to use gparted on the pi to expand the root partition make sure that you install it before you make your backup as there is not enough free space to install gparted if you have not.
I thought about how you could implement multiple partitions in the backup but there are too many variables when recovering to a different size sd card and the beauty of your app is that its easy to use, thats why I thought a warning would suffice assuming you can skip the other extended partitions.
Ad Blocking Detected
Please consider disabling your ad blocker for our website.
We rely on these ads to be able to run our website.
You can of course support us in other ways (see Support Us).
MovieScanner2-2.0.16-Linux-GTK-64bits.tar.gzDate: 2022-05-03 - Size: 29.2 MBA small application that uses FFProbe to scan your video files and logs these details in a small database. This is the 64 bit Linux version for GTK.
MovieScanner2-2.0.16-Linux-QT5-64bits.tar.gzDate: 2022-05-03 - Size: 29.1 MBA small application that uses FFProbe to scan your video files and logs these details in a small database. This is the 64 bit Linux version for QT5.
MovieScanner2-v2.0.16-macOS-64bit.dmgDate: 2022-05-03 - Size: 25.4 MBA small application that uses FFProbe to scan your video files and logs these details in a small database. This is the 64 bit macOS version.