You are not logged in.

#1 2025-04-18 20:24:55

maxiy2a
Guest

LUKS encrypted system keeps breaking filesystem after reboot

I am trying to set up arch with LUKS encryption on my Lenovo laptop and the setup described in the wiki is straight forward.The setup also works and I can log into my system. However, after a couple of reboots, my ext4 filesystem gets completely destroyed - checksum errors etc.

Keep in mind that I can use an unencrypted Arch system on my Device without any problems.

When inspecting the dmesg logs, I found a kernel panic error that only seems to be present in dmesg after the filesystem gets corrupted (see at the bottom).

I am not quite sure if this is this behavior is related to the kernel panic, but since I was able to find this only in the dmesg after the ext4 gets destroyed, I am guessing that this might be the issue. I would appreciate if someone can help me out with this!

Here is my bone fides that I've configured the system correctly and that I've tried pretty much everything:

CONFIGURATIONS
Here are my config files for LUKS:

mkinitcpio.conf HOOKS

HOOKS=(base systemd autodetect microcode modconf kms keyboard block sd-encrypt filesystems fsck)

bootloder

default arch.conf
editor no
timeout 3
console-mode keep

bootloader entry

title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options rd.luks.name=ad4d36b9-6f6b-4e93-be6e-0f8ae228eb67=root root=/dev/mapper/root rw nvme_core.default_ps_max_latency_us=0

lsblk

nvme1n1                                                                                                  
├─nvme1n1p1 vfat        FAT32                        6C7B-159B                             985.2M     4% 
└─nvme1n1p2 crypto_LUKS 2                            ad4d36b9-6f6b-4e93-be6e-0f8ae228eb67                
  └─root    ext4        1.0                          f0f5a831-ea8b-4601-9fd0-d0451ab4acdb  864.9G     0% 

My BIOS has the newest version installed from the official vendor website.

HARDWARE
I have bought a completely new NVME drive for this and memtest86 passed 3 times without any errors. I don't think that hardware is the issue here

WHAT I HAVE TRIED
I have tried using archinstall's / UBUNTU's automated LUKS configuration, which also broke
I tried siabling the nouveau driver because I found a cut here realted to it in the dmesg
I tried setting nvme_core.default_ps_max_latency_us=0 and nvme.noacpi=1

KERNEL PANIC

