please pardon that I broke the rules. I use a password manager which which I couldn’t access from the live USB. I’m not writing from my windows partition. I’ll change the password here to something simpler, and later will log in from the live USB into this account.
Shall I also delete the post that I made with the other account (“ghostroger”). This won’t happen again, I promise.
BTW
When booting this time around I noticed that something changed in the screen where I decrypt the harddrive. Before trying the fix today it said “hd0, gpt9” and now it “hd1,gpt9”.
does not matter much to me, as long as I know that I’m talking to the same person
It is, however, easy to recover your password (or set a new one) via the way that @Yochanan mentioned.
Easy.
To address the issue:
we should start by getting a picture of the situation
boot from USB
open a terminal
issue: lsblk -f
post the result
I think it is a fully encrypted system - but we’ll see whether that is actually so.
so:
(this is now to the start of how to chroot into that encrypted system)
boot from the USB again - or maybe you are still there …
and issue sudo cryptsetup open /dev/nvme0n1p9 encryptedroot
(this should prompt you for the password to decrypt that partition - and open it)
also:
the “encryptedroot” is just a word I chose - you can use any word you like. It’s just a name … not important what it is, but some word needs to be there
You can now mount what is referred to as “encryptedroot”
to somewhere - usually to /mnt
sudo mount /dev/mapper/encryptedroot /mnt
and then call “manjaro-chroot”
manjaro-chroot -a
to change root into your encrypted system - and perform whatever repair is needed
The prompt you see should change.
And you are now in your, now decrypted, systems file system
(sans the /home/user data - this is separate and not available as of now - but also not needed)
It would help, at this stage, if you had a terminal file manager installed.
… to move around, look around, and also more easily view and change contents of files
as is probably needed
sudo pacman -S mc
will install that for you
you open it by typing: mc and enter
more easy than to rely on only terminal commands - but that works just as well, of course
needs some getting used to - reminicent of the good old days … but works a treat
I get an error message when trying to manjaro-chroot -a:
rub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> ERROR: No Linux partitions detected!
which means: chroot to whatever is mounted to /mnt and run the bash shell as a shell there
I could not look it up easily (but you could have)
because it is on the live media, but not on an already installed system.
hmm sudo update-grub
once again
(from within chroot)
and then reboot
see what you changed … changed anything
ps:
mounting efi does not actually change anything - no files in that directory are altered
that step is very likely not even needed - it was just a thought of mine
I get this, but not sure if I understand “from within chroot” correctly
sudo update-grub
/usr/bin/grub-probe: error: failed to get canonical path of `overlay'.
and now this:
sudo update-grub
/usr/bin/grub-editenv: error: cannot open `//boot/grub/grubenv.new': No such file or directory.
/usr/bin/grub-mkconfig: line 263: /boot/grub/grub.cfg.new: No such file or directory
)
