0 Members and 1 Guest are viewing this topic.
During your anniversary Windows 10 update did you miss any restarts, accidentally have the system boot LL instead of Windows 10?
You mention you have Debian on the disk. Can you boot the Debian system? Grub can be repaired and edited from Debian, and you can also mount the LL volume and make changes.
To avoid this quirk in the future the boot order should have Windows 10 last, and Debian first, and Debian should also be the first system on the disk.
....and Debian first, and Debian should also be the first system on the disk.
Otherwise try a Rescatux live cd to restore grub for Linux Lite. Easy to use GUI. No terminal work.
Hi Hughparker1,Yes, I've had this problem sometimes with a either Windows / LL dual boot or a Linux only dual or multiple boot setup, on an MBR disk.Like you LL sometimes needed to be 'reset' so that it was again 'in charge' of the grub list, though unlike you I didn't have the 'Welcome to emergency mode' message.Like you I ran the first two lines of code you have shown, but left out the 'umount' line, and that seemed to work. Maybe Hugh try again, but without unmounting /dev/sda8. Maybe worth a try...CheersMike
$ sudo nano /media/linux/LINUX-LITE/etc/default/grub
GRUB_DEFAULT=4#GRUB_HIDDEN_TIMEOUT=0GRUB_HIDDEN_TIMEOUT_QUIET=trueGRUB_TIMEOUT=10GRUB_DISTRIBUTOR=`lsb_release -d 2> /dev/null || echo Debian`GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"GRUB_CMDLINE_LINUX=""
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs. "Systemctl reboot" to reboot, "systemctl default or D to try again to boot into default mode.Give root password for maintenance(or press Control-D to continue):
$ sudo mount /dev/sda8 /mnt # Mount the LL root partition on the HDD to the live environment$ sudo grub-install --boot-directory=/mnt/boot /dev/sda # Install grub to the MBR of sda drive$ sudo umount /dev/sda8