Closed alreadyconfused closed 3 months ago
Just to clarify: i copied the RaspiOS_Full_armhf folder from NOOBS and then replaced the boot and root files with my custom configured legacy rpi lite os files and changed the .json files a bit. Probably not the most intuitive thing to do
Also when looking at the original tar.xz files from NOOBS' RaspiOS_Full_armhf folder, all the directories and files inside the .xz files are at the root. When i imaged my os' sd card, then used the tar command in ubuntu to make the tar.xz files, it showed that all the necessary files and directories were in the root of the file, but when opening the same files in windows with winrar, the uncompressed tar file was inside the root of the tar.xz file. So do all the necessary files and directories need to be in the root of the tar.xz file, and if so how do i exactly do that?
If you have a customised RaspioOS LITE OS, would it make more sense to start off with a NOOBS RaspiOS LITE installation?
You might want to consider renaming it's folder from "Raspios Full...." to "VideoLooper" to distinguish it and to be consistent with the rest of the naming.
Executing: "sh -o pipefail -c "cat '/mnt/os/RaspiOS_Full_armhf/boot.tar.xz' | tee /tmp/fifo | xz -dcT 0 | bsdtar -xf - -C /mnt2 --no-same-owner | sha512sum /tmp/fifo > /tmp/sha1.out.txt"" "xz: (stdin): File format not recognized "
There seems to be some issues with your tar.xz files. have you followed the instructions/tutorials I provided in the README_PINN.md and on the Wiki? You probably need to install the prescribed bsdtar version
when opening the same files in windows with winrar, the uncompressed tar file was inside the root of the tar.xz file
I think that's just a quirk of some Windows compression software - they're not used to the "double wrapper" commonly used by Linux archives, so they show a .tar
file "inside" the .xz
file, when that's not really the case (depending on how you look at things!).
I can tell that there's a lot going wrong here but don't really know where to start. Here's the log file output that i got from savelog :