From d848e5d0577fc6b715c8b4431c3f5e9bbcfa1718 Mon Sep 17 00:00:00 2001 From: Leandro Noferini Date: Wed, 23 Jun 2021 09:28:28 +0200 Subject: [PATCH] Can't understand "miunt" (#1707) * Can't understand "miunt" line 123, I can't understand "miunt" word: perhaps would be "mount"? * Fix typo in noaccess.md Co-authored-by: tituspijean --- .../01.administrate/08.troubleshooting/03.noaccess/noaccess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md b/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md index e39a3177..d5f145db 100644 --- a/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md +++ b/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md @@ -120,7 +120,7 @@ If you are in "rescue" mode with `grub`, it may be due a misconfiguration of `gr In that case, access the storage drive from another system (your provider's "rescue" mode, live USB drive, read the SD or drive on another computer) and try to check partitions integrity with `smartctl`, `fsck`, and `mount`. -If disks are corrupted or hard to miunt, you have to save your data and maybe reformat, reinstall, and/or change the drive. If you succeed in mounting the drive, you can use `systemd-nspawn` to access its database. +If disks are corrupted or hard to mount, you have to save your data and maybe reformat, reinstall, and/or change the drive. If you succeed in mounting the drive, you can use `systemd-nspawn` to access its database. Otherwise, run `grub-update`, `grub-install` again with `chroot` or with `systemd-nspawn`.