Chroot into the broken system: # chroot /mnt.Bind mount various virtual filesystems: # for i in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run do sudo mount -B $i /mnt$i done The mount executable supplied with busybox does not support the -B option, use "mount -o bind" in this case.For example, for a system with an EFI partition on /dev/sdb1, an unencrypted /boot partition on /dev/sdb2, and a LUKS-encrypted / partition on /dev/sdb3, do: # cryptsetup luksOpen /dev/sdb3 crypt The exact details of how to do this depend on the particulars of your installation. Mount the broken system somewhere into the running filesystem. If the directory /sys/firmware/efi/efivars is empty, you need to boot the rescue system including the kernel option "efi=runtime" and mount the EFI variables before proceeding: # mount -t efivarfs none /sys/firmware/efi/efivars.(You can verify that the system has booted using UEFI by checking for the existence of the directory /sys/firmware/efi or by running efibootmgr.) (The following procedure is described in greater detail here.)īoot (using UEFI) into a live system, such as a DebianLive CD/USB or the ?Debian installer in rescue mode. Using A Live CD/USB To Fix Your Current System To reinstall grub, you need either a live CD/USB to access your current system, or you can use the rEFInd boot manager on a live CD/USB to boot your current system. Problem2: EFI boot entries disappear after reboot.Problem1: Weak EFI implementation only recognizes the fallback bootloader.Reinstalling grub-efi on your hard drive.Boot your computer with the Refind media.Using A Live CD/USB To Fix Your Current System.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |