On 20-08-18 21:24, Héctor González wrote: > Hello, > > The latest kernel update has this weirdness while booting: > > Begin: Loading essential drivers ... done. > Begin: Running /scripts/init-premount ... done. > Begin: Mounting root file system ... Begin: Running /scripts/local-top > ... done. > Begin: Running /scripts/local-premount ... [ 2.858611] PM: Starting > manual resume from disk > done. > Begin: Will now check root file system ... fsck from util-linux 2.29.2 > [/sbin/fsck.ext4 (1) -- /dev/xvda2] fsck.ext4 -a -C0 /dev/xvda2 > fsck.ext4: symbol lookup error: /lib/x86_64-linux-gnu/libext2fs.so.2: > undefined symbol: com_err > fsck exited with status code 127 > done. > Failure: File system check of the root filesystem failed > The root filesystem on /dev/xvda2 requires a manual fsck > (initramfs) [ 266.336115] random: crng init done > > > Returning to the previous kernel boots normally. I tried > "update-intramfs -k all -u", but it doesn´t make any difference, does > anyone know where this "com_err" symbol should be defined, or how to > workaround this issue? > > Thanks. > Cacho.
A search with Google shows a Deb**n package com_err a library for common error messages. Which depends on https://packages.debian.org/wheezy/libcomerr2 so maybe installing this lib solves your problem. Grtz. Nick
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