[   18.880465] ------------[ cut here ]------------
[   18.880469] Unpatched return thunk in use. This should not happen!
[   18.880472] WARNING: CPU: 4 PID: 744 at arch/x86/kernel/cpu/bugs.c:3070 __warn_thunk+0x2a/0x40
[   18.880478] Modules linked in: videobuf2_common wl(POE+) snd_pci_acp5x snd_intel_dspcfg snd_intel_sdw_acpi videodev snd_hda_codec mousedev mc snd_hda_core ee1004 snd_hwdep snd_pcm snd_timer snd soundcore crct10dif_pclmul snd_rn_pci_acp3x iwlwifi hid_multitouch polyval_clmulni btusb ucsi_acpi(+) polyval_generic btrtl btintel btbcm typec_ucsi typec btmtk snd_acp_config sp5100_tco roles snd_soc_acpi i2c_hid_acpi wmi_bmof ideapad_laptop bluetooth ghash_clmulni_intel i2c_hid i2c_piix4 platform_profile sparse_keymap cm32181 sha1_ssse3 snd_pci_acp3x psmouse i2c_smbus rapl cfg80211 ccp k10temp rfkill joydev industrialio mac_hid pcspkr acpi_cpufreq pkcs8_key_parser dm_mod nfnetlink ip_tables x_tables overlay squashfs loop isofs cdrom hid_generic usbhid amdgpu nouveau crc32_pclmul mxm_wmi crc32c_intel drm_gpuvm amdxcp sha512_ssse3 drm_exec sha256_ssse3 drm_panel_backlight_quirks gpu_sched drm_buddy r8169 aesni_intel drm_ttm_helper ttm gf128mul realtek nvme crypto_simd drm_suballoc_helper i2c_algo_bit uas mdio_devres nvme_core
[   18.880574]  cryptd drm_display_helper usb_storage libphy nvme_auth cec serio_raw atkbd libps2 vivaldi_fmap i8042 video serio wmi
[   18.880591] CPU: 4 UID: 0 PID: 744 Comm: (udev-worker) Tainted: P        W  OE      6.13.8-arch1-1 #1 456fce73f556a6ef8edc444db474316a8147249d
[   18.880596] Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[   18.880598] Hardware name: LENOVO 82B5/LNVNB161216, BIOS EUCN41WW 09/20/2023
[   18.880600] RIP: 0010:__warn_thunk+0x2a/0x40
[   18.880603] Code: 66 0f 1f 00 0f 1f 44 00 00 80 3d b8 27 59 02 00 74 05 e9 89 8c fb 00 48 c7 c7 30 6a f7 a0 c6 05 a3 27 59 02 01 e8 36 41 06 00 <0f> 0b e9 6f 8c fb 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
[   18.880605] RSP: 0018:ffffac20c1be7a28 EFLAGS: 00010282
[   18.880608] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
[   18.880610] RDX: ffff9a65ff4218c8 RSI: 0000000000000001 RDI: ffff9a65ff4218c0
[   18.880612] RBP: ffffac20c1be7a78 R08: 0000000000000000 R09: ffffac20c1be78a8
[   18.880613] R10: ffffffffa18b5448 R11: 0000000000000003 R12: ffffffffc26e4aa5
[   18.880615] R13: ffffac20c1be7ac0 R14: ffff9a630375e6c0 R15: ffff9a630450dcf0
[   18.880617] FS:  00007f739b71f880(0000) GS:ffff9a65ff400000(0000) knlGS:0000000000000000
[   18.880619] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   18.880621] CR2: 00007f739a8d831b CR3: 00000001111c6000 CR4: 0000000000350ef0
[   18.880624] Call Trace:
[   18.880626]  <TASK>
[   18.880628]  ? __warn_thunk+0x2a/0x40
[   18.880631]  ? __warn.cold+0x93/0xf6
[   18.880633]  ? __warn_thunk+0x2a/0x40
[   18.880639]  ? report_bug+0xff/0x140
[   18.880643]  ? console_unlock+0x9d/0x140
[   18.880647]  ? handle_bug+0x58/0x90
[   18.880650]  ? exc_invalid_op+0x17/0x70
[   18.880654]  ? asm_exc_invalid_op+0x1a/0x20
[   18.880661]  ? __warn_thunk+0x2a/0x40
[   18.880663]  ? __warn_thunk+0x2a/0x40
[   18.880666]  warn_thunk_thunk+0x1a/0x30
[   18.880671]  getvar+0x20/0x70 [wl 65965ac5ae4c2f96673446ac429a5282b42f8731]
[   18.880706]  ? __UNIQUE_ID_vermagic470+0x53def82e5960/0x53def82e5960 [wl 65965ac5ae4c2f96673446ac429a5282b42f8731]
[   18.880735]  wl_module_init+0x17/0xa0 [wl 65965ac5ae4c2f96673446ac429a5282b42f8731]
[   18.880762]  ? do_one_initcall+0x5b/0x310
[   18.880768]  ? do_init_module+0x60/0x230
[   18.880771]  ? init_module_from_file+0x89/0xe0
[   18.880778]  ? idempotent_init_module+0x115/0x310
[   18.880784]  ? __x64_sys_finit_module+0x65/0xc0
[   18.880787]  ? do_syscall_64+0x82/0x190
[   18.880791]  ? vfs_read+0x15e/0x370
[   18.880794]  ? srso_return_thunk+0x5/0x5f
[   18.880798]  ? vfs_read+0x15e/0x370
[   18.880800]  ? srso_return_thunk+0x5/0x5f
[   18.880803]  ? __rseq_handle_notify_resume+0xa2/0x4d0
[   18.880808]  ? srso_return_thunk+0x5/0x5f
[   18.880810]  ? switch_fpu_return+0x4e/0xd0
[   18.880814]  ? srso_return_thunk+0x5/0x5f
[   18.880816]  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
[   18.880820]  ? srso_return_thunk+0x5/0x5f
[   18.880822]  ? syscall_exit_to_user_mode+0x37/0x1c0
[   18.880826]  ? srso_return_thunk+0x5/0x5f
[   18.880828]  ? do_syscall_64+0x8e/0x190
[   18.880832]  ? srso_return_thunk+0x5/0x5f
[   18.880835]  ? do_sys_openat2+0x9c/0xe0
[   18.880839]  ? srso_return_thunk+0x5/0x5f
[   18.880842]  ? syscall_exit_to_user_mode_prepare+0x15e/0x1a0
[   18.880845]  ? srso_return_thunk+0x5/0x5f
[   18.880847]  ? syscall_exit_to_user_mode+0x37/0x1c0
[   18.880850]  ? srso_return_thunk+0x5/0x5f
[   18.880853]  ? do_syscall_64+0x8e/0x190
[   18.880855]  ? srso_return_thunk+0x5/0x5f
[   18.880858]  ? do_syscall_64+0x8e/0x190
[   18.880862]  ? srso_return_thunk+0x5/0x5f
[   18.880864]  ? srso_return_thunk+0x5/0x5f
[   18.880868]  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
[   18.880874]  </TASK>
[   18.880876] ---[ end trace 0000000000000000 ]---

Last edited by maxiy2a (2025-04-18 20:43:30)

#2 2025-04-18 22:48:58

qu@rk
Member
Registered: 2021-07-28
Posts: 149

Re: LUKS encrypted system keeps breaking filesystem after reboot

PCIe bus issues could cause it. I experienced the same while playing with PCIe clock. Might be something else related to it, but you're on a laptop. Check bios for spread spectrum (only GPU related but could misbehave and upset the bus somehow), any kind of overclocking you did in BIOS? Is it a gaming laptop?

Offline

#3 2025-04-19 00:34:40

maxiy2a
Guest

Re: LUKS encrypted system keeps breaking filesystem after reboot

qu@rk wrote:

PCIe bus issues could cause it. I experienced the same while playing with PCIe clock. Might be something else related to it, but you're on a laptop. Check bios for spread spectrum (only GPU related but could misbehave and upset the bus somehow), any kind of overclocking you did in BIOS? Is it a gaming laptop?

Yes it is a gaming laptop. I haven't done any overclocking myself and I believe anything related to it is turned off by default in the BIOS.

Board footer

Powered by FluxBB