https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c6 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tony.neely@gmail. | |com) --- Comment #6 from Richard Brown <rbrown@suse.com> --- Ok so, a few questions and I’ll do my best to address them all On the matter of your primary drive. No matter what you may have done in YaST, you have a /@/home subvolume. But given you mounted a separate /home partition on your second drive, it should be empty Now, I tested empty disks with /@/home subvolumes extensively and never hit this issue. So let’s just assume you have some weird other issue with your existing filesystem on your drive We could debug it.. but it sounds like there’s no data of interest on that primary drive So, I’d like to propose a workaround Your Aeon installer comes fully equipped with a terminal (with sudo privileges) and all the partioning tools you may need Before clicking ok on the installer welcome screen Id recommend firing up a terminal And establishing a new partition table on the disk you want to install Aeon to This error will vanish as a result Meanwhile Aeons installer won’t touch the second disk (with your /home) at all You have two options as how to make use of it after installing Aeon Option 1. Boot your new Aeon install, go through the first run wizard and then after first login edit /etc/fstab to mount your /home partition instead of the /@/home subvolume. As long as UIDs and the like all match up things should work ok. You may need to run /usr/bin/aeon-mig-firstboot just to fix up a few things on first login to the migrated /home partition but I expect that to be a minor hiccup if at Option 2. Aeon fully supports combustion. You could write a shell script to edit your new Aeon installs fstab, create user accounts, or any other customisation you like. That script needs to be called “script” and stored in a “combustion” directory on the “ignition” partition of your Aeon installer USB stick. Then it will be executed on first boot of your Aeon install. Potentially it’s a cleaner more reproducible approach that someone with your experience might appreciate Does this help at all? -- You are receiving this mail because: You are on the CC list for the bug.