Cannot boot having errors

I’m having this error while trying to boot and it’s stuck like that

“Failed to start Anonymizing overlay network for tcp”
This error repeats six time and it’ll stuck:(

Welcome :slight_smile:

We need more details and the garuda-inxi, you can use the live ISO for that.

1 Like

How can I do that?

5 Likes

At a quick internet search, this seems to be a TOR error (often related to permissions).
Strange that it stucks the boot process.
Anyway, in my opinion, you could at least chroot from the live USB into your system and temporarily disable that service ( tor.service).
Then you may want to start digging on the internet for the possible causes, but at least that should give you a bootable system.
Check also for a possible /etc/tor/torrc.pacnew to be merged.

4 Likes

How should I exactly do that?

In the live ISO, open the Garuda Welcome and you should see a chroot button.
That will give you a terminal prompt with root privilege (#) into your system.
If not working, there is also a manual procedure to get there.
Then you should give a:

systemctl disable tor.service
3 Likes

I’ve done this and now I’m stuck on
Loading Linux linux-zen …
Loading initial ramdisk …

3 Likes

There is something strange going on.
In my opinion you should consider restoring the latest working snapshot.

3 Likes

The grub freezes for me after I used it a bit is there a way to rollback using console?

It should be possible but I can't help you with that.
I would rather try using the live USB. If you open Btrfs Assistant -> Snapper, I think it is possible to restore from there.
The disadvantage is that you can't try booting from grub to see what you will get after restoring, but right now it seems to me the situation is difficult, so I would try.

3 Likes

It won’t open and my disk is encrypted is there a tutorial?

Yes, there is–SGS linked it above. It seems like you just skipped right by it. :smirk:

Anyway, I think Tor is a red herring. A misconfiguration in Tor should not prevent your system from booting. I think a kernel bug that is affecting your specific hardware is more likely. Try installing the LTS kernel to test.

This is a good place to start:

From inside the chroot:

pacman -Syu linux-lts linux-lts-headers

exit to get out of the chroot, then reboot and select the new kernel from the advanced options of the Grub menu.

2 Likes

Welcome @devloren. The suggestion to install the LTS kernel from chroot was already mentioned, so it seems odd that you were motivated to create an account just to suggest it again, but welcome nonetheless. :slightly_smiling_face:

Just to clarify:

That is an error from the Tor service. I’m not sure where you got this idea, but I am certain that you are mistaken.

Since that was the only error message the OP had posted, an effort was made to chase that error message even though probably the issue lies elsewhere–that’s why I referred to it as a red herring.

In any case, a potentially better suggestion was made here, to resolve the issue without changing kernels by installing NVIDIA drivers as described:

4 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.