Switch issues - how to get better issue information?

Help
1

I switched back to an older (still running) generation

  • but I’m not sure if the nix output is really true for the current state …

  • system: "x86_64-linux"

  • host os: Linux 5.19.9, NixOS, 22.05 (Quokka), 22.05.3242.72783a2d0db

  • multi-user?: yes

  • sandbox: yes

  • version: nix-env (Nix) 2.8.1

  • channels(root): "home-manager-22.05.tar.gz, nixos-22.05"

  • channels(usera): ""

  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

while in
sudo nix-env --list-generations -p /nix/var/nix/profiles/system

the current running generation is the oldest
In the boot menu s´there is still an deleted generation (via sudo nix-env --profile /nix/var/nix/profiles/system --delete-generations 106) listed

switch breaks the graphical output (X11)

stopping the following units: ModemManager.service, NetworkManager-wait-online.service, NetworkManager.service, accounts-daemon.service, acpid.service, alsa-store.service, audit.service, avahi-daemon.service, avahi-daemon.socket, crio.service, cups-browsed.service, cups.service, cups.socket, docker.service, docker.socket, kmod-static-nodes.service, logrotate-checkconf.service, lxcfs.service, lxd.service, lxd.socket, mount-pstore.service, mullvad-daemon.service, network-local-commands.service, network-setup.service, nscd.service, rtkit-daemon.service, systemd-modules-load.service, systemd-resolved.service, systemd-sysctl.service, systemd-timesyncd.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket, systemd-udevd.service, thermald.service, tlp.service, udisks2.service, upower.service, usbmuxd.service, vsftpd.service, wpa_supplicant.service, xrdp.service
NOT restarting the following changed units: display-manager.service, getty@tty1.service, libvirt-guests.service, systemd-fsck@dev-disk-by\x2duuid-5275\x2d7CA4.service, systemd-journal-flush.service, systemd-logind.service, systemd-random-seed.service, systemd-remount-fs.service, systemd-update-utmp.service, systemd-user-sessions.service, user-runtime-dir@1000.service, user@1000.service, xrdp-sesman.service
activating the configuration...
removing group ‘lxd’
setting up /etc...
removing obsolete symlink ‘/etc/lxc/default.conf’...
removing obsolete symlink ‘/etc/lxc/lxc.conf’...
removing obsolete symlink ‘/etc/lxc/lxc-usernet’...
restarting systemd...
reloading user units for user...
setting up tmpfiles
reloading the following units: dbus.service, firewall.service, reload-systemd-vconsole-setup.service
restarting the following units: dhcpcd.service, network-addresses-eno1.service, network-addresses-wlp110s0.service, nix-daemon.service, polkit.service, sshd.service, systemd-journald.service
starting the following units: ModemManager.service, NetworkManager-wait-online.service, NetworkManager.service, accounts-daemon.service, acpid.service, alsa-store.service, audit.service, avahi-daemon.socket, crio.service, cups-browsed.service, cups.socket, docker.socket, kmod-static-nodes.service, logrotate-checkconf.service, mount-pstore.service, mullvad-daemon.service, network-local-commands.service, network-setup.service, nscd.service, rtkit-daemon.service, systemd-modules-load.service, systemd-resolved.service, systemd-sysctl.service, systemd-timesyncd.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket, thermald.service, tlp.service, udisks2.service, upower.service, usbmuxd.service, vsftpd.service, wpa_supplicant.service, xrdp.service
Failed to start logrotate-checkconf.service: Transaction for logrotate-checkconf.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction).
See system logs and 'systemctl status logrotate-checkconf.service' for details.

with restart it does not boot up - freezes

2

If you read the last line of the log then it gives you pretty clear advise how to proceed.

3

if I switch

  • the system / graphics gets lost (hard to work in this state - blindly if it is not frozen )

booting is not possible in the new generation - it freezes (not possible to get logs … )

4

Can you switch to another TTY and log in? The default keybinding for that is Ctrl+Alt+F1 to F7 where F7 is the graphical one.

5

what is the currently best/working way of testing a new nixos configuration in a vm?

6

nixos-rebuild vm ist Peggy the easiest because it is build in.

7

nixos-rebuild build-vm
builds up …

journalctl -b -k | grep -b2 -a2 -i "error"
shows nothing …

8

Probably a graphics driver issue then, will be hard to debug with a VM.