Slow Boot after resizing root

Issues & Assistance
1

I have been using Garuda for a week and it is amazing! However, today I shrunk my Windows partition to add more space to Garuda root. I did so successfully(using a live Garuda USB). But now, my system takes 1 minute to boot(earlier was 2-3 sec), NetworkManager Service does not autostart. Please help me out.

Output of inxi -Fzza

System:    Kernel: 5.10.10-114-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq 
           root=UUID=f2947d3f-0ce7-4b11-8892-ceb656679574 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 
           vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3 
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Garuda Linux 
Machine:   Type: Laptop System: ASUSTeK product: TUF Gaming FX505DD_FX505DD v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: FX505DD v: 1.0 serial: <filter> UEFI: American Megatrends v: FX505DD.315 date: 09/22/2020 
Battery:   ID-1: BAT0 charge: 10.6 Wh condition: 42.0/50.6 Wh (83%) volts: 12.1/12.3 model: FX50442 type: Li-ion serial: N/A 
           status: Charging 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter> charge: 55% (should be ignored) 
           rechargeable: yes status: Discharging 
CPU:       Info: Quad Core model: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen/Zen+ 
           note: check family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108102 L2 cache: 2 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 33575 
           Speed: 1802 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 1: 1802 2: 2767 3: 2753 4: 2765 5: 2768 
           6: 2768 7: 2758 8: 2769 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107M [GeForce GTX 1050 3 GB Max-Q] vendor: ASUSTeK driver: N/A 
           alternate: nouveau, nvidia_drm, nvidia bus ID: 01:00.0 chip ID: 10de:1c91 
           Device-2: Advanced Micro Devices [AMD/ATI] Picasso vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 05:00.0 
           chip ID: 1002:15d8 
           Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus ID: 3-1:2 chip ID: 13d3:56a2 
           serial: <filter> 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: modesetting display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 120 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5") 
           OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.40.0 5.10.10-114-tkg-bmq LLVM 11.0.1) v: 4.6 Mesa 20.3.3 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 05:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.10.10-114-tkg-bmq 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: e000 
           bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: down mac: <filter> 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: AzureWave driver: rtw_8822be v: N/A 
           modules: rtw88_8822be port: d000 bus ID: 04:00.0 chip ID: 10ec:b822 
           IF: wlp4s0 state: up mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 234.82 GiB (20.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520 SDAPNUW-256G-1002 size: 238.47 GiB 
           block size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 serial: <filter> rev: 20110000 temp: 46.9 C 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: SDM4 
Partition: ID-1: / raw size: 172.52 GiB size: 172.52 GiB (100.00%) used: 52.21 GiB (30.3%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-2: /boot/efi raw size: 500 MiB size: 499 MiB (99.80%) used: 29.6 MiB (5.9%) fs: vfat dev: /dev/nvme0n1p1 
           maj-min: 259:1 
           ID-3: /home raw size: 172.52 GiB size: 172.52 GiB (100.00%) used: 52.21 GiB (30.3%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-4: /var/log raw size: 172.52 GiB size: 172.52 GiB (100.00%) used: 52.21 GiB (30.3%) fs: btrfs 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
           ID-5: /var/tmp raw size: 172.52 GiB size: 172.52 GiB (100.00%) used: 52.21 GiB (30.3%) fs: btrfs 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100) 
           ID-1: swap-1 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0 
           ID-2: swap-2 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1 
           ID-3: swap-3 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2 
           ID-4: swap-4 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3 
           ID-5: swap-5 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4 
           ID-6: swap-6 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5 
           ID-7: swap-7 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6 
           ID-8: swap-8 type: zram size: 931 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7 
Sensors:   System Temperatures: cpu: 58.6 C mobo: N/A gpu: amdgpu temp: 58.0 C 
           Fan Speeds (RPM): cpu: 2700 
Info:      Processes: 282 Uptime: 9m wakeups: 3 Memory: 7.27 GiB used: 3.38 GiB (46.4%) Init: systemd v: 247 Compilers: 
           gcc: 10.2.0 clang: 11.0.1 Packages: pacman: 1719 lib: 533 Shell: fish v: 3.1.2 running in: konsole inxi: 3.2.02

Output of systemd-analyze critical-chain

graphical.target @51.480s
└─multi-user.target @51.480s
  └─systemd-swap.service @1.597s +49.883s
    └─basic.target @1.533s
      └─sockets.target @1.533s
        └─virtlogd.socket @1.533s
          └─sysinit.target @1.529s
            └─systemd-timesyncd.service @1.464s +63ms
              └─systemd-tmpfiles-setup.service @1.273s +188ms
                └─local-fs.target @1.270s
                  └─data.mount @972ms +297ms
                    └─local-fs-pre.target @968ms
                      └─lvm2-monitor.service @288ms +679ms
                        └─lvm2-lvmetad.service @447ms
                          └─systemd-udevd.service @355ms +90ms
                            └─systemd-tmpfiles-setup-dev.service @324ms +24ms
                              └─kmod-static-nodes.service @287ms +20ms
                                └─systemd-journald.socket @280ms
                                  └─system.slice @262ms
                                    └─-.slice @262ms
2

Welcome to the forum!

If I understand there are 2 issues:

  1. It boots slowly?
  2. Network-Manager does not start?

What about that OS called Windows? Does it still boot normally?

Did you proceed with any other change whatsoever when you resized the partition? Like performing a package update without rebooting and then you resized the partition, installing a new kernel without rebooting and then resized partition, etc...

1 Like
3

Looks like this is the main culprit. Check its journal entries.

4

Yes those are the issues. Windows boots fine. Slow boot is the issue. No I was fully updated, did not install anything new, did not modify any system file

5

How do I do that?
sudo journalctl -b| grep systemd-swap.service

Is that right?

6

Close,

sudo journalctl -eu systemd-swap.service

-u says which unit to look at, -e skips directly to the end. Add --no-pager if you want to copy-paste.

2 Likes
7

The reason why NM was not starting might be related to that timeout. Maybe Network-Manager.wait-online (not sure how to write it) was timing out or some other service related to NM. I had that kind of issue long ago with another distro, NM was just collateral damage.

At the moment I'd suggest not thinking about NM but definately fixing that slow boot and then see how NM works.

1 Like
8

These are separate issues. It is always best to open a thread for networking issues in the “Networking Suoport” sub forum. That issue is probably caused one of several recently identified bugs. Open a thread for that issue and myself or someone else will surely be able to assist you to correct that problem.

Windows is the root of all problems, best to wipe it and install only Garuda if you want less problems IMO. However, if you enjoy endless troubleshooting, then by all means leave Windows installed. :joy:

Welcome to the forum.

1 Like
9

You need to Balance btrfs filesystem after resizing it.

You can do so via garuda assistant.

5 Likes
10

Aw c'mon, now he's going to keep using M$. :sob: :wink:

1 Like
11

Maybe try this

It sounds similar issue.

2 Likes
12

Um no. I was on Manjaro for a long time, saw this and decided to switch. I only have Windows so that I could try cyberpunk on launch. I was thinking it was time to nuke it(now that we have promises of WINE/Proton being able to run EAC games, and my FL setup works flawlessly on Linux!).
If this issue is not fixed, either I will go back to Manjaro or clean reinstall Garuda. I do not like MS.

13

Output of sudo journalctl -b -eu systemd-swap.service --no-pager 

-- Journal begins at Wed 2021-01-20 20:18:51 IST, ends at Fri 2021-01-29 11:03:58 IST. --
Jan 29 10:58:21 bl4z3pc systemd[1]: Starting Manage swap spaces on zram, files and partitions....
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Load: /etc/systemd/swap.conf.d/swap.conf
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Removing working directory...
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Removing files in /var/lib/systemd-swap/swapfc/...
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Load: /etc/systemd/swap.conf.d/swap.conf
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: WARN: Combining zram with zswap/swapfc/swapd_auto_swapon can lead to LRU inversion and is strongly recommended against
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Zram: check availability
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Zram: not part of kernel, trying to find zram module
Jan 29 10:58:22 bl4z3pc systemd-swap[514]: INFO: Zram: module successfully loaded
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram0
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram1
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:23 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram2
Jan 29 10:58:24 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:24 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram3
Jan 29 10:58:24 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:24 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram4
Jan 29 10:58:25 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:25 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram5
Jan 29 10:58:25 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:25 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram6
Jan 29 10:58:26 bl4z3pc systemd-swap[514]: INFO: Zram: trying to initialize free device
Jan 29 10:58:26 bl4z3pc systemd-swap[514]: INFO: Zram: initialized: /dev/zram7
Jan 29 10:59:11 bl4z3pc systemd-swap[514]: INFO: Writing destroy info...
Jan 29 10:59:11 bl4z3pc systemd-swap[514]: INFO: swapD: pick up devices from systemd-gpt-auto-generator
Jan 29 10:59:11 bl4z3pc systemd-swap[514]: INFO: swapD: searching swap devices
Jan 29 10:59:11 bl4z3pc systemd[1]: Started Manage swap spaces on zram, files and partitions..
14

You need to Balance btrfs filesystem after resizing it.
You can do so via garuda assistant.

I am trying this now, will let you know what happens.

Also my bad, I should have replied to all of you in a single post. Will do that from now, did not realise I could do that.

15

You need to Balance btrfs filesystem after resizing it.

This seems to have fixed it! Thank you.
On another note, I think this is related, so could you tell me how I can nuke M$ and add that storage to my Garuda install(safely this time).

1 Like
16

Well you need to boot to live media
Then delete all ntfs partitions
Then resize btrfs partition to take all space
Then balance filesystem after boot

3 Likes
17

Well you need to boot to live media
Then delete all ntfs partitions

Can’t I delete all NTFS partitions from within Garuda? Using KDE Partition manager. That is what I did last time, after which I booted into the live USB and added the extra space to Garuda and rebooted. Did I mess up?

18

Maybe you can (try), but it is suggested to do this with your system in cold state, as safer.

I am not sure this would not change current system btrfs partition UUID.
I would suggest to create a new btrfs partition in the unused space (deleted partitions space) and after booting to Garuda, add this to your system with btrfs commands (or however).

19

Well it did not change uuid for me when i did resizing.

4 Likes
20

resizing partition won't change UUID. I did it many times :sunglasses: (and also spoiled my hard disk by the way :disappointed:)

1 Like