Arch is not booting, while Windows 11 has no issues.

seth · 2023-12-30 21:51:28

The archiso pattern showed up a couple of times, try "maxcpus=1"
https://bbs.archlinux.org/viewtopic.php … 1#p2128071

Same for the regular boot… alternatively the initramfs is actually corrupted, either for FS issues or because you're running out of space on the boot partition:
https://bbs.archlinux.org/viewtopic.php?id=291332
https://bbs.archlinux.org/viewtopic.php?id=290272

If you can boot the iso and chroot, try to regenerate the initramfs.

Zibi1981 · 2023-12-30 23:38:24

I was finally able to boot "normally" - maybe it is some kind of UEFI/BIOS issue? I did perform couple of upgrades this year as they were released by MSI.

Currently I've reinstalled GRUB and regenerated initramfs, but don't believe this is the cause.

My /boot partition seem to have 41% of free space, so that's not the case.

$ df -h
System plików  rozm. użyte dost. %uż. zamont. na
dev              32G     0   32G   0% /dev
run              32G   29M   32G   1% /run
efivarfs        192K  119K   69K  64% /sys/firmware/efi/efivars
/dev/nvme0n1p6  467G  211G  232G  48% /
tmpfs            32G  147M   32G   1% /dev/shm
/dev/nvme0n1p7  900M  682M  219M  76% /windows_x
/dev/nvme0n1p8   25G   24G  719M  98% /windows_y
tmpfs            32G   43M   32G   1% /tmp
tmpfs            32G  872K   32G   1% /var/spool
tmpfs            32G     0   32G   0% /var/tmp
/dev/nvme0n1p3  400G  107G  294G  27% /windows_c
/dev/nvme0n1p1  296M  175M  122M  59% /boot
tmpfs           6,3G  176K  6,3G   1% /run/user/1000
overlaid        6,3G  176K  6,3G   1% /run/user/1000/psd/zbigniew-vivaldi
overlaid        6,3G  176K  6,3G   1% /run/user/1000/psd/zbigniew-vivaldi-snapshot
overlaid        6,3G  176K  6,3G   1% /run/user/1000/psd/zbigniew-chromium
overlaid        6,3G  176K  6,3G   1% /run/user/1000/psd/zbigniew-opera

A corruption of the Ext4 FS also came to my mind, but I've performed a full checkup using Ashampoo tool under Windows and it didn't detect any issues at all.

Last edited by Zibi1981 (2023-12-30 23:40:55)

seth · 2023-12-31 09:33:47

a full checkup using Ashampoo tool under Windows

https://grml.org

The multithreaded decompression is probably a race condition, but w/ re-installed grub and regenerated initramfs several relevant elements also changed.
(Did it allow you to boot the install iso? How did you "reinstalled GRUB and regenerated initramfs"?)

Zibi1981 · 2023-12-31 09:43:25

seth wrote:

The multithreaded decompression is probably a race condition, but w/ re-installed grub and regenerated initramfs several relevant elements also changed.
(Did it allow you to boot the install iso? How did you "reinstalled GRUB and regenerated initramfs"?)

Under the booted Arch from terminal

# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB --modules="normal test efi_gop efi_uga search echo linux all_video gfxmenu gfxterm_background gfxterm_menu gfxterm loadenv configfile tpm"

# grub-mkconfig -o /boot/grub/grub.cfg

# mkinitcpio -P

Last edited by Zibi1981 (2023-12-31 09:43:46)

seth · 2023-12-31 15:20:08

Under the booted Arch from terminal

So just went away by itself??

Zibi1981 · 2023-12-31 15:24:18

That's right. One time Arch ins't booting at all, the other time it gets stuck at some point, and then, after after several tries - it is able to start.

Eddie_Foss · 2024-01-02 07:58:29

Sorry, it's quite random suggestion but did you checked if drives UUIDs match in fstab file?
With 'blkid' command you can get actual UUIDs

seth · 2024-01-02 10:55:38

If the UUIDs mimatched, you'd get consistent failures.
The zstd errors have previously been linked to SMP, hence "maxcpus=1" worked around that. But while that's "ok" to work around an immediate problem w/ the install is, it's hardly usable on a da-to-day basis.

https://wiki.archlinux.org/title/Mkinitcpio#COMPRESSION
You could try lz4 or, if space doesn't matter, "cat" (uncompressed)

c00ter · 2024-01-02 11:52:52

Zibi1981 wrote:

That's right. One time Arch ins't booting at all, the other time it gets stuck at some point, and then, after after several tries - it is able to start.

I'm wondering if entropy might be a factor?

Zibi1981 · 2024-01-02 13:38:29

Just a thought: could it be due to some GRUB misconfiguration, i.e. inappropriate kernel modules order or error in GRUB_CMDLINE_LINUX_DEFAULT?

Recently I noticed that AppArmor isn't working anymore, which was due to an error above mentioned. I've corrected it now.

seth · 2024-01-02 14:11:50

"kernel modules order"
What did/does your kernel commandline look like right now?

However, the pre-existing SMP pattern is strong and also your install iso boot was affected itr (and that hopefully doesn't come w/ a bogus grub config)

Zibi1981 · 2024-01-02 22:13:55

seth wrote:

"kernel modules order"
What did/does your kernel commandline look like right now?

This is my current /etc/default/grub file

# GRUB boot loader configuration

GRUB_DEFAULT=2
GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet lsm=landlock,lockdown,yama,integrity,apparmor,bpf sysrq_always_enabled=1 loglevel=3 splash audit=1"
GRUB_CMDLINE_LINUX="ibt=off nvidia_drm.modeset=1 ec_sys.write_support=1"

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
GRUB_TERMINAL_OUTPUT="gfxterm"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `videoinfo'
GRUB_GFXMODE=2560x1600x32,1024x768x32,auto
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="green"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/boot/grub/splash.png"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
GRUB_DISABLE_OS_PROBER=false
GRUB_THEME="/usr/share/grub/themes/Vimix/theme.txt"

seth · 2024-01-02 22:20:58

ibt=off should™ no longer be required, drop that. Could be the cause.

Not sure whether apparmor could remotely cause anything like this.

What's up w/ ec_sys.write_support?
The module says "Dangerous, reboot and removal of battery may be needed."?

Zibi1981 · 2024-01-02 22:53:09

seth wrote:

ibt=off should™ no longer be required, drop that. Could be the cause.

It's there from day one of this Arch's instance on my new laptop. If I remember correctly this seemed required when using nVidia proprietary graphics driver, as stated in the wiki. Now I know that modern driver versions should not require this, but there were some reports of people having trouble with nVidia drivers while booting without this kernel parameter.

seth wrote:

Not sure whether apparmor could remotely cause anything like this.

Me neither, although I haven't experienced failed booting since I corrected AppArmor modules entry in GRUB config file...for now at least.

seth wrote:

What's up w/ ec_sys.write_support?
The module says "Dangerous, reboot and removal of battery may be needed."?

It was required for a piece of software designed to give more control over MSI laptops (ISW-Modern), although I've never made it to work. I guess I have to remove this entry.

Last edited by Zibi1981 (2024-01-02 23:15:28)

seth · 2024-01-02 23:01:36

Remove ibt=off, if it's a problem, nvidia won't load w/ an ENDBR error and you can restore it.
If not, it's at least in the vicinity of SMP related decompression errors. (Not saying that it /is/ the cause, but also not that it isn't)

What was the incorrect apparmor entry?

ec_sys.write_support isn't gonna make or break the decompression of the initramfs, I just wanted to give you a heads up because of the modinfo warning.

Zibi1981 · 2024-01-02 23:18:24

I have removed ibt=off and ec_sys.write_support=1 - so far so good, one booting without issues :-)

I don't remember what exactly was wrong with AppArmor modules entry, but I think there were spaces between enumerated modules.

Last edited by Zibi1981 (2024-01-03 10:03:08)

Zibi1981 · 2024-02-01 09:04:54

I wait until KDE/Plasma 6 will be released and the reinstall Arch...I cannot find more strength in me for this...

seth · 2024-02-01 09:21:07

Broken RAM or disk.
Since the disk in this case is the initramfs and there're multiple decompression issues reported on various systems w/o any useful pattern

seth wrote:

https://wiki.archlinux.org/title/Mkinitcpio#COMPRESSION
You could try lz4 or, if space doesn't matter, "cat" (uncompressed)

Did you?

Zibi1981 · 2024-02-01 10:30:25

My disk seems OK, I also haven't experienced any RAM issues.

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.2-arch1-2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZVL22T0HBLB-00B00
Serial Number:                      S677NX0T804375
Firmware Version:                   GXB7601Q
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 2048408248320 [2,04 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2048408248320 [2,04 TB]
Namespace 1 Utilization:            1011538612224 [1,01 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 b821b4e126
Local Time is:                      Thu Feb  1 12:18:58 2024 CET
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     81 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.37W       -        -    0  0  0  0        0       0
 1 +     8.37W       -        -    1  1  1  1        0     200
 2 +     8.37W       -        -    2  2  2  2        0     200
 3 -   0.0500W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        50 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    79650800 [40,7 TB]
Data Units Written:                 34008961 [17,4 TB]
Host Read Commands:                 678616627
Host Write Commands:                513519225
Controller Busy Time:               3212
Power Cycles:                       852
Power On Hours:                     1001
Unsafe Shutdowns:                   102
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               50 Celsius
Temperature Sensor 2:               54 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x002)

Why do you think the initramfs compression method might be causing this strange behavior?

seth · 2024-02-01 14:04:04

the disk in this case is the initramfs and there're multiple decompression issues reported on various systems w/o any useful pattern

Also the nondeterministic behavior, it's just a hunch.

Arch Linux

#26 2023-12-30 21:51:28

Re: Arch is not booting, while Windows 11 has no issues.

#27 2023-12-30 23:38:24

Re: Arch is not booting, while Windows 11 has no issues.

#28 2023-12-31 09:33:47

Re: Arch is not booting, while Windows 11 has no issues.

#29 2023-12-31 09:43:25

Re: Arch is not booting, while Windows 11 has no issues.

#30 2023-12-31 15:20:08

Re: Arch is not booting, while Windows 11 has no issues.

#31 2023-12-31 15:24:18

Re: Arch is not booting, while Windows 11 has no issues.

#32 2024-01-02 07:58:29

Re: Arch is not booting, while Windows 11 has no issues.

#33 2024-01-02 10:55:38

Re: Arch is not booting, while Windows 11 has no issues.

#34 2024-01-02 11:52:52

Re: Arch is not booting, while Windows 11 has no issues.

#35 2024-01-02 13:38:29

Re: Arch is not booting, while Windows 11 has no issues.

#36 2024-01-02 14:11:50

Re: Arch is not booting, while Windows 11 has no issues.

#37 2024-01-02 22:13:55

Re: Arch is not booting, while Windows 11 has no issues.

#38 2024-01-02 22:20:58

Re: Arch is not booting, while Windows 11 has no issues.

#39 2024-01-02 22:53:09

Re: Arch is not booting, while Windows 11 has no issues.

#40 2024-01-02 23:01:36

Re: Arch is not booting, while Windows 11 has no issues.

#41 2024-01-02 23:18:24

Re: Arch is not booting, while Windows 11 has no issues.

#42 2024-02-01 09:04:54

Re: Arch is not booting, while Windows 11 has no issues.

#43 2024-02-01 09:21:07

Re: Arch is not booting, while Windows 11 has no issues.

#44 2024-02-01 10:30:25

Re: Arch is not booting, while Windows 11 has no issues.

#45 2024-02-01 14:04:04

Re: Arch is not booting, while Windows 11 has no issues.

Board footer