I recently did an update on system and baselayout (1.11.13-r1) as well as e2fsprogs (1.38) was updated to the most stable versions. I ran the env-update and after restarting got an error: fsck: invalid option -- A and it asked me for the admin password. Using a usb keyboard I was unable to do anything further. After messing with this for a few hours, I found I could delete checkfs off a boot disk, the system boots up but with a ton of warnings. It appears as if some options may have been removed from fsck (And to add to the happiness, the e2fsprogs doesn't seem to create a symlink from fsck to e2fsck either) I don't see any change to this in any of the newer baselayout(s) or any idea for a better solution without editing these myself. I didn't boot some drives in over a year, which might have caused some of these things to occur. Reproducible: Always Steps to Reproduce: 1. emerge e2fsprogs baselayout 2. reboot and have checkfs need to run 3.
fsck and e2fsck are not the samething fsck supports the -A option unconditionally post `emerge info` like the bug report page told you to, and run: emerge e2fsprogs >& log then post the log file as an attachment
Upon further investigation, the problem seems to lie with the build of e2fsprogs or my system configuration. I only saw the problem with baselayout as this is where it hangs. When I 'emerge e2fsprogs' and get version 1.38 it configures it with this command: ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man -- infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc -- localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu -- bindir=/bin --sbindir=/sbin --enable-elf-shlibs --with-ldopts= --enable-dynamic- e2fsck --without-included-gettext --enable-nls --disable-fsck Resulting in 'Not building fsck wrapper' (because of the passing of the -- disable-fsck option. If I attempt to build off e2fsprogs-1.37.ebuild it configures it with the following and it works fine and builds a workable fsck. ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man -- infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc -- localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu -- bindir=/bin --sbindir=/sbin --enable-elf-shlibs --with-ldopts= --enable-dynamic- e2fsck --without-included-gettext --enable-nls It *appears* to be getting set be this line in the e2fsprogs-1.38.ebuild $(use_enable userland_GNU fsck) Anyway, I have no idea how to resolve this to move from e2fsprogs 1.37 to 1.38. Thanks for the response, though it really didn't concern this package.
Created attachment 69947 [details] Emerge info
bug in your portage, USERLAND isnt being set to GNU like it should be
*** This bug has been marked as a duplicate of 105304 ***
