On Thu, Aug 22, 2024 at 11:14 AM Diederik de Haas <didi.deb...@cknow.org> wrote: > > On Thu Aug 22, 2024 at 10:48 AM CEST, Martin Steigerwald wrote: > > Bug#1079273: initramfs-tools: Error with initramfs-tools during apt full- > > upgrade on Debian Sid and reiserfsck > > > > https://bugs.debian.org/1079273 > > > > It is off topic, I know. But as the kmod warning really was helpful to me, > > I thought I just write this mail. This does not seem to be as severe as > > the kmod thing however. > > Rule of thumb: If you see errors during generation of initramfs, do not > reboot but investigate first. If ``ls -lh /boot/initrd*`` does NOT show > anything out of the ordinary (wrt the updated initramfs), then you're > probably fine. > > And in general: if there are problems, it's *very* likely APT warned you > about in advance and/or during execution. > So don't use `-y` and read what APT tells you and then use common sense. > > With the kmod issue, I did see the errors mentioned in the bug > report(s), so I investigated it. > I reported it here given the severity AND it came *together* with KDE > related updates which could (and did) fix previous KDE related issues. > After those updates I wanted to reboot directly. Luckily I didn't > because I choose to first investigate the reported problem. > Given by the messages on #debian-next, that's apparently not something > that everyone does ;-P > > Cheers, > Diederik
initramfs-tools fixed ERRORing dracut-install - that is for me the REAL fix. "mkinitramfs, hook-functions: Exit with error if dracut-install fails" https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/347c5426c035b8de8cc6ede8905b307e98b1df27 The above issue demonstrated the pitfall as a BROKEN (incomplete) initrd.img was generated - surprises with next reboot. My test-cace is a VERBOSE output: KVER="6.10.4-amd64" ; update-initramfs -c -k $KVER -v 2>&1 | tee log_update-initramfs_$KVER.txt TIPP: So, you should always have a 2nd linux-image installed for RESCUE cases. -Sedat-
