So to be or not to be in chroot is a difficult question.
The only idea of what issuing commands from within chroot might be is to rightclick in the mnt folder where the partition is mounted in issuing update-grub.
You manjaro-chroot
The prompt changes.
You can now see your files - and examine/change them.
You can’t do that if you are not in chroot.
… I’m thinking - but right now I can’t come up with a better explanation …
that console file manager I mentioned (mc) … can really help you
You don’t have it in the live system.
If you are in chroot, and install it, you’ll have it.
But only there - not in the live system (when not in chroot)
That is, thus, also an indication on where you are … chroot or not.
I think I can confirm that while in chroot suod update grub results in the second message that freaked you out.
Thanks for all you help. I really appreciate it. I think to ask more of you would not be appropriate. Probably it needs a break till I can try once more.
But better would be to remember what you did to /etc/mkinitcpio.conf
and /etc/default/grub
and revert the changes
or possibly just post the contents of those files here
for others to have a look
anyway:
in the future, make it a habit to make a copy of the file you are going to edit
so you have something to go back to - by simply replacing the edited file with the copy of the original
As I said earlier I didn’t change /etc/default/grub and in /etc/mkinitcpio.config I only erased two words from this line – plymouth and plymouth-encrypt :
Actually typed that but must have erased it again:
“plymouth” and “plymouth-encrypt”
Meanwhile I changed it back, ran sudo mkinitcpio -P (which has some warnings in it), but update-grup doesn’t work. – The error message for update-grub says a folder and a file aren’t there. Isn’t this akward, too? Because in the live USB folders there is a grub folder in /boot and the file “grubenv”.
(All for a little cosmetic correction of the boot screen.)
But for tonight I think this is enough. If I could give you a badge (for this forum), I would!
And reading this, I deleted plymouth as well, I think it was something that bogdan supposed to do, to get rid of the misaligned splash screen. Hence the supposed removal of the two words including plymouth.
/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
And I think I was. But thank you very I don’t want to ask any more of you. I’m just not capable enough to solve it right now. And you already did so much!
First I had the idea of trying to reinstall grub in chroot, because of the missing files and folders. Just a guess. This brought me to reinstalling pymouth in chroot which, as I said I removed before the errors began. Then mkinitcpio -P and upgrade-grub worked (better, as there still were warnings or missing stuff). But finally I could restart my manjaro. However with the misaligned splashscreen…