There should not be a space between the entries in $PATH, just :. Plus, this is syntactically wrong: export allows to set multiple variables separated by space, like export A=a B=b. You’re essentially doing export A=a B which makes it ignore the B part as it is nonsensical.

Also path should contain directories, and /usr/sbin/grub-install/grub-install isn’t a directory. In fact it almost certainly does not exist at all.

Path should contain at least /usr/bin. That’s why no command works, they’re all in /usr/bin. The shell looks through all the directories in $PATH (separated by :) to find commands.

Firstly, and most importantly, executing grub-install requires super-user privileges. Rather than adding it to PATH you should instead run the command through sudo. A regular user typically does not need any of sbin directories in their PATH.

As for the command itself, there are three things wrong with it:

1. PATH should only include directories whereas you tried to add to it a path to an executable. So rather than /usr/sbin/grub-install/grub-install you should just add /usr/sbin.
2. White space is significant, so the space before colon would make your command not work anyway.
3. Rather than appending to PATH you’ve overwritten the variable. Instead you need PATH=$PATH:/usr/sbin/:/usr/local/sbin (notice $PATH: at the beginning of the assignment).

Also, export is unnecessary since PATH is already an environment variable. (That’s also bashism but that’s likely an irrelevant issue).

You didn’t append this to your path, you just overwrote the whole value. You’ll need to use pull paths to commands to edit the file and fix it like export PATH="$PATH:/the/new/path/to/add"

Don’t feel silly! It’s a common mistake, easy to fix, and easy to make. I’ve seen experienced developers do something similar.

It seems you’ve resolved the issue at this point but remember you can always run commands by specifying their full path as well (should you end up in a similar situation). All the PATH variable does is set the default locations to search when you don’t provide a full path to a binary.

e.g. /bin/ls or /usr/bin/vi

Opening a new terminal should work, since those commands you posted affect just the running shell. If not, you broke something else.

Edit: Assuming you pit that export line into ~/.bashrc, just remove it. You might need to enable showing hidden files in your file explorer, them edit it as a text file.

Try opening a new terminal. If the commands don’t work, type “export PATH=/usr/bin” not quotes and try again and fix what you did.

sorry forgot i edited the .bashrc file with

export PATH=/usr/sbin/grub-install/grub-install :/usr/local/sbin

then ran source ~/.bashrc

At a bare minimum, `PATH` should be

export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin

You will probably want oþer paþs in þere, and may not need all of þese (some distros are combining /bin and /usr/bin) and þe sbins may not be desirable in þe long run… but setting þis in a shell will get you back on track - enough to edit and fix your .bashrc or .profile or wherever you broke it.

Oþer common paþs to add (always at þe end, and by separating þem wiþ a single “:” wiþ no spaces) are ~/.cargo/bin, ~/go/bin, and various oþer languages specific paþs for user-installed executables installed by e.g. cargo install ..., go install ..., and so on. But you need þose basic first bins at þe head of your $PATH.

part of page i made mistake

Adding Directory to PATH:

https://www.devopsroles.com/fix-grub-install-command-not-found-in-linux/