My user account doesnt have sudo despite being in sudoers. I cant run new commands i have to execute the binary. Grub takes very long to load with “welcome to grub” message. I just wanted a stable distro as arch broke and currupted my external ssd

  • tal@lemmy.today
    1·
    2 years ago

    Hmm.

    looks further

    Okay. It looks like there’s normally both a /usr/sbin/fsck and an /sbin/fsck, which are hardlinked together, and symlinks in both /usr/sbin and in /sbin/. The default PATH, set in /etc/profile, on Debian searches /usr/sbin first and so will find that (and, in fact, looking at your above message, it was using the /usr/sbin path to fsck, which I just glanced over). I above asked you to list /sbin rather than /usr/sbin; I should have given /usr/sbin.

    $ ls -l /usr/sbin/fsck.ext2 /usr/sbin/e2fsck
-rwxr-xr-x 1 root root 356624 Sep  8 00:47 /usr/sbin/e2fsck
lrwxrwxrwx 1 root root      6 Sep  8 00:47 /usr/sbin/fsck.ext2 -> e2fsck

    If the e2fsck binary in /usr/sbin is missing but the symlink in /usr/sbin is present, fsck will find the symlink, stop searching further in PATH, and then – testing by mangling my system in the same way as I’m guessing yours might be – print the same error you got.

    Can you do the above ls -l /usr/sbin/fsck.ext2 /usr/sbin/e2fsck and see whether possibly the symlink – /usr/sbin/fsck.ext2 – is present in /usr/sbin but the binary – /usr/sbin/e2fsck – is missing? I don’t know how your system would have gotten into that state, but it’d at least produce the error message you’re seeing.