Segfault halting boot up

Support
1

Hi everyone. I am having trouble with a segfault which keeps preventing me from being able to boot up. It started the other day when a family member had a frozen screen, which was the second time in the last couple of weeks that the computer did this. As with the first time, I proceeded to restart the computer, only unlike the first time, it did not work and I got the segfault error. The following is from the most recent start up attempt:

[  94.084804] systemd[1]: segfault at 7ffdd0a48a88 ip 00007f68e04b5388 sp 00007ffdd0a48a88 error 6 in libsystemd-shared-255.2-2.so[7f68e0319000+287000]
[  94.086201] Code: ff 15 8c 69 20 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 81 ec 00 10 00 00 <48> 83 0c 24 00 48 81 ec 98 01 00 00 89 bd 7c ee ff ff 89 f3 4d 89
[  94.088391] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000008b
[  94.091713] CPU: 3 PID: 1 Comm: systemd Not tainted 5.10.206-1-MANJARO #1
[  94.091713] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Pro4, BIOS P1.60 11/05/2018
[  94.091713] Call Trace:
[  94.091713]  dump_stack+0x6b/0x83
[  94.091713]  panic+0x11a/0x2ee
[  94.091713]  do_exit.cold+0x2c/0xb3
[  94.091713]  do_group_exit+0x33/0xa0
[  94.091713]  get_signal+0x107/0x8f0
[  94.091713]  arch_do_signal_or_restart+0xb3/0x740
[  94.091713]  exit_to_user_mode_prepare+0xd0/0x160
[  94.091713]  ? asm_exc_page_fault+0x8/0x30
[  94.091713]  irqentry_exit_to_user_mode+0x5/0x20
[  94.091713]  asm_exc_page_fault+0x1e/0x30
[  94.091713] RIP: 0033:0x7f68e04b5388
[  94.091713] Code: ff 15 8c 69 20 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 81 ec 00 10 00 00 <48> 83 0c 24 00 48 81 ec 98 01 00 00 89 bd 7c ee ff ff 89 f3 4d 89
[  94.091713] RSP: 002b:00007ffdd0a48a88 EFLAGS: 00010206
[  94.091713] RAX: 0000000000000000 RBX: 00007ffdd049ba0 RCX: 000000000000006f
[  94.091713] RDX: 0000564922533612 RSI: 0000000000000000 RDI: 0000000000000000
[  94.091713] RBP: 00007ffdd0a49ab0 R08: 0000564922536ce2 R09: 0000564922533940
[  94.091713] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000e00cc860
[  94.091713] R13: 00007ffdd0a49ba8 R14: 0000000000000923 R15: 0000564922533612
[  94.091713] Kernel Offset: 0x39a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[  94.091713] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000008b ]---

Things I have tried:

  1. Replaced ram (ran old sticks through Memtest86+ v.7 and they were bad). New ram didn’t help (ran them through a few passes of Memtest and they’re good), but it did spit out some more information during the boot process than the old ram did.

  2. Tried booting using different kernels: 6.6.10-1-MANJARO x64, 6.1.71-1-MANJARO x64, 5.15.146-1-MANJARO x64, 5.10.206-1-MANJARO x64.

  3. Tried editing the run-levels.

  4. Tried using a live USB and chroot to access my system but received this:

[manjaro@manjaro ~]$ manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda1]
 --> mount: [/mnt]
[manjaro /]#

At this point I don’t know where to turn next so I am hoping someone can help out. Thanks and much appreciation in advance.

2

This looks normal to me - you are in chroot at the end.
Now you can run updates or check the system logs for what might be the cause.

It’s a bit confusing because your original user name and host name apparently are the same as the default in chroot.

3

This can have unexpected consequences

ALL file system operations go through RAM. If data is corrupted, it ends up corrupted on the disk. As long as this concerns files, this is usually painful. But if it hits file system management information, it is fatal.

I would strongly advise backing up important data and then writing the system off as “lost” (and reinstall). Otherwise, long-term consequences could occur that result in a total loss of data. (Even if the RAM doesn’t add any new bugs from now on)

Tip: btrfs would immediately raise an alarm in the event of such problems (the file system immediately becomes readonly to prevent further damage)
:footprints:

1 Like
4

Thank you. I backed up all important data and will reinstall. Much appreciated for the quick reply.

1 Like
5

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