init 16 - fatal signal: Bus error after installing new world

tembun

tembun

As usual, today I've built the system from stable/15 branch. First, built the kernel, then installed it separately and booted. Everything was fine, so I installed the world. After installing the world I saw an error in the terminal that was similar to the one in the title. I tried to exexute su(1), but it core dumped with the same errror. I rebooted, but the boot stops with this error (see title). I tried to boot the trusted good kernel - same error.

I booted the live syatem from the usb stick and checked if the SSD data is alive - it is, I still have access to my data. I do have backups.

Can I somehow fix the problem without reinstalling the system from the backup? Any help is appreciated!
 
Most likely some shared library changed - most likely libc.so.7 -- try replacing each of the five shared libs that init depends on one by one from a recent backup to see which one broke. What is the commit hash and what is the underlying arch? x86-64, arm64 or something else?

In my view the decision to dynamically link /sbin/init post 15.1 should be considered a bug.
 
bakul said:
Most likely some shared library changed - most likely libc.so.7 -- try replacing each of the five shared libs that init depends on one by one from a recent backup to see which one broke. What is the commit hash and what is the underlying arch? x86-64, arm64 or something else?

In my view the decision to dynamically link /sbin/init post 15.1 should be considered a bug.
Click to expand...
Thanks! Unfortunately, I don't have backups of libraries, I only backup my data in /home and configuration files.

I'm on amd64, I can't see the exact hash, but I pulled the tree today at about 1PM UTC.

I tried to replace init binary to statically linked one from /rescue, and the machine boots, but it's still unusable, because other programs crash.

So, it seems that fresh install and restoring the backup is the only way now?

Well, could I possibly checkout to earlier revision from the live system, rebuild and reinstall the world? Is it worth trying?
 
Hard to say what is the right thing to do as you don't know why things broke. Try copying /lib/libc.os.7 from the live system to your ssd /lib. If that doesn't fix, try copying more stuff. The other four libraries init depends on are: libutil.so.10, libcrypt.so.5, libmd.so.7 & libsys.so.7.

But really it shouldn't have broken so may be there is an issue in your build or somewhere else. To be absolutely sure, you can reinstall 15.1-RELEASE (& patches) but may be you can try replacing shared libs first.
 
bakul said:
Hard to say what is the right thing to do as you don't know why things broke. Try copying /lib/libc.os.7 from the live system to your ssd /lib. If that doesn't fix, try copying more stuff. The other four libraries init depends on are: libutil.so.10, libcrypt.so.5, libmd.so.7 & libsys.so.7.

But really it shouldn't have broken so may be there is an issue in your build or somewhere else. To be absolutely sure, you can reinstall 15.1-RELEASE (& patches) but may be you can try replacing shared libs first.
Click to expand...
Replacing /lib/libc.so.7 to one taken from the live system worked! bakul Thank you so much, mate you literally saved me! I wish I could give you 10 'Thanks' here :)

Well, sure, I haven't figured out the cause of the problem yet, but at least I can now boot into my system and do it here.

I'll post an update if I find what was wrong in my case.
 
I'm still investigating the issue, but maybe it will be helpful: the list of commits before my last stable/15 build and the current one:
 

Attachments

You must log in or register to reply here.
Back
Top