Arch Linux

khouli

Member

Registered: 2014-12-14

Posts: 70

[SOLVED] Kernel panics on boot, live image chroot segfaults

I'm troubleshooting a system I borked (apparently) by upgrade packages.

I upgraded packages earlier today and a few hours later, XScreenSaver wouldn't accept my password and I couldn't ssh in either. I forced a restart and now I get a kernel panic if I try a standard boot. I'm currently trying to troubleshoot from a live image.

My root directory lives on a RAID 0 array with 2 disks.

The kernel panic seems to happen right after the RAID array is assembled.

From a live image, I'm able to assemble the RAID array (md127, consisting of /dev/sdc1 and /dev/sdg1) using mdadm without issue but I can't chroot.

<code>
mdadm --assemble /dev/md127 /dev/sdc1 /dev/sdg1
mkdir new_root
mount /dev/md127 new_root
chdir new_root
[1] 1136 segmentation fault (core dumped) chroot new_root
</code>

dmesg shows that the segfault is coming from ld-2.25.so.

mdadm -D /dev/md127 lists "State: clean", fsck shows no errors for /dev/md127, and I can access files after mounting.

Live image + chroot is my step 1 for troubleshooting boot issues so at this point I've hit a wall and I'm not sure how to proceed. If chroot is segfaulting, I would have thought that the issue is very likely due to a hardware or filesystem problem but as far as I can tell, that doesn't seem to be the case.

It's been a while since I configured my RAID array. It's totally be possible that I'm doing something boneheaded so don't be afraid to ask "is it plugged in?".

Thanks for reading. Please ask for any other info that would be useful.

Last edited by khouli (2017-08-25 06:05:30)

khouli

Member

Registered: 2014-12-14

Posts: 70

Re: [SOLVED] Kernel panics on boot, live image chroot segfaults

Issue had nothing to do with RAID. chroot was segfaulting due to ld on installed system (I originally thought ld on the live image was segfaulting). This is somehow due to prelink. Immediate solution was to copy ld from live image to installed system. After booting up, I then reinstall every package reporting warnings with pacman -Qkk. Apparently prelink -au could have undone prelink without reinstall packages so that might also have worked.

https://bbs.archlinux.org/viewtopic.php?pid=1725315

https://www.reddit.com/r/archlinux/comm … ks_system/

https://bugs.archlinux.org/task/54820

Last edited by khouli (2017-08-25 08:40:30)