Glibc Update to the glibc-2.26-6-omv2015.0.x86_64.rpm

Other
1

I had the same problem today. As is in the https://forum3.openmandriva.org/t/glibc-update/1410 link.

I did update to the http://ftp-stud.hs-esslingen.de/pub/Mirrors/openmandriva/3.0/repository/x86_64/main/updates/glibc-2.26-6-omv2015.0.x86_64.rpm glibc version.
Fortunately, I could repair it in the dual-boot by the https://www.paragon-software.com/home/extfs-windows-pro/index.html?utm_source=top-banner&utm_medium=ext-win-free-page&utm_campaign=extfs-win-free program in Windows 7.

1 Like
2

Great you have managed this way.

There ofcourse is other way to do it.

  1. You need to boot live system from usb or boot from dracut to command line (rescue mode)
  2. Chroot into a broken system
  3. Edit /etc/nsswitch.conf
  4. Add “files” as a first option to passwd and group
  5. Save your changes
  6. Umount your disk
  7. Boot your system normally
2 Likes
3

If you can’t reach the command line in rescue mode you may use the emergency shell by adding rd.break (as @Colin said to me ) as boot parameter at the end of kernel command. In the shell the root partition is mounted automatically into /sysroot directory so the file to change in this case is is /sysroot/etc/nsswitch.conf.

1 Like
4

And I still have had no problems at all with the former and the current update of glibc in one of my two computers…Would like to know why this particular laptop has shown no problem to boot. This makes me think that the root of the problem is not properly identified…