Skip to main content ↑ ↓
Topic: Unable to boot after latest update (Read 2241 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Unable to boot after latest update

Reply #16 –
No, doesn't work. Just upgraded for sharing the logs and then downgraded back to earlier version.

Re: Unable to boot after latest update

Reply #18 –
Actually providing that file on a successful start as well would be helpful. Presumably a service deadlocks. mount-fstab seems like the culprit but on paper it shouldn't be possible. Anyways a compare/contrast between a successful start and a bad start would help.

Re: Unable to boot after latest update

Reply #22 –
What does your tree look like: 66-intree

Re: Unable to boot after latest update

Reply #23 –
Thanks for all the logging so far. So far, I have noticed that mount-swap does not appear to start for you on the new upgrade for some reason. If that oneshot really never starts, that would explain why you hang during boot at least. Verbosity 6 is apparently far too much logging information. Instead, could you set it to 2 and redo the logs one more time for both the bad and good case? Thanks!

Re: Unable to boot after latest update

Reply #24 –
https://paste.artixlinux.org/62e29710 - Current bad

https://paste.artixlinux.org/d005e4cf - Current good

VERBOSITY=2
LIVE=/run/66
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
TREE=boot
RCINIT=/etc/66/rc.init
RCSHUTDOWN=/etc/66/rc.shutdown
RCSHUTDOWNFINAL=/etc/66/rc.shutdown.final
UMASK=0022
RESCAN=0
CONTAINER=0
RCINIT_CONTAINER=/etc/66/rc.init.container
CATCHLOG=1

Re: Unable to boot after latest update

Reply #25 –
What does your tree look like: 66-intree

Re: Unable to boot after latest update

Reply #26 –
Quote from: ndowens – on
What does your tree look like: 66-intree

Name         : audio
Initialized  : no
Enabled      : yes
Starts after : None
Current      : yes
Symlinks     : svc->source db->backup
Contents     : pipewired-log pipewired

Re: Unable to boot after latest update

Reply #27 –
That should not be all your trees; there should be boot, and default

Re: Unable to boot after latest update

Reply #28 –
@mubh 

To add the default tree, you can run
Code: [Select]
# 66-tree -ncE default
# 66-env -t boot boot@system
# 66-enable -t boot -F boot@system

Then populate the default tree. You need at least these services:
Code: [Select]
acpid dhcpcd dbus logind syslog-ng
plus your network manager, if any, and any other services you are using. You can add just those listed services using the command:
Code: [Select]
# 66-enable -t default acpid dhcpcd dbus logind syslog-ng
# 66-all -t default up

If you need to add pipewired to the default tree, the commands are:
Code: [Select]
# 66-enable -t default pipewired
# 66-start -t default pipewired

Update: Information on how to create "boot" and "default" trees from scratch is added to the wiki entry on suite66 (TL;DR section at the top).

Re: Unable to boot after latest update

Reply #29 –
@strajder - Thanks for the commands on setting up the tree and the services.

For now, I'm not changing anything on my system. I saw there was one more update 1.7.1.7-1 on the suite66-scripts, i upgraded to that version however i was again faced with a non booting system,  so downgraded  back. I will have to keep ignoring suite66 updates until i find a newer version that works.

We can close this thread if there is no other solution that is likely to fix the issue that i'm having.

Thanks for all your help.