One of my systems doesn't work and can't boot again, after update of glibc-solibs.
This happened just after an upgrade of glibc-* on Slint64-14.2 (but I don't know if/how this can be related to that):
Code:
ls -ltr /old/var/log/packages This is also what it says when I try to chroot from another one, even though the binaries /bin/bash seem identical according to stat and after having copied /bin/bash from a working (same arch and version) to the broken system. Perms and ownership in /bin seem correct. I have no idea what happened, any clue or thing to do to investigate appreciated. EDIT. The broken system gets a kernel panic just after "fast init done". It says "kernel panic: not syncing: no working init found. Try passing init= option to kernel. See linux/Documentation/admin guide/init.rst for guidance". This message occurs when booting a 4.10 kernel as well as sith 4.4.38 (only the link to the doc differ). EDIT 2. Now solved, re-installing the new glibc-solibs with "installpkg --root /rootofbrokensystem glibc-solibs-2.23-x86_64-2_slack14.2". It seems that the "doinst.sh" didn't work as expected. Now I have to investigate what happened, trying the upgrade another system. Maybe there is an issue using spkg instead of installpkg in this specific case? I will report my findings. EDIT 3: I confirm that spkg didn't work as expected. It said Code:
WARNING: Post-installation script failed. (32512) Code:
root[/home/didier]# installpkg -i glibc-solibs-2.23-x86_64-2_slack14.2.txz |
Glad you found the reason why. Also, getting your post off the zero-reply list :)
|
In case you did not see the other thread, here are instructions on how to fix your system if it became unbootable:
https://www.linuxquestions.org/quest...ml#post5731583 |
All times are GMT -5. The time now is 11:32 PM. |