[Bug 1225689] New: Error message received from tik with mount system call failed.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 Bug ID: 1225689 Summary: Error message received from tik with mount system call failed. Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown@suse.com Reporter: tony.neely@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: [tik][20240531-02:01:04][LOG] [START] /usr/bin/tik [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:04][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [zenity][0][] --info --ok-label=Install Now --no-wrap --width=300 --height=300 --icon=distributor-logo-Aeon-symbolic --title= --text=<big>Welcome to openSUSE Aeon</big>\n\nPlease press <b>Install Now</b> to continue [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [STOP] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:24][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/20-mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:32][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [zenity][0][nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V] --list --column=Disk --column=Size --width=1000 --height=340 --title=Select A Disk --text=Select the disk to install the operating system to. <b>Make sure any important documents and files have been backed up.</b>\n ata-Samsung_SSD_860_EVO_1TB_S3Z8NY0M767057P 931.5G nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V 232.9G [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [probe_partitions] /dev/disk/by-id/nvme-eui.0025385691b29275-part2 found [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] Legacy Aeon Install FOUND [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/umount /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/rmdir /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/mkdir /var/lib/tik/mig/mnt mount: /var/lib/tik/mig/mnt: mount system call failed: No such file or directory. dmesg(1) may have more information after failed mount system call. [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][32] /usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][ERROR] Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [zenity][0][] --error --text Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [STOP][1] /usr/bin/tik Reproducible: Always Actual Results: System notified me of error and shut down. I have an existing Aeon install, with a separate drive (BTRFS formatted) for my /home. Easy enough to setup with old installer. Chose system drive (not /home drive) for the install. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c1 --- Comment #1 from Tony Neely <tony.neely@gmail.com> --- Created attachment 875230 --> https://bugzilla.suse.com/attachment.cgi?id=875230&action=edit tik.log -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c2 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tony.neely@gmail.com Flags| |needinfo?(tony.neely@gmail. | |com) --- Comment #2 from Richard Brown <rbrown@suse.com> --- What kind of storage device are we talking about here? And what kind of system specs (CPU? RAM?) I'm curious because the error appears to be your system complaining that /var/lib/tik/mig/mnt wasn't present..but it was made immediately before hand So I'm expecting a performance issue causing things to get confused -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c3 Tony Neely <tony.neely@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tony.neely@gmail. | |com) | --- Comment #3 from Tony Neely <tony.neely@gmail.com> --- System specs "shouldn't" be an issue. (Famous last words). It's a desktop I built myself, no issues installing or running RC1. CPU: Ryzen 5 5600x RAM: 16 GB DDR4, 3200 Mhz Install target: 256 GB Samsung NVME via PCIE Drive for /home: 1 TB SSD - SATA Only other "issue" I noticed was it took so long to get to the install screen that originally I rebooted to try again. Screen was just black. Second time I just waited it out. Sometime this evening or weekend I can try a different USB stick in case it caused issues. I used the recommended impression flatpak on RC1 to burn the image. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c4 --- Comment #4 from Tony Neely <tony.neely@gmail.com> --- Almost forgot. It does run a dedicated GPU: AMD 6600. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c5 --- Comment #5 from Tony Neely <tony.neely@gmail.com> --- Ok, a little update here. There was no difference when using a different usb stick. I believe the issues is from how I installed the RC1. While I've run linux/BSD/plan9/etc for close to 20 years, I tend to avoid the shiny and new. So, I don't have a lot of experience with systemd or btrfs. With the old installer (yast I presume), I was able to edit the partitions and mount points after the system put in the defaults. I chose my secondary drive as /home and upon doing so, it removed the @/home subvolume from the primary nvme. Installation worked well and I've run it that way for months. So, I'm wondering if the new installer notices subvolumes that would indicate a previous, Legacy Aeon install but runs into issues when it moves forward until @/home isn't found on that disk as it's on the secondary drive, which wasn't chosen for install. As other, anecdotal evidence I installed universal-blue bazzite. The anaconda installer isn't as nice as yast and the only option I saw for using two disks was to select both for moving forward in the install. I'm not sure how this works with btrfs, but it shows 1.2 Tb or so of capacity (1 Tb ssd, 256 Gb nvme) for the subvolumes as if it is across both drives. With the idea that I could try this approach with Aeon, I reinstalled Aeon using the new image (RC2) but as far as I'm aware it only lets me choose a single disk. At least this time it installed successfully with no errors and offering to backup my home. It seems that after the defaults of bazzite were written over my custom install, Aeon install worked as an @home subvolume would be on that nvme drive. However, once again I'm stuck only using one drive. I tried editing /etc/fstab to use the secondary drive as @home (replacing the UUID of the primary drive with the second for the @home subvolume line) but it seems that isn't as straightforward with btrfs and subvolumes. It wouldn't boot. So....right now I'm on bazzite hoping that there is a way to use two drives on Aeon, even if it using the subvolumes, growfs, etc across both drives instead of isolating /home to one. Any chance or not supported? Thanks -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c7 --- Comment #7 from Tony Neely <tony.neely@gmail.com> --- Thanks, Richard. Seems like I was close before when editing fstab, I just should have removed the subvolume bit. So, I used cfdisk and mkfs.btrfs to clean up the two drives partitions and went through with the install. After logging into the new system, I edited the existing line in /etc/fstab that mounts /home by replacing the primary drive's UID with secondary drive's UID and removed the subvolume bit. However, after this the system didn't behave as expected. After editing fstab, I rebooted and while I was able to login and show the appropriate drives were mounted correctly, none of the changes from the Aeon firstboot had saved. I ran aeon-mig-firstboot (and later aeon-firstboot) but neither would complete. It stated that it could not mkdir /home/tony and could not install flathub repo. Making /home/tony was easy enough but the strange behavior continued. Every time I opened gnome-terminal it asked if I wanted it to be default. If I tried to pin the terminal icon to the dash, it gave a notification that it had been done but would immediately go back to the app drawer. After creating the /home/tony directory, I ran the firstboots again and each gave the same error about flathub repo not being able to install. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c8 --- Comment #8 from Richard Brown <rbrown@suse.com> ---
It stated that it could not mkdir /home/tony and could not install flathub repo.
I would assume your /home partition already has a tony user, for your tony user account..after all, that's who you should have already been logged in as..no? aeon-firstboot and aeon-mig-firstboot aren't magic. They're required to be run by fully created users (normally created by gnome-initial-setup but ignition or combustion would be fine also) a working valid /home/$USER directory would be mandatory So..if you're trying to stitch things together using your own custom /home arrangement, you need to take care of those basics. That's not going to be something we can ever fully support in Aeon - we have the recommended disk layout we have precisely to avoid stuff like this and the madness it causes :) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c9 --- Comment #9 from Tony Neely <tony.neely@gmail.com> --- Hi Richard, Seems we are miscommunicating. Good luck with the distro. If I can close this bug, I will. If not, please feel free to. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1225689 https://bugzilla.suse.com/show_bug.cgi?id=1225689#c10 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tony.neely@gmail. | |com) | Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Richard Brown <rbrown@suse.com> --- Believed resolved by tik v1.2.1. Please reopen if problem occurs in Aeon release 20240801 or later -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com