Skip to main content ↑ ↓
Topic: lacking libicu-symlink killing the system (Read 159 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

lacking libicu-symlink killing the system

Just a heads-up: After updating the system yesterday, it was utterly unbootable.
When passing GRUB, I got a bluescreen-esque error telling me vfs: unable to mount root fs on unknown-block(0,0).

I originally thought it was a grub issue, since that had been updated, but the update was running in the background - so (as usual) I missed both that and the fast-passing log message telling me to grub-install/update-grub.

However, reinstalling/updating grub did nothing.

Ultimately, it turned out that libicu was updated, but apparently was too slow to write its symlink or something, causing.libicuuc.so.76: cannot open shared object file: No such file or directory.

This proved to be fatal, because libicuuc.so.76 is used by bsdtar, which is used in the process of generating initramfs.

In other words: libicu screwed up its symlink, so I didn't get a bootable ramdisk.

Since the symlink does exist now, the problem was solved by booting from live Artix, artix-chrooting into the system and reinstalling linux, linux-headers and linux-firmware, triggering the initramfs-generation to rerun.
After that, booting worked as normal.


Unrelated: If your Chrome doesn't work after the update, complaining error while loading shared libraries: libLLVM.so.18.1: cannot open shared object file, you have to install llvm18-libs for the older version.

Yes - I had a lot of fun with missing libraries the past 24 hours.