[SOLVED] Kernel ==> WARNING

saleem · 2024-11-01 18:41:32

In my system update a few minutes back during the kernel up gradation I noticed a warning line

 Running build hook: [filesystems]
==> WARNING: Possibly missing '/bin/bash' for script: /usr/bin/mount.unionfs

I do not know where this error/warning is coming from and how do I get rid of it/fix it?

Last edited by saleem (2024-11-06 05:04:58)

WorMzy · 2024-11-01 19:09:18

Is your root filesystem running on unionfs?

Mod note: moving to AUR Issues.

saleem · 2024-11-01 19:34:17

WorMzy wrote:

Is your root filesystem running on unionfs?
Mod note: moving to AUR Issues.

Sorry , but I am afraid to understand this question . My root file system in on ext4 ( if this is a correct answer to the question asked above ) and here is my fstab

/dev/sda10         /            ext4      noatime,errors=remount-ro     0      1
/dev/sda5         swap          swap      defaults,noatime              0      0

If any further questions/directions can answer/direct me towards the correct answer to the above question , can you please guide me how to confirm if my oot filesystem running on unionfs or not .

I do have unionfs-fuse 3.5-1 installed on my system but how it can relate to this warning I am not sure , my online search did not give me any clue.

Last edited by saleem (2024-11-01 19:36:09)

seth · 2024-11-01 19:52:49

mount

and post your mkinitcpio.conf

saleem · 2024-11-01 19:58:14

seth wrote:

mount
and post your mkinitcpio.conf

Here is my mkinitcpio.conf

# vim:set ft=sh
MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck plymouth)
COMPRESSION="zstd"

loqs · 2024-11-01 20:12:18

Is the warning only generated for the fallback initrd? Also what is the output of `stat /bin /bin/bash`

https://github.com/rpodgorny/unionfs-fu … unionfs#L1

saleem · 2024-11-01 20:21:12

loqs wrote:

Is the warning only generated for the fallback initrd? Also what is the output of `stat /bin /bin/bash`
https://github.com/rpodgorny/unionfs-fu … unionfs#L1

To the first question , this terminal out put might be of help

(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img
==> Starting build: '6.6.59-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: '6.6.59-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
  -> Running build hook: [filesystems]
==> WARNING: Possibly missing '/bin/bash' for script: /usr/bin/mount.unionfs
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

To the second question here is the output

stat /bin /bin/bash
  File: /bin -> usr/bin
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: 8,10	Inode: 13          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-11-01 16:42:03.088020699 +0500
Modify: 2024-04-07 23:02:30.000000000 +0500
Change: 2024-04-19 09:32:43.472206994 +0500
 Birth: 2024-04-19 09:32:43.472206994 +0500
  File: /bin/bash
  Size: 1117080   	Blocks: 2184       IO Block: 4096   regular file
Device: 8,10	Inode: 523829      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-11-01 22:50:18.000000000 +0500
Modify: 2024-09-25 00:46:06.000000000 +0500
Change: 2024-11-01 22:50:18.400044410 +0500
 Birth: 2024-11-01 22:50:18.396711135 +05

seth · 2024-11-01 20:40:26

loqs wrote:

warning only generated for the fallback initrd

This.

seth wrote:

mount

The output will show whether you're using the unionfs right now at all.

https://github.com/rpodgorny/unionfs-fu … nt.unionfs uses bin/bash as sheband and probably contains some bashisms, but bin/bash isn't added to the initramfs by default.
Since you most likely don't need unionfs at all, you can simply ignore the warning.

saleem · 2024-11-01 20:48:50

seth wrote:

loqs wrote:
warning only generated for the fallback initrd
This.
seth wrote:
mount
The output will show whether you're using the unionfs right now at all.
https://github.com/rpodgorny/unionfs-fu … nt.unionfs uses bin/bash as sheband and probably contains some bashisms, but bin/bash isn't added to the initramfs by default.
Since you most likely don't need unionfs at all, you can simply ignore the warning.

Sorry , I thought you just wanted me to run the command mount and paste the other output , here is what mount shows

 mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=6051620k,nr_inodes=1512905,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
/dev/sda10 on / type ext4 (rw,noatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=39,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=737)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-udev-load-credentials.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/credentials/systemd-tmpfiles-setup-dev-early.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-sysctl.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-sysusers.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-tmpfiles-setup-dev.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-vconsole-setup.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64)
tmpfs on /run/credentials/systemd-tmpfiles-setup.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1212384k,nr_inodes=303096,mode=700,uid=1000,gid=100,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/sda23 on /run/media/saleem/DSK_VOL4 type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=100,iocharset=utf8,uhelper=udisks2)
gvfsd-fuse on /root/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
/dev/sda7 on /run/media/root/End-Openbox type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)

seth · 2024-11-01 21:12:27

The only fuse there is gvfs, you're not using any unionfs - not sure why you have the FS installed, but you can ignore the warning if you don't want to explicitly add bash to the initramfs.

saleem · 2024-11-05 19:20:52

seth wrote:

The only fuse there is gvfs, you're not using any unionfs - not sure why you have the FS installed, but you can ignore the warning if you don't want to explicitly add bash to the initramfs.

I am afraid I don`t get what you mean by " not sure why you have the FS installed,"
I noticed this warning after recent updates , and though I am ignoring it , it appears very annoying on this more than a decade old installation which never spilled out any such error/warning in past.

seth · 2024-11-05 20:36:23

I don't understand why you'd have unionfs installed if you're not even using a unionfs filesystem ("FS")

saleem · 2024-11-06 05:03:55

seth wrote:

I don't understand why you'd have unionfs installed if you're not even using a unionfs filesystem ("FS")

You are right , removing unionfs filesystem resolved
the issue.

Not sure why or when I installed this package

Arch Linux

#1 2024-11-01 18:41:32

[SOLVED] Kernel ==> WARNING

#2 2024-11-01 19:09:18

Re: [SOLVED] Kernel ==> WARNING

#3 2024-11-01 19:34:17

Re: [SOLVED] Kernel ==> WARNING

#4 2024-11-01 19:52:49

Re: [SOLVED] Kernel ==> WARNING

#5 2024-11-01 19:58:14

Re: [SOLVED] Kernel ==> WARNING

#6 2024-11-01 20:12:18

Re: [SOLVED] Kernel ==> WARNING

#7 2024-11-01 20:21:12

Re: [SOLVED] Kernel ==> WARNING

#8 2024-11-01 20:40:26

Re: [SOLVED] Kernel ==> WARNING

#9 2024-11-01 20:48:50

Re: [SOLVED] Kernel ==> WARNING

#10 2024-11-01 21:12:27

Re: [SOLVED] Kernel ==> WARNING

#11 2024-11-05 19:20:52

Re: [SOLVED] Kernel ==> WARNING

#12 2024-11-05 20:36:23

Re: [SOLVED] Kernel ==> WARNING

#13 2024-11-06 05:03:55

Re: [SOLVED] Kernel ==> WARNING

Board footer