Re: "depmod: WARNING" after kmod update

[MaMiMa81 <MaMiMa81@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 3891 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1219615259

Comment:
@TeusLollo 
> > I managed to boot in the system, by repeatedly entering exit & found the other 2 partitions plus swap also mounted the /media/ directory.
> 
> Would you care to post more info? The fact that system `fstab` was ignored, and partitions were mounted into `/media/` as RO in loopback, would point towards `mkinitcpio` initializing your system as if it were a Live Image. Maybe you have `void-mklive` installed? Maybe there's some other hook at work? Weird.
> 
> Anyway, I'm inclined to believe your problem with `mkinitcpio` was more of a mis-configuration case.


Well wasn't going to stray to much away from the core issue - the dracut depmod warning - but regarding `mkinitcpio` your conclusion may well be right.


Since I did the `mkinitcpio` install I have seen this post here:

[https://reddit.com/r/voidlinux/comments/ql2les/void_console_font/hj07qmo/#c](url)

Specifically @ahesford :

> If you want to use mkinitcpio, we ship a kernel hook to generate the initramfs on kernel upgrades. Just xbps-reconfigure -f linux<X.Y> after installing mkinitcpio. Also, to /etc/default/initramfs-regenerate add INITRAMFS_GENERATOR=mkinitcpio so packages that otherwise trigger initramfs regeneration do the right thing.

While I did `xbps-reconfigure -f linux<X.Y>` I didn't add `INITRAMFS_GENERATOR=mkinitcpio` to `/etc/default/initramfs-regenerate` firstly the file didn't exist & I thought the file `/usr/libexec/xbps-triggers/initramfs-regenerate` had it covered - but on re-reading the file it states that it uses `dracut` by default so it looks like it is necessary to specify `INITRAMFS_GENERATOR=mkinitcpio` at `/etc/default/initramfs-regenerate`. I assume this should be done before `xbps-reconfigure -f linux<X.Y>` & perhaps `xbps-reconfigure -fa` wouldn't hurt actually.
So here I may well of not correctly configured `mkinitcpio` & it lead to the issues I experienced. 

> Maybe you have `void-mklive` installed? Maybe there's some other hook at work?

No I don't have `void-mklive`installed & I am unaware of any other hook at work & from when I checked it appeared that `dracut` was completely uninstalled.

Upon booting as I said it flagged up the issue that the `root` partition was only mounted RO & I was dropped into a rescue console with a message that it was unable to carry out `fsck` on the other partitions (I can't remember whether I stated that the `root` partition had been subjected to `fsck`or not - probably not that's maybe why it was mounted RO).
After a bit of research I booted from a Live Image to fsck the partitions on my HDD & they were all OK. But as I have stated I spent a considerable amount of time trying to sort the issue without success so I just re-installed from a backup.
So it's quite possible that what I have stated above was the issue - maybe @ahesford could add some input here as from what I understand he uses `mkinitcpio` on his systems?


@ahesford 

> Problems with Debians test suite for initramfs-tools are of no consequence here.

OK accept that &

> has anybody demonstrated that these warnings actually lead to a problem with the initramfs image? 

No I haven't - but then again I don't know if it is causing issues I haven't noticed or been subjected to? Or will cause issues going forward.
I have have changes to my system now - initially by downgrading `kmod` to v.29_2 (as it is a similar vintage to `dracut v.53_2`) but subsequently re-upgrading `kmod` to v.30 & amending the `/usr/lib/dracut/dracut-init.sh` file as per posts above - so maybe others may wish to comment here whether or not they have experienced problems?

> Somebody is welcome to PR a fix.

Indeed - but for me - please see my first post in this thread.