On 25/03/2025 02:40, J wrote:
user@debian:~$ sudo for i in /dev /dev/pts /proc /sys /sys/firmware/efi/
efivars /run; do mount -B $i /mnt/$i; done
Notice that the page suggests "# for i in /dev /dev/pts /proc "
so it is assumed that users should run
$ sudo -i
# # more commands given above...
# for i in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run; do
mount -B $i /mnt/$i; done
user@debian:~$ sudo bash bash.sh
mount: /mnt//dev: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
The error suggests that you forgot to mount the root partition to /mnt.
This case you will get the same error with your variant of commands:
On 21/03/2025 20:38, J wrote:
*I had to use*
sudo mount --bind /dev /mnt/dev
sudo mount --bind /dev/pts /mnt/dev/pts
So your suggestion is still not clear to me.
https://wiki.debian.org/GrubEFIReinstall#Using_the_rEFInd_rescue_media
In the context of bind-mounts the link is confusing. In some cases
rEFInd should be able to boot *installed* Linux in the case of troubles
system firmware, e.g. missed boot entry. No chroot is required for grub
reinstall. However you wrote that you removed kernel, so rEFInd had no
chance to boot anything.
