Destroys install

[StiflingChip192]

All this did was destroy my install by deleting everything besides my home folder and putting my home folder at the root of the partition.

Luckily this was just a clean install instead of a legitimate one or id be very upset.

As for details, I was just testing the software out to see if my archiso setup would work with it, all I did was add the custom repo along with the relevant file modifications. The same setup successfully creates an ISO with archiso with zero errors. Attached is a photo showing how only /dev and /proc are in the build folder with nothing else.

The output iso directory is empty and the original directory it was run from seems the same from all what I can tell. My best guess is that something was attempting to use a relative path to the root but instead used an absolute path, overwriting the current file system.

[arcolinuxz]

Are you using Btrfs?

[StiflingChip192]

Was using ext4 with the same folder I always use with archiso and it works with no problem through that.

If it is not compatible with ext4 that's on me for missing the documentation of that, however it should do a simple check and exit the process in that case instead of continuing regardless and corrupting the filesystem.

Also, I realized I never attached the photo of the fs afterwards, sorry about that here it is. I chrooted in and just checked out a couple things to see where everything had gone so you can see where things ended up.

Just to clarify this is the partition arch was running from, not the result of an attempted install with an iso. It started out with terminal stalling with an output of "failed to open up /dev/null: permission denied" with every keystroke. I rebooted with the intent of /dev being automatically rebuilt when I discovered the reason for the error was the overwritten filesystem.

I quickly fixed the drive so sorry I don't have any much more information than this, let me know if there's anything else I could do/say that could be beneficial.

[arcolinuxz]

I have been using Ext4 since the start of the project

build 1000+ ISOS since then - so I am quite sure it is not the formatting system ext4 that caused this but ... what could have is now still unsure