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
System:
  Kernel: 5.18.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC misobasedir=garuda
    misolabel=GARUDA_I3_TALON quiet systemd.show_status=1 systemd.unified_cgroup_hierarchy=1
    driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: i3 v: 4.20.1 info: i3bar vt: 7 dm: LightDM v: 1.30.0 Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170-A v: Rev 1.xx serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 1702 date: 01/28/2016
CPU:
  Info: model: Intel Core i5-6402P bits: 64 type: MCP arch: Skylake-S gen: core 6 built: 2015
    process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 3309 high: 3393 min/max: 800/3400 scaling: driver: intel_pstate
    governor: powersave cores: 1: 3238 2: 3392 3: 3215 4: 3393 bogomips: 22399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia v: 515.57
    alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current (as of 2022-06) arch: Maxwell
    process: TSMC 28nm built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1380 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1360x768 s-dpi: 84 s-size: 411x232mm (16.18x9.13") s-diag: 472mm (18.58")
  Monitor-1: VGA-0 res: 1360x768 hz: 60 dpi: 85 size: 406x229mm (15.98x9.02")
    diag: 466mm (18.35") modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel
    bus-ID: 1-11:5 v: kernel bus-ID: 00:1f.3 chip-ID: 09da:2701 chip-ID: 8086:a170 class-ID: 0300
    class-ID: 0403
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX] vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:0fbc class-ID: 0403
  Device-3: A4Tech Bloody Gaming Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.18.12-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.55 running: yes
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-12:6
    chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
  IF: wlp0s20f0u12 state: down mac: <filter>
Drives:
  Local Storage: total: 1.15 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3B2QGXA7 temp: 38.9 
C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EALX-009BA0 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Blade size: 14.32 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.27 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A gpu: nvidia temp: 42 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 27%
Info:
  Processes: 211 Uptime: 3m wakeups: 0 Memory: 31.27 GiB used: 2.72 GiB (8.7%) Init: systemd
  v: 251 default: graphical tool: systemctl Compilers: gcc: 12.1.0 Packages: pacman: 1244 lib: 305
  Client: shell wrapper v: 5.1.16-release inxi: 3.3.19
Garuda (2.6.5-1):
  System install date:     2022-11-18
  Last full system update: 2022-11-18 ↻
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       <superuser required>
  Snapshots:               Snapper
  Failed units:            

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.