Skip to content

Installation fails with systemd-repart no space left on device on 2TB SSD #47

@vyskocilm

Description

@vyskocilm

Describe the bug
Installation on brand new Lenovo Thinkpad P14, 64GB of RAM, 2TB of SSD, existing Windows partition. tik fails immediately after clicking on a Install and confirm that the installation will wipe the drive. The tik log says systemd-repart fails with no space left on a device.

Note that using older Aeon installer (VERSION="20250923") succeed on the same hardware.

To Reproduce

  1. boot the installer
  2. click on install
  3. agree with disk being wiped out
  4. fail!

Expected behavior
Aeon installed.

tik log
tik.log

/etc/os-release

NAME="Aeon"
# VERSION="20260207"
ID="aeon"
ID_LIKE="suse opensuse opensuse-tumbleweed opensuse-microos opensuse-aeon microos"
VERSION_ID="20260207"
PRETTY_NAME="Aeon"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:aeon:20260207"
BUG_REPORT_URL="https://aeondesktop.org/reportbug"
SUPPORT_URL="https://aeondesktop.org/bugs"
HOME_URL="https://aeondesktop.org/"
DOCUMENTATION_URL="https://aeondesktop.org/docs"
LOGO="distributor-logo-Aeon"

Additional context

I tried to debug the problem further - the tik.log says Failed to link temporary file [/etc/fstab.repart] file exists. What I found weird it that there are two files /etc/fstab and /etc/fstab.repart before installation starts. The later one has wrong UUIDs, which does not match the content of /dev. I tried to do sudo rm -f /etc/fstab.repart before clicking OK, but tik failed with the same error just a few minutes later. Attached as tik2.log. The [disk.txt] contains the result of ls -lh /dev/disk/by-uuid.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions