recently switched to suite66 and right about when "modules-kernel: info: starts..." comes up, it "freezes" and the log at /run/66/log/0/current gets spammed with the line in the title. Funnily enough, I can switch to tty12 just fine and start X, in fact, I am posting from that X session right now.
"Full" log below:
2021-07-20 12:50:27.848137887 [Initiate db of tree boot...]
2021-07-20 12:50:27.877928629 [Start db services of tree boot...]
2021-07-20 12:50:27.897267312 mount-proc: info: starts...
2021-07-20 12:50:27.897588693 system-hostname: info: starts...
2021-07-20 12:50:27.897794407 mount-tmp: info: starts...
2021-07-20 12:50:27.898000836 mount-run: info: starts...
2021-07-20 12:50:27.903469260 populate-run: info: starts...
2021-07-20 12:50:27.905189410 mount-sys: info: starts...
2021-07-20 12:50:27.910013030 populate-tmp: info: starts...
2021-07-20 12:50:27.910397129 mount-dev: info: starts...
2021-07-20 12:50:27.910620854 populate-sys: info: starts...
2021-07-20 12:50:27.924231046 populate-dev: info: starts...
2021-07-20 12:50:27.924566697 mount-cgroups: info: starts...
2021-07-20 12:50:27.925959603 mount-pts: info: starts...
2021-07-20 12:50:27.926163278 mount-shm: info: starts...
2021-07-20 12:50:27.963570942 system-random: info: starts...
2021-07-20 12:50:27.964062996 system-sysctl: info: starts...
2021-07-20 12:50:27.964315785 modules-kernel: info: starts...
2021-07-20 12:50:27.965428774 modules-system: info: starts...
2021-07-20 12:50:27.965811362 system-hwclock: info: starts...
2021-07-20 12:50:27.975153067 * Applying /usr/lib/sysctl.d/10-artix.conf ...
2021-07-20 12:50:27.975156821 fs.inotify.max_user_instances = 1024
2021-07-20 12:50:27.975158746 fs.inotify.max_user_watches = 524288
2021-07-20 12:50:27.975160807 * Applying /usr/lib/sysctl.d/60-libvirtd.conf ...
2021-07-20 12:50:27.975162528 fs.aio-max-nr = 1048576
2021-07-20 12:50:27.975174459 * Applying /etc/sysctl.d/99_magic_sysrq.conf ...
2021-07-20 12:50:27.975176451 kernel.sysrq = 1
2021-07-20 12:50:29.183512281 udevadm: info: starts...
2021-07-20 12:50:29.749673048 system-fontnkey: info: starts...
2021-07-20 12:50:29.804867086 system-fsck: info: starts...
2021-07-20 12:50:29.817999405 e2fsck: Cannot continue, aborting.
2021-07-20 12:50:29.818002639
2021-07-20 12:50:29.818003484
2021-07-20 12:50:29.818310129 system-fsck: info: /dev/sdb3 is mounted.
2021-07-20 12:50:29.824108706 mount-fstab: info: starts...
2021-07-20 12:50:30.748366232 mount-rw: info: starts...
2021-07-20 12:50:30.756977285 mount-netfs: info: starts...
2021-07-20 12:50:30.757200498 local-loop: info: starts...
2021-07-20 12:50:30.757441843 mount-swap: info: starts...
2021-07-20 12:50:30.757685406 local-sysusers: info: starts...
2021-07-20 12:50:30.759123714 local-locale: info: starts...
2021-07-20 12:50:30.759400936 local-tmpfiles: info: starts...
2021-07-20 12:50:30.759646071 local-time: info: starts...
2021-07-20 12:50:30.761627507 local-sethostname: info: starts...
2021-07-20 12:50:30.761881756 local-authfiles: info: starts...
2021-07-20 12:50:30.792501220 local-dmesg: info: starts...
2021-07-20 12:50:30.802879503 all-Runtime: info: starts...
2021-07-20 12:50:30.889112676 mount-tmp: info: starts...
2021-07-20 12:50:30.889316203 mount-run: info: starts...
2021-07-20 12:50:30.892824199 system-hostname: info: starts...
2021-07-20 12:50:30.893695344 mount-proc: info: starts...
2021-07-20 12:50:30.901470430 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:30.908734766 populate-tmp: info: starts...
2021-07-20 12:50:30.911985749 populate-run: info: starts...
2021-07-20 12:50:30.913012620 mount-sys: info: starts...
2021-07-20 12:50:30.920742132 mount-dev: info: starts...
2021-07-20 12:50:30.928321281 populate-sys: info: starts...
2021-07-20 12:50:30.943552524 populate-dev: info: starts...
2021-07-20 12:50:30.950818645 mount-cgroups: info: starts...
2021-07-20 12:50:30.958186989 mount-shm: info: starts...
2021-07-20 12:50:30.965551885 mount-pts: info: starts...
2021-07-20 12:50:30.977939929 modules-kernel: info: starts...
2021-07-20 12:50:31.891155218 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:32.892103051 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:33.892767074 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:34.893763109 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:35.894313091 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:36.895189884 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:37.895396260 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:38.896398773 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:39.896642884 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:40.897838321 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2021-07-20 12:50:41.898814329 s6-log: fatal: unable to lock /run/66/log/udevd/lock: Device or resource busy
2
What does your tree look like?
sudo 66-intree ?
Out of curiosity does rm-ing the lock file and restarting help
Yep anytime there is a boot issue with 66 tty12 is available atleast until the issue can be fixed
Here is the output for 66-intree
$ sudo 66-intree
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : tty-earlier@tty12 system-hostname mount-run populate-run mount-tmp
populate-tmp mount-proc mount-sys populate-sys mount-dev mount-pts
mount-shm populate-dev mount-cgroups 00 all-Mount system-hwclock
modules-kernel system-random modules-system system-sysctl udevd-log
udevd udevadm system-fontnkey system-fsck mount-fstab all-System
mount-rw mount-swap mount-netfs local-loop local-sethostname
local-time local-authfiles local-tmpfiles local-sysusers local-dmesg
local-locale all-Local all-Runtime All tty-rc@tty3 tty-rc@tty2
tty-rc@tty1 boot@system
Name : default
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : root
Symlinks : svc->backup db->source
Contents : wpa_supplicant-log hdparm-log cronie-log dhcpcd-log dhcpcd acpid-log
hdparm openvpn-log wpa_supplicant acpid openvpn cronie mount-proc
mount-sys mount-dev mount-pts mount-cgroups sshd-log sshd dbus-log
dbus elogind-log elogind mount-tmp alsa NetworkManager-log
NetworkManager mount-run connmand-log connmand syslog-ng-log
virtlockd-log populate-run syslog-ng haveged-log virtlockd-socket
mdadm-log mdadm system-hostname populate-tmp populate-sys mount-shm
populate-dev 00 modules-kernel udevd-log udevd cupsd-log libvirtd-log
virtlockd haveged virtlogd-log virtlogd libvirtd cupsd
And yeah, I just deleted the lock file and it came back right away and the following message appeared in the log
2021-07-20 14:55:00.165155701 66-all: fatal: unable to start atomic services list
2021-07-20 14:55:00.166738628 all-Runtime: fatal: crashed! -- Your machine is operational
but some runtime service failed to start correctly. Please see the complete boot log at /run/66/log/0/current for further information.
tty1 now gives me the option to log in but I will restart first. brb
Just restarted and I got the same error as before. Only deleting the lock file allows me to log in, although, as that log said, some runtime service failed to start correctly.
You have 00 duplicated in default, while populate-tmp is in default instead of boot. It seems that your tree is not set up correctly. Here's mine:
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : tty-earlier@tty12 system-hostname mount-run
populate-run mount-tmp populate-tmp mount-proc mount-sys populate-sys
mount-dev mount-pts mount-shm populate-dev mount-cgroups 00 all-Mount
modules-kernel udevd-log udevd udevadm devices-lvm system-Devices
system-fontnkey system-fsck mount-fstab system-hwclock system-random
modules-system system-sysctl all-System mount-rw mount-netfs
mount-swap local-loop local-sethostname local-time local-authfiles
local-tmpfiles local-sysusers local-rc local-dmesg local-locale
all-Local all-Runtime All tty-rc@tty1 tty-rc@tty2 tty-rc@tty4
tty-rc@tty5 tty-rc@tty3 boot@system
Name : default
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : root
Symlinks : svc->source db->source
Contents : acpid-log acpid dhcpcd-log dhcpcd chrony-log chrony
transmission-log transmission atd-log atd syncthing-log syncthing
cronie-log cronie connmand-log cupsd-log haveged-log haveged ufw
rpcbind-log rpcbind dbus-log dbus colord-log colord apache-log
lvm2-monitor syslog-ng-log syslog-ng cupsd apache lvm2-pvscan
lvmpolld-log lvmpolld alsa connmand
Follow the guide here to set up 66 correctly: https://wiki.artixlinux.org/Main/Suite66
Yep you have boot related stuff also in default tree and should only be in boot
Yeah, thanks. I think what happened is that I accidentally enabled udevd in the default tree while migrating from runit to 66. It all works flawlessly now.