Stop alteratord in /mnt/destination Stopping alteratord service: [ tput: unknown terminfo capability '2' DONE ] [ DONE ] Stop alteratord.service Stopping 'alteratord.service', but its triggering units are still active: alteratord.socket [ DONE ] Stop alteratord.socket [ DONE ] cp: not replacing '/usr/share/install2/postinstall.d/00-remove-installer-pkgs.sh' cp: not replacing '/usr/share/install2/postinstall.d/01-remove-installer-desktop-pkgs.sh' cp: not replacing '/usr/share/install2/postinstall.d/01-remove-pkgs' cp: not replacing '/usr/share/install2/postinstall.d/01-wizard-log.sh' cp: not replacing '/usr/share/install2/postinstall.d/10-increase-raid-limit.sh' cp: not replacing '/usr/share/install2/postinstall.d/30-gen-host-keys.sh' cp: not replacing '/usr/share/install2/postinstall.d/45-setup-dhcp.sh' cp: not replacing '/usr/share/install2/postinstall.d/65-setup-services.sh' cp: not replacing '/usr/share/install2/postinstall.d/66-setup-mdmon.sh' cp: not replacing '/usr/share/install2/postinstall.d/90-clean.sh' cp: not replacing '/usr/share/install2/postinstall.d/90-firsttime.sh' cp: not replacing '/usr/share/install2/postinstall.d/91-alterator-setup' cp: not replacing '/usr/share/install2/postinstall.d/95-dconf-update' cp: not replacing '/usr/share/install2/postinstall.d/99-fstrim' cp: not replacing '/usr/share/install2/postinstall.d/99-online-repo.sh' Running postinstall script [00-remove-installer-pkgs.sh] package alterator-kopidel is not installed Preparing packages... installer-distro-ximper-stage2-0.9-alt1.noarch installer-alterator-pkg-3.2.5-alt1.noarch alterator-vm-0.4.48-alt1.x86_64 installer-livecd-install-0.11.0-alt1.noarch guile-evms-0.6.7-alt1.x86_64 installer-feature-stop-md-dm-stage2-0.7.0-alt1.noarch livecd-rescue-base-utils-1.1-alt6.x86_64 livecd-rescue-utility-0.50-alt2.x86_64 installer-distro-ximper-stage3-0.9-alt1.noarch installer-feature-fstrim-stage2-0.1-alt1.noarch installer-common-stage2-1.16.34-alt1.x86_64 installer-feature-desktop-suspend-stage2-0.6.1-alt1.noarch installer-feature-runlevel5-stage2-0.2-alt1.noarch alterator-preinstall-0.9.2-alt1.noarch installer-common-base-stage2-1.16.34-alt1.x86_64 installer-scripts-remount-stage2-0.7.0-alt1.noarch x11vnc-0.9.17-alt1.x86_64 alterator-luks-0.3.2-alt1.noarch livecd-rescue-launcher-0.1.3-alt2.noarch libevms-2.5.5-alt89.x86_64 alterator-postinstall-0.1-alt3.noarch livecd-auto-hostname-0.1.2-alt1.noarch livecd-timezone-0.1.1-alt1.noarch livecd-net-eth-0.5.4-alt1.noarch livecd-setlocale-0.3.16-alt1.noarch livecd-backlight-max-0.1-alt1.noarch livecd-user-0.3.3-alt1.noarch volumes-profile-kdesktop-0.13.2-alt1.noarch installer-feature-setup-plymouth-0.5.11-alt1.noarch installer-feature-online-repo-0.21-alt1.noarch installer-feature-bootloader-grub-0.1.0-alt4.x86_64 installer-feature-serial-stage3-0.6.4-alt2.noarch installer-feature-alterator-setup-stage2-0.5.2-alt1.noarch Running /usr/lib/rpm/posttrans-filetriggers Reading Package Lists... Building Dependency Tree... The following packages will be REMOVED: alterator-backend-x11 ddcprobe x-cursor-theme-jimmac alterator-datetime etcnet x11presetdrv alterator-datetime-functions etcnet-defaults-server xconsole alterator-grub glibc-timezones xinit alterator-hw-functions ifrename xinitrc alterator-net-eth libXScrnSaver xorg-drv-ati alterator-net-functions libbtrfs xorg-drv-intel alterator-root libmultipath xorg-drv-nouveau alterator-service-functions libvncclient0 xorg-drv-radeon alterator-sysconfig libx86 xorg-drv-video alterator-sysconfig-functions libxf86config xorg-xvfb alterator-users multipath-tools xrandr altlinux-repos passwdqc-utils xsetroot app-defaults sessreg xsetup autologin-sh-functions udev-rules-sgutils avahi-autoipd vhttpd-utils 0 upgraded, 0 newly installed, 46 removed and 0 not upgraded. Need to get 0B of archives. After unpacking 9454kB disk space will be freed. Committing changes... Preparing... ################################# [100%] Cleaning up / removing... 1: alterator-net-eth-5.2.11-alt1 ################################# [ 2%] 2: alterator-backend-x11-1.98.17-alt1 ################################# [ 4%] 3: xorg-drv-video-7.8-alt9 ################################# [ 7%] 4: alterator-datetime-4.9.3-alt3 ################################# [ 9%] 5: alterator-net-functions-2.1.3-alt1 ################################# [ 11%] 6: etcnet-defaults-server-0.9.35-alt1 ################################# [ 13%] 7: etcnet-0.9.35-alt1 #########################warning: /etc/sysconfig/network saved as /etc/sysconfig/network.rpmsave ######## [ 15%] 8: multipath-tools-0.11.1-alt3 ################################# [ 17%] 9: alterator-users-10.27-alt2 ################################# [ 20%] 10: alterator-sysconfig-1.3.29-alt1 ############################warning: /etc/alterator/sysconfig/lang/langlist.all saved as /etc/alterator/sysconfig/lang/langlist.all.rpmsave ##### [ 22%] 11: alterator-datetime-functions-4.9.3-alt3 ################################# [ 24%] 12: xorg-drv-ati-4:22.0.0-alt1 ################################# [ 26%] 13: xorg-drv-intel-8:2.99.917-alt1.20250321 ################################# [ 28%] 14: ddcprobe-3.0-alt1.qa2 ################################# [ 30%] 15: xinit-1.4.1-alt3 ################################# [ 33%] 16: xinitrc-2.4.47-alt4 ################################# [ 35%] 17: alterator-root-1.2-alt1 ################################# [ 37%] 18: alterator-grub-0.29-alt1 ################################# [ 39%] 19: alterator-hw-functions-0.7.8-alt1 ################################# [ 41%] 20: passwdqc-utils-2.0.3-alt3 ################################# [ 43%] 21: app-defaults-0.2.8.5-alt2 ################################# [ 46%] 22: sessreg-1.1.4-alt1 ################################# [ 48%] 23: xconsole-1.0.4-alt1.qa1 ################################# [ 50%] 24: xrandr-1.5.3-alt1 ################################# [ 52%] 25: xsetroot-1.1.2-alt1 ################################# [ 54%] 26: libx86-1.1-alt10 ################################# [ 57%] 27: libXScrnSaver-1.2.4-alt1 ################################# [ 59%] 28: xorg-drv-radeon-4:22.0.0-alt1 ################################# [ 61%] 29: alterator-service-functions-3.0.0-alt4 ################################# [ 63%] 30: vhttpd-utils-0.7.13-alt2 ################################# [ 65%] 31: alterator-sysconfig-functions-1.3.29-alt1 ################################# [ 67%] 32: autologin-sh-functions-0.3.2-alt1 ################################# [ 70%] 33: udev-rules-sgutils-1.48-alt2 ################################# [ 72%] 34: libmultipath-0.11.1-alt3 ################################# [ 74%] 35: ifrename-29-alt11 ################################# [ 76%] 36: glibc-timezones-6:2.40.0.142.2eb180-alt1 ################################# [ 78%] 37: xorg-drv-nouveau-2:1.0.18-alt1 ################################# [ 80%] 38: x11presetdrv-2.1.4-alt1 ################################# [ 83%] 39: libxf86config-1.0-alt2.qa1 ################################# [ 85%] 40: xsetup-1.98.17-alt1 ################################# [ 87%] 41: avahi-autoipd-0.8-alt5 ################################# [ 89%] 42: xorg-xvfb-2:21.1.21-alt1 ################################# [ 91%] 43: x-cursor-theme-jimmac-20030906-alt2 ################################# [ 93%] 44: libvncclient0-0.9.14-alt1 ################################# [ 96%] 45: libbtrfs-6.17.1-alt1 ################################# [ 98%] 46: altlinux-repos-11.0-alt3 ################################# [100%] Done. [ DONE ] Running postinstall script [01-remove-installer-desktop-pkgs.sh] [ DONE ] Running postinstall script [01-remove-pkgs] removing branding-etersoft-ximper-alterator alterator* rpm-macros-alterator guile* libvhttpd autologin-sh-functions Reading Package Lists... Building Dependency Tree... The following packages will be REMOVED: alterator alterator-sh-functions alterator-browser-gui-common alterator-wizardface alterator-browser-qt6 branding-etersoft-ximper-alterator alterator-l10n guile alterator-lookout guile22 alterator-notes libguile-vhttpd alterator-notes-base libvhttpd alterator-notes-utils rpm-macros-alterator 0 upgraded, 0 newly installed, 16 removed and 0 not upgraded. Need to get 0B of archives. After unpacking 57.0MB disk space will be freed. Committing changes... Preparing... ################################# [100%] Cleaning up / removing... 1: alterator-wizardface-2.3-alt2 ################################# [ 6%] 2: alterator-browser-qt6-3.7.4-alt1 ################################# [ 13%] 3: branding-etersoft-ximper-alterator-0.9.3-eter3 ################################# [ 19%] 4: alterator-notes-1.6.0-alt1 ################################# [ 25%] 5: alterator-notes-base-1.6.0-alt1 ################################# [ 31%] 6: alterator-lookout-2.8.1-alt1 ################################# [ 38%] 7: alterator-5.4.5-alt1 ################################# [ 44%] 8: libguile-vhttpd-0.7.13-alt2 ################################# [ 50%] 9: guile-2.2-alt2 ################################# [ 56%] 10: guile22-2.2.7-alt1 ################################# [ 63%] 11: libvhttpd-0.7.13-alt2 ################################# [ 69%] 12: alterator-l10n-2.9.176-alt1 ################################# [ 75%] 13: alterator-sh-functions-0.13-alt4 ################################# [ 81%] 14: rpm-macros-alterator-5.4.5-alt1 ################################# [ 88%] 15: alterator-notes-utils-0.4.2-alt1 ################################# [ 94%] 16: alterator-browser-gui-common-0.1-alt2 ################################# [100%] Done. Reading Package Lists... Building Dependency Tree... The following packages will be REMOVED: distro-licenses libqt6-quickcontrols2impl libqt6-hunspellinputmethod libqt6-quickcontrols2material libqt6-labsanimation libqt6-quickcontrols2materialstyleimpl libqt6-labsfolderlistmodel libqt6-quickdialogs2 libqt6-labsplatform libqt6-quickdialogs2quickimpl libqt6-labssettings libqt6-quickdialogs2utils libqt6-labssharedimage libqt6-quickeffects libqt6-labswavefrontmesh libqt6-quicklayouts libqt6-qmlcore libqt6-quickparticles libqt6-qmllocalstorage libqt6-quickshapes libqt6-qmlnetwork libqt6-quicktemplates2 libqt6-qmlxmllistmodel libqt6-sql libqt6-quickcontrols2 libqt6-virtualkeyboard libqt6-quickcontrols2basic libqt6-virtualkeyboardqml libqt6-quickcontrols2basicstyleimpl libqt6-virtualkeyboardsettings libqt6-quickcontrols2fusion qt6-declarative libqt6-quickcontrols2fusionstyleimpl qt6-translations libqt6-quickcontrols2imagine qt6-virtualkeyboard libqt6-quickcontrols2imaginestyleimpl qt6-virtualkeyboard-common 0 upgraded, 0 newly installed, 38 removed and 0 not upgraded. Need to get 0B of archives. After unpacking 40.7MB disk space will be freed. Committing changes... Preparing... ################################# [100%] Cleaning up / removing... 1: qt6-virtualkeyboard-6.9.3-alt1 ################################# [ 3%] 2: qt6-declarative-6.9.3-alt1 ################################# [ 5%] 3: libqt6-quickcontrols2basic-6.9.3-alt1 ################################# [ 8%] 4: libqt6-quickcontrols2fusion-6.9.3-alt1 ################################# [ 11%] 5: libqt6-quickcontrols2imagine-6.9.3-alt1 ################################# [ 13%] 6: libqt6-quickcontrols2material-6.9.3-alt1 ################################# [ 16%] 7: libqt6-quickcontrols2-6.9.3-alt1 ################################# [ 18%] 8: libqt6-quickcontrols2materialstyleimpl-6.9.3-alt1 ################################# [ 21%] 9: libqt6-quickcontrols2basicstyleimpl-6.9.3-alt1 ################################# [ 24%] 10: libqt6-quickdialogs2-6.9.3-alt1 ################################# [ 26%] 11: libqt6-quickdialogs2quickimpl-6.9.3-alt1 ################################# [ 29%] 12: libqt6-quickcontrols2impl-6.9.3-alt1 ################################# [ 32%] 13: libqt6-labsplatform-6.9.3-alt1 ################################# [ 34%] 14: libqt6-quicktemplates2-6.9.3-alt1 ################################# [ 37%] 15: libqt6-qmllocalstorage-6.9.3-alt1 ################################# [ 39%] 16: libqt6-virtualkeyboardqml-6.9.3-alt1 ################################# [ 42%] 17: libqt6-hunspellinputmethod-6.9.3-alt1 ################################# [ 45%] 18: libqt6-virtualkeyboardsettings-6.9.3-alt1 ################################# [ 47%] 19: libqt6-virtualkeyboard-6.9.3-alt1 ################################# [ 50%] 20: qt6-virtualkeyboard-common-6.9.3-alt1 ################################# [ 53%] 21: libqt6-sql-6.9.3-alt2 ################################# [ 55%] 22: libqt6-quickdialogs2utils-6.9.3-alt1 ################################# [ 58%] 23: libqt6-quickcontrols2imaginestyleimpl-6.9.3-alt1 ################################# [ 61%] 24: libqt6-quickcontrols2fusionstyleimpl-6.9.3-alt1 ################################# [ 63%] 25: libqt6-quickparticles-6.9.3-alt1 ################################# [ 66%] 26: libqt6-quickshapes-6.9.3-alt1 ################################# [ 68%] 27: libqt6-qmlxmllistmodel-6.9.3-alt1 ################################# [ 71%] 28: libqt6-quicklayouts-6.9.3-alt1 ################################# [ 74%] 29: libqt6-qmlcore-6.9.3-alt1 ################################# [ 76%] 30: libqt6-labswavefrontmesh-6.9.3-alt1 ################################# [ 79%] 31: libqt6-labssharedimage-6.9.3-alt1 ################################# [ 82%] 32: libqt6-labssettings-6.9.3-alt1 ################################# [ 84%] 33: libqt6-labsfolderlistmodel-6.9.3-alt1 ################################# [ 87%] 34: libqt6-labsanimation-6.9.3-alt1 ################################# [ 89%] 35: libqt6-quickeffects-6.9.3-alt1 ################################# [ 92%] 36: libqt6-qmlnetwork-6.9.3-alt1 ################################# [ 95%] 37: qt6-translations-6.9.3-alt1 ################################# [ 97%] 38: distro-licenses-1.4.0-alt1 ################################# [100%] Done. [ DONE ] Running postinstall script [01-wizard-log.sh] [ DONE ] Running postinstall script [10-increase-raid-limit.sh] [ DONE ] Running postinstall script [30-gen-host-keys.sh] [ DONE ] Running postinstall script [45-setup-dhcp.sh] [ DONE ] Running postinstall script [65-setup-services.sh] error reading information on service anacron: No such file or directory error reading information on service bridge: No such file or directory error reading information on service clamd: No such file or directory error reading information on service dhcpd: No such file or directory error reading information on service dmeventd: No such file or directory error reading information on service idmapd: No such file or directory error reading information on service krb5kdc: No such file or directory error reading information on service lvm2-lvmetad: No such file or directory error reading information on service netfs: No such file or directory error reading information on service o2cb: No such file or directory error reading information on service ocfs2: No such file or directory error reading information on service postfix: No such file or directory error reading information on service rawdevices: No such file or directory error reading information on service slapd: No such file or directory error reading information on service sysstat: No such file or directory error reading information on service update_wms: No such file or directory error reading information on service xinetd: No such file or directory Synchronizing state of NetworkManager.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable NetworkManager Failed to enable unit: Unit alteratord.service does not exist Failed to enable unit: Unit asusd.service does not exist Synchronizing state of avahi-daemon.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable avahi-daemon Synchronizing state of bluetoothd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable bluetoothd Synchronizing state of chronyd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable chronyd Synchronizing state of cpufreq-simple.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable cpufreq-simple Synchronizing state of cups.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable cups Failed to enable unit: Unit livecd-auto-hostname.service does not exist Failed to enable unit: Unit livecd-backlight-max.service does not exist Failed to enable unit: Unit livecd-evms.service does not exist Failed to enable unit: Unit livecd-fstab.service does not exist Failed to enable unit: Unit livecd-install-wmaker.service does not exist Failed to enable unit: Unit livecd-net-eth.service does not exist Failed to enable unit: Unit livecd-save-nfs.service does not exist Failed to enable unit: Unit livecd-setauth.service does not exist Failed to enable unit: Unit livecd-setlocale.service does not exist Failed to enable unit: Unit livecd-timezone.service does not exist Failed to enable unit: Unit livecd-user.service does not exist Failed to enable unit: Unit network.service does not exist Synchronizing state of plymouth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable plymouth The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit anacron.service does not exist Failed to disable unit: Unit anacron.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of blk-availability.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable blk-availability Failed to disable unit: Unit bridge.service does not exist Failed to disable unit: Unit bridge.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit clamd.service does not exist Failed to disable unit: Unit clamd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit dhcpd.service does not exist Failed to disable unit: Unit dhcpd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit dmeventd.service does not exist Failed to disable unit: Unit dmeventd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of dnsmasq.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable dnsmasq Synchronizing state of gpm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable gpm Synchronizing state of gssd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable gssd The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit idmapd.service does not exist Failed to disable unit: Unit idmapd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit krb5kdc.service does not exist Failed to disable unit: Unit krb5kdc.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit lvm2-lvmetad.service does not exist Failed to disable unit: Unit lvm2-lvmetad.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of lvm2-lvmpolld.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable lvm2-lvmpolld The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of lvm2-monitor.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable lvm2-monitor Synchronizing state of mdadm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable mdadm The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Unit /usr/lib/systemd/system/netfs.service is masked, ignoring. The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit o2cb.service does not exist Failed to disable unit: Unit o2cb.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit ocfs2.service does not exist Failed to disable unit: Unit ocfs2.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of openvpn.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable openvpn Failed to disable unit: Unit postfix.service does not exist Failed to disable unit: Unit postfix.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of powertop.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable powertop Failed to disable unit: Unit rawdevices.service does not exist Failed to disable unit: Unit rawdevices.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of rpcbind.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable rpcbind Failed to disable unit: Unit slapd.service does not exist Failed to disable unit: Unit slapd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Synchronizing state of smartd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable smartd Synchronizing state of sshd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable sshd Failed to disable unit: Unit sysstat.service does not exist Failed to disable unit: Unit sysstat.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit update_wms.service does not exist Failed to disable unit: Unit update_wms.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to disable unit: Unit xinetd.service does not exist Failed to disable unit: Unit xinetd.service does not exist The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. [ DONE ] Running postinstall script [66-setup-mdmon.sh] [ DONE ] Running postinstall script [90-clean.sh] [ DONE ] Running postinstall script [90-firsttime.sh] [ DONE ] Running postinstall script [90-runlevel5.sh] [ DONE ] Running postinstall script [91-alterator-setup] Генерируется файл настройки grub … Найдена тема: /boot/grub/themes/ximper/theme.txt Найден образ linux: /boot/vmlinuz Найден образ initrd: /boot/initrd.img Найден образ linux: /boot/vmlinuz-6.12.63-6.12-alt1 Найден образ initrd: /boot/initrd-6.12.63-6.12-alt1.img Найден образ linux: /boot/vmlinuz-6.12 Найден образ initrd: /boot/initrd-6.12.img Добавляется элемент загрузочного меню для настроек микропрограммы UEFI … Found memtest image: /boot/memtest-8.00.bin Found memtest image: /boot/memtest-8.00.efi Detecting snapshots ... No snapshots found. If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs" Unmount /tmp/grub-btrfs.BlibqtgoNR .. Success завершено [ DONE ] Running postinstall script [95-dconf-update] [ DONE ] Running postinstall script [99-fstrim] running 'fstrim -av' (add notrim to kernel cmdline to suppress) /mnt/destination/boot/efi: 502.8 MiB (527200256 bytes) trimmed on /dev/sda1 /mnt/destination: 22.4 GiB (24086933504 bytes) trimmed on /dev/sda3 [ DONE ] Running postinstall script [99-online-repo.sh] [ DONE ]