On 12/12/2020 03:40 PM, Neil Bothwick wrote: > On Fri, 11 Dec 2020 14:36:51 -0700, the...@sys-concept.com wrote: > >> I wipe the /boot, reinstall kernel, initframes, grub. >> The system boots, I can login as root but X is not running, >> the command is displaying: "(none) /#" >> >> When I try to start the network I get: >> fsck.fat 4.1 (2017-01-24) open: no such file or directory >> Filesystems couldn't be fixed >> ERROR: fsck failed to start >> >> It seems to me "/" file system mount in "read only" mode. >> When I try to emerge anything I get: /var/log/emerge.log Read-only file >> system. > > Have you actually booted fully? This looks like the situation when > mounting root fails and the initramfs drops you to a console? Does mount > show that you partitions from fstab have mounted?
A lot of folks get hurt over this bug, I'm supersized that nobody reported it yet that fsck.fat 4.1 has bugs. Symptoms: One day you end up with command line login: (none) login: Your root file system will be mounted as RO and only way to access your system is to boot-strap it. Recompiling anything (emerge -e system) will not help. The screen output fly by so fast that you need to have a high speed camera to catch the scrolling line. What help me is in "/" running: touch forcefsck It will force the system to run a check on all file systems in fstab. This will slow down the system, so you will notice that error message: fsck.fat 4.1 (2017-01-24) open: no such file or directory There is a similar related bug filed about it (but I don't know why is it marked resolved) https://bugs.gentoo.org/306119 SOLUTION (workaround): if you have UEFI system most likely your "boot" partition is some form of "vfat" if you have in fstab: LABEL=boot /boot vfat noauto,noatime 1 2 Change it to: LABEL=boot /boot vfat noauto,noatime 0 0 The force check of vfat system will skip and your system will boot normally. My permanent solution will be to go back to old reliable "ext2 as boot". Most newer BIOS system have CSM (compatibility support module under Boot menu) turning it ON will allow the boot partition to be in "ext2", it will avoid future problems with "fsck.fat" Running "boot" in ext2 I don't need "initramfs" either.
