Having to chroot Garuda every ~1.5 weeks|bug report

Hello, I have been having this problem for around 7 months now.
I need to chroot into Garuda and reinstall the bootloader every time the laptop goes down to empty battery. I do this by using a portable install of linux on a thinmb drive and then shhing into that system from my tower. I dual boot windows and garuda linux dragonized, but I had the same error when driving the gnome version. safeboot also switches on whenever this happens. I have learned to live with this error, but I would still really like a solution for it.
Is anyone else experiencing this error??

Can you provide your

garuda-inxi

1 Like

Do not let the battery run down.

This is similar to a hard reset, something will break, in your case always grub.

There is no other solution.

Just shut down the computer.

2 Likes
System:
Kernel: 6.1.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=605d4277-a8a4-4df5-bbe5-9dd511155311 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: Razer product: Book 13 - RZ09-0357 v: 0.04
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Razer model: MA310 v: 4 serial: <superuser required> UEFI: Razer
v: 2.00 date: 11/20/2020
Battery:
ID-1: BAT0 charge: 45.2 Wh (85.3%) condition: 53.0/55.2 Wh (96.0%)
volts: 13.1 min: 11.6 model: Razer Blade type: Unknown serial: <filter>
status: charging
CPU:
Info: model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP
arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
microcode: 0xA6
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 2600 high: 2800 min/max: 400/4700 scaling:
driver: intel_pstate governor: powersave cores: 1: 2800 2: 2800 3: 2800
4: 2800 5: 2800 6: 1200 7: 2800 8: 2800 bogomips: 44851
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Razer USA
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
bus-ID: 3-1:2 chip-ID: 13d3:5447 class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48")
s-diag: 599mm (23.57")
Monitor-1: eDP-1 model: Sharp LQ134N1JW48 built: 2020 res: 1920x1200
hz: 60 dpi: 169 gamma: 1.2 size: 288x180mm (11.34x7.09") diag: 340mm (13.4")
ratio: 16:10 modes: 1920x1200
API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Xe Graphics (TGL GT2)
direct render: Yes
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Razer USA
driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:a0c8 class-ID: 0401
Sound API: ALSA v: k6.1.6-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-10:5 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 37.73 GiB (15.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 model: NVMe CA5-8D256 size: 238.47 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
type: SSD serial: <filter> rev: CQ20904 temp: 31.9 C scheme: GPT
Partition:
ID-1: / raw-size: 53.71 GiB size: 53.71 GiB (100.00%)
used: 35.52 GiB (66.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 51.3 MiB (53.4%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /home raw-size: 53.71 GiB size: 53.71 GiB (100.00%)
used: 35.52 GiB (66.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
ID-4: /var/log raw-size: 53.71 GiB size: 53.71 GiB (100.00%)
used: 35.52 GiB (66.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
ID-5: /var/tmp raw-size: 53.71 GiB size: 53.71 GiB (100.00%)
used: 35.52 GiB (66.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.39 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 279 Uptime: 1m wakeups: 1 Memory: 15.39 GiB
used: 3.22 GiB (20.9%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman
pkgs: 1408 libs: 375 tools: octopi,paru,yay Shell: fish v: 3.6.0
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.24
Garuda (2.6.14-1):
System install date:     2022-11-09
Last full system update: 2023-01-19
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Sounds like dead CMOS battery so your NVRAM variables get reset on every battery drain. The chroot guide has a step in which you run grub-install. On that step, add the --removable parameter to the ones ones provided in the guide. A word of warning, this may break Windows boot.

3 Likes

I am trying to do so, but it is kind of a pain when you get to school and you find out that you forgot to shut the laptop down, and then have to use windows for the whole day without having any of stuff on it

could be, but I have to say, the laptop is pretty new(it has like 1 year max), but I will try.

do you mean that as permanent, or will I be still able to boot to it from grub?

Bootloaders are for some reason always the first thing that dies on a hard reset. I wonder why

If it were dead, the computer would not boot.
Anyway, I have experienced it twice so far on desktop PC’s

You may have to do the equialvent of chrooting into Windows and reinstalling bootloader. This has a low chance, though.

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