ISO not Installable (Bad unpackfs configuration)

[N0N4s]

Dear Leo,

I found your p3ng0s OS and wanted to give it a try, after creating a Live USB with the ISO on it, I'm getting the following Error from the Calamera Installer after filling all required informations

""" Installation Failed

Bad unpackfs configuration

Details:

The source filesystem '/run/archiso/bootmnt/arch/x86_64/airootfs.sfs' does not exist

"""

Also another Question, is it possible to Install p3ng0s as a virtual Machine?, I tried installing it via vmWare Workstation, but once the Live System is booted, the Installer is not even showing up or able to start, the whole System freeze, would be awesome to be able doing that.

Looking forward your help, and can't wait to try your OS

Kind regards

[p4p1]

Hy mate, for the iso problem with the file not existing error is normal if you boot the iso on a "new machine" basically everything after legacy boot without having legacy boot enabled will break the install program. I have manually fixed it during an install by mounting the flash drive finding the files and editing calamares config manually and then was able to install on a 2024 release laptop i am working on finding a fix for this bug and for the virtual machine that bug you described sounds like a bug with the compositor ive had this problem with vm installs where i had to delete the picom package with pacman -R picom before launching the gui (you can test this out by first running dwm-light 2nd option on boot if that one works fine it probably means picom is the issue) don't know why it's there nor how to fix it 🤷

[N0N4s]

Hey,

Thank you so much for your fast reply.

Can you somehow give some further Explanations how you solved it manually? Like which files exactly you had to edit and where you edit the calamares config?

Right now I just want to be able installing the OS because I'm kinda stoked about it xD the following with being able to install it as virtual machine is maybe a bit to far in the future.

I really appreciate your work, with creating all of it.

[p4p1]

Hello Hello, sorry for the delay in answering I immigrated to a different country and I'm currently waiting for my daughter to be born so a lot on my mind LOL but I really wanted to answer because I think this should be documented somewhere sorry it took me over 1.5month. So to answer your question basically when you boot on a real machine if it's a new one there is a 100% chance you are in EFI mode I have setup a virtual machine on virtual box with this exact setup here is my vbox config (There is an error on the screenshot the size of the harddrive should be minimum 50Gig not 20Gig): When setting up a VM just do not have efi active like I did because VM+efi don't mix well for vm's you just need to select the second option for the window manager and run clamares as root from a terminal and you should be fine on installing like that the rest of the explanation is for real hardware (efi)

Side Note: you can guess your computer is running EFI if you get an error like this on boot:

Once you boot up the .iso in the VM or the real machine you can just go into the normal dwm window manager mode like the first option here:

from here if you are in a VM you should have a broken screen that is frozen on this:

NOTE: this is only for Virtual Machines real hardware usually is fine here

Right from this if you are frozen you can escape this hell hole with the Shortcut: Alt-Shift-e this will then return you to the previous screen where you need to select the 2nd option:

now you should have feedback so if you do Alt-Enter you should see a termial popup:

From here you can run calamares with this command in the terminal:

sudo calamares

Now to the actual calamares problem with uefi installs that I didn't fix. Basically during install this file "/run/archiso/bootmnt/arch/x86_64/airootfs.sfs" is the OS that will be flashed on the file system because uefi does something I don't understand to the boot CD the file is missing so inside of the calamares config we have to change the path inside of the following file:

/etc/calamares/modules/unpackfs.conf

just fyi: unpackfs.conf -> unpack file system conf

what we need to edit is those two lines with the correct path:

I found the correct path through the most obscure method possible, what I did was the following I mounted the installation medium to the live OS through those commands:

fdisk -l
mount /dev/sda /mnt/

From there I found the airootfs.sfs and the vmlinuz-linux file inside of the actual usb key updated the paths and re launched calamares then the installation finished. This is a temporary fix up until I actually fix the issue hope this helps :)