Error with partitions being overwritten

[clarkster48]

I am trying to restore an image backup that was made using the image-backup utility. I followed the article about creating a multi boot SD card out of 2 existing OSes using PINN but only did it for the one .img. When I install the OS and reboot, all of the partitions disappear and the system hands on "waiting for SD card (settings partition)". When going into recovery mode, all partitions except recovery are wiped out. What am I doing wrong or where can I look to make adjustments?

OS is latest Raspbian OS Trixie.

Thanks

[procount]

Please post the meta files you created for your OS (everything except your tar.xz files and marketing.tar)

[clarkster48]

os.json
partition_setup.sh
partitions.json

I pulled these off the raspberry pi site per the instructions for my OS (latest trixie 32bit / 64 bit).
If I am missing something in the config, please let me know!

[procount]

In partitions.json, you don't need the "requires_partition_number" for either partition.
I assume you have modified the various sizes appropriately?

I've not seen this behaviour of wiping out all the partitions before.

[clarkster48]

I added the "requires_partition_number" to try to see if I could force it to stick to those partitions.
I modified the sizes based on the page and even doubled the numbers in one instance.

It installs fine, before I click OK at the confirmation of successful installation to go forward, I go to the recovery partition to confirm the partitions are written right, and they are.

The image files are made through image-backup (image-utils) and are uploaded in a .img that I downloaded. I have also tried to copy direct from the SD card with the same issue.

Once I click OK on the confirmation, it loads, then reboots, then hangs on the waiting for settings partition. After a while, I push escape, go to the recovery partition and see only the recovery partition after that.

This ONLY happens with the .img files made through image-backup. If I install fresh OS through PINN, everything works fine, but if try to do an image backup install, the problem persists.

I also attempted to do an image-backup the new OS on pinn, same results.

[procount]

Don't use img files.
Use tar.xz files instead.

[clarkster48]

Sorry I have to make a correction, the image-backup files backup as .img files, I mount them as boot and root partitions then convert to .tar.xz files per the instructions in the guide, they are all ultimately .tar.xz files; same issues.

[procount]

Which version of PINN are you using?

[clarkster48]

I attempted 3.8.8 and 3.9.3 - I am using a raspberry pi 4b with 8gb of memory if it helps.

[procount]

Could you try with a fresh installation of PINN v3.9.8?
Before installing your OS, have a look at the troubleshooting section step 6 and download/copy savelog to the PINN partition.
After installing your OS, but before pressing OK when it is successfully installed, follow the troubleshooting section step 6 to run savelog and post the log output. It might help diagnose he problem, but it is a very odd one.

[clarkster48]

How sensitive is the os.json file in running everything? I did a clean install and adjusted the kernel to the kernel from the image backup and it seems to have maybe taken hold now and seems to maybe be working... doing some more evaluating, but just wondering?

[procount]

How sensitive is the os.json file in running everything?

Well, a lot of it is just for information to describe the OS and to present it within PINN. It does decide whether it is suitable for your current RPi model, though. Most of the other files used locally are identified based on the os name or partition names.

I did a clean install and adjusted the kernel to the kernel from the image backup and it seems to have maybe taken hold now and seems to maybe be working... doing some more evaluating, but just wondering?

Do you mean you altered the kernel version in os.json to match the version used in your backup? That shouldn't make any difference. It's just for information, but it must be in the correct json format, otherwise os.json won't be used at all.

[clarkster48]

I am wondering if it is pi hole causing it. The backup I insalled had pi hole disabled, when I enabled it, the partition rebooted and everything disappeared.... Any ideas on that?

[procount]

Sorry, I have no idea.

[clarkster48]

I have narrowed the problem down to something with image-backup. When I do a backup using pinn to usb, or just follow the instructions and copy the data on the sd to the usb card, it works fine, so I guess it is something related to that program and I will make a manual script to automate my backups. Thanks for the help!

[procount]

That makes sense.
I've never used image-backup, it seems to be an unnecessary step. Normally I would just mount the SD card itself.
Where did you get it from?
Perhaps it shrinks the file systems before creating the image and adds a script to expand them when it is installed again, but this may mess with PINN's partitions since the structure is not what it expects......?????