Strange Boot Behavior v4
Every Once in a while boot gets stuck on "dev/sda2: clean xxx/xxxxx files xxx/xxxxxx blocks". It takes a few minutes then it displays some text very short and reboots. This reboot only takes a few seconds to boot into blend os. Anyone knows whats causing the first boot stuck problem? Updated a few times, over the last few weeks, still all the same.
Solution:Jump to solution
It seems I fixed it. The simplest thing because it is documented on the official page: https://blendos.co/faq/#why-are-my-aliases-not-showing-up-on-fish In there: "The plasma-track is not working". Did it so far no more failed boots. Will update here if there's still something wrong and if I get 10 or more boots now that work in a row I will consider this solved. Edit after a week: Solved, no issues at all.
FAQ - blendOS
blendOS FAQ
16 Replies
Well you’d need to see what that text was, you can find it using bootctl
I checked out bootctl but could not find an option or at least not obvious for me which option I would have to type in order to get the text output from the failing boot. Do you know? Edit: From a quick search on google I think you mean journalctl not bootctl am i right? But I could not figure out how it lists my failed boots because I only get one boot entry there,
journalctl -b I think
you were right. but i had to make the logs persistent which took me a bit of luck to find out not one but two files that needed changes to 'persistent'. Now I can take a look at least
Perhaps you can see something which is causing this massive delay of like 5 minutes. Reboots then.
it keeps getting SIGINT signals, are you spamming ctrl+c or ctrl+alt+del?
something told systemd to stop booting basically with a SIGINT
Ok so thats right but only like 5 or 6 minutes after nothing happens beeing stuck
I have a strange solution
Are you running the KDE track
Edit /etc/systemd/logind.conf
And restart systemd-logind
And reload systemd
Using systemctl daemon-reload
And it somehow worked
Idk how
with what
Would like to know also how to modify the logind.conf would be appreciated. I discovered that it behaves normal after reboot but the problem accurs after a normal shutdown when switching the pc on again. I read something related to arch having problems with nvidia drivers which would cause this to happen but I use an Intel Arc 750.
Hey is it possible to integrate or to send you the journalctl output of a working vs a nonworking boot (:html files from the termnal) here?
Handlelidswitch
to which parameter I have "#HandleLidSwitch=suspend"
Uncomment it
ok, did so but unfortuantely that did not help
Idk fixed it for me
Solution
It seems I fixed it. The simplest thing because it is documented on the official page: https://blendos.co/faq/#why-are-my-aliases-not-showing-up-on-fish In there: "The plasma-track is not working". Did it so far no more failed boots. Will update here if there's still something wrong and if I get 10 or more boots now that work in a row I will consider this solved. Edit after a week: Solved, no issues at all.
FAQ - blendOS
blendOS FAQ