Your suggested message presupposes that busybox is used on a particular distribution. That's not necessarily the case. Remember, e2fsprogs is designed for all distributions, not just for Ubuntu. If Canonical wants to make a change like that to e2fsprogs, all distributions are free to make any changes they want to a package. (At which point they own any liability if the user is clueless enough that they need that amount of hand holding, but if that information is just enough to cause them to attempt to do a file system fixup, but they then lose files because they fumble the job, that's on Ubuntu, not on me.)
Or perhaps Canonical could put a multiple page, or even a book-length tutorial in its initramfs scripts that tries to teach all eventualities of what a user might need to fix when they run e2fsck by hand, if fsck exits with an error code indicating that the file system needs to be fixed by hand. Again, feel free to convince canonical to do something like that if it's really needed by novice users. Personally, I think it's roughly equivalent to trying to teach medicine to a novice as opposed to telling them to see a doctor, but hey, Ubuntu can try to break ground by trying to lead users by the hand. I do predict that after you tell users to "hit fsck /dev/xxxxxx", what will happen next is users will go to forum.ubuntu-fr.org and ask, how do I answer this question? I'm so confused.... Where does this end? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/XXXXXXXX requires a manual fsck" become "execute this command 'fsck -y /dev/xxxxxx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
