https://bugzilla.suse.com/show_bug.cgi?id=1226109 https://bugzilla.suse.com/show_bug.cgi?id=1226109#c1 --- Comment #1 from StellarTerror <StellarTerror2@gmail.com> --- Created attachment 875384 --> https://bugzilla.suse.com/attachment.cgi?id=875384&action=edit the log file of the installation error -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226109 https://bugzilla.suse.com/show_bug.cgi?id=1226109#c3 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Richard Brown <rbrown@suse.com> --- Hi, thanks for the bug report, but its lacking some important details that as a reporter you should have included: During your first installation (at 12:19 on 08-06-2024) - You were prompted that an existing backup existed (when it did not) - You chose 'No' to delete the backup that didn't exist - You got an error message "Command /usr/bin/rmdir /var/lib/tik/mig/mnt FAILED" and that's how your install ended During your second installation (at 12:29 on 08-06-2024) - You were again prompted that an existing backup existed (when it did not) - You chose 'Yes' to use the backup that didn't exist - You got the error message you used to report this bug with Now I'm not writing all this to scald you, but just to help you write good bug reports in the future..I nearly wasted a lot of time debugging the second installation when infact ALL your issues were related to the first During your first installation, the installer was probing your existing installation on your target disk For some reason, after probing, your system refused to unmount the disk cleanly. This left a mount point lingering in /var/lib/tik tik's migration module assumes if there is ANY files in /var/lib/tik then that's a backup which can be used.. but there was no backup..just the broken mount point from your misbehaving existing filesystem Every other problem came after that point - your first installation failed because of the misbehaving filesystem , and your second installation failed because your tried to use a backup that wasn't actually there so it was trying to restore files that didn't exist So, we need to address the core bug(s) tik should use somewhere else for it's mounting than the same location we check for backups and we need to figure out a way of more gracefully handing misbehaving existing filesystems We'll get on it..meanwhile, a quick and dirty work around would be to backup anything you want from your existing installation, format the disk you want to install, and then Aeon will install fine. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226109 https://bugzilla.suse.com/show_bug.cgi?id=1226109#c5 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |StellarTerror2@gmail.com Flags| |needinfo?(StellarTerror2@gm | |ail.com) --- Comment #5 from Richard Brown <rbrown@suse.com> --- partly addressed in tik 1.0.7's improved mounting behaviour Can you please retest using openSUSE-Aeon-Installer snapshot versions 20240611 or later (once they exist)? -- You are receiving this mail because: You are on the CC list for the bug.