Boot error when Linux Lite not first (default) choice in grub menu in dual-boot

[hughparker1]

Maybe a silly question but isnt it possible to be able to boot into both operating systems without having to do all kinds of things to get it working?

I have also had difficulties getting LL to boot after i installed a second os (Mint, openuse, manjaro). I am also not really an expert on linux, just got the booting fixed by installing grub customizer on the latest installed linux version and fixing the boot problem using that. Now i dont even dare to install a second os anymore because everytime i removed the second os i was unable to boot into LL and had to reinstall all again.

thanks for your comments.   I don't know exactly what happened to LL after installing Xubuntu, but now after re-installing LL it is working great. It seems to me that LL needs to be the last OS in a multi-boot linux setup.   I also have other laptops/computers with multiple operating systems and this is the first time I encountered this problem, but this is the first time I've installed Linux Lite.  I must say my first impressions of LL are very good so far.

I am also not really an expert on linux, just got the booting fixed by installing grub customizer on the latest installed linux version and fixing the boot problem using that.

I have never used grub customizer before, I will check it out.

EDIT:  I just noticed this post... [SOLVED] grub2 and lite3 release
https://www.linuxliteos.com/forums/installing-linux-lite/grub2-and-lite3-release/
I will read it now, it mentions existing linux users should use Grub Customizer or Rescatux, since LL is  targeted at Windows users and as such, the grub config is set for them.

[TMG1961]

Maybe a silly question but isnt it possible to be able to boot into both operating systems without having to do all kinds of things to get it working?

I have also had difficulties getting LL to boot after i installed a second os (Mint, openuse, manjaro). I am also not really an expert on linux, just got the booting fixed by installing grub customizer on the latest installed linux version and fixing the boot problem using that. Now i dont even dare to install a second os anymore because everytime i removed the second os i was unable to boot into LL and had to reinstall all again.

[hughparker1]

Our distro is aimed at Windows users, so our grub is set up in such a way as to easily identify our OS from grub when they dual boot with Windows.

thanks for quick reply, I appreciate your feedback. 

I have just encountered an unexpected error after I ran sudo apt-get update and wondered if this was related to my previous steps above....

Code: [Select]

hugh@DELL-VOSTRO-LINUX-LITE:~$ sudo apt-get update
Hit:1 http://archive.canonical.com xenial InRelease
Hit:2 http://ppa.launchpad.net/nemh/systemback/ubuntu xenial InRelease                               
Hit:3 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu xenial InRelease                       
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease                                     
Hit:5 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu xenial InRelease                               
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial InRelease                                           
Hit:7 http://repo.linuxliteos.com/linuxlite citrine InRelease                                         
Hit:8 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease                                   
Hit:9 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease     
Ign:10 http://linux.dropbox.com/ubuntu wily InRelease                   
Hit:11 http://linux.dropbox.com/ubuntu wily Release
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
hugh@DELL-VOSTRO-LINUX-LITE:~$
so I ran the command suggested...

Code: [Select]

$ sudo dpkg --configure -a

Code: [Select]

hugh@DELL-VOSTRO-LINUX-LITE:~$ sudo dpkg --configure -a
Setting up linux-image-4.4.0-24-generic (4.4.0-24.43) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
Error! Your kernel headers for kernel 4.4.0-24-generic cannot be found.
Please install the linux-headers-4.4.0-24-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
Error! Your kernel headers for kernel 4.4.0-24-generic cannot be found.
Please install the linux-headers-4.4.0-24-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-24-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic
Generating grub configuration file ...
Found background: /boot/grub_linux_lite.png
Found background image: /boot/grub_linux_lite.png
Found linux image: /boot/vmlinuz-4.4.0-24-generic
Found initrd image: /boot/initrd.img-4.4.0-24-generic
Found linux image: /boot/vmlinuz-4.4.0-22-generic
Found initrd image: /boot/initrd.img-4.4.0-22-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 (loader) on /dev/sda1
Found Ubuntu 16.04 LTS (16.04) on /dev/sda6
done
hugh@DELL-VOSTRO-LINUX-LITE:~$
I notice there are errors above but I'm quite new to linux so don't know how to fix, any help would be appreciated.

I ran sudo apt-get update again and it completed ok

Code: [Select]

hugh@DELL-VOSTRO-LINUX-LITE:~$ sudo apt-get update
Hit:1 http://archive.canonical.com xenial InRelease
Hit:2 http://ppa.launchpad.net/nemh/systemback/ubuntu xenial InRelease                                                 
Hit:3 http://security.ubuntu.com/ubuntu xenial-security InRelease                                                     
Hit:4 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu xenial InRelease                                         
Hit:5 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu xenial InRelease                                                 
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial InRelease                                                             
Hit:7 http://repo.linuxliteos.com/linuxlite citrine InRelease                                                         
Hit:8 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease                                     
Hit:9 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease     
Ign:10 http://linux.dropbox.com/ubuntu wily InRelease                   
Hit:11 http://linux.dropbox.com/ubuntu wily Release
Reading package lists... Done                     
hugh@DELL-VOSTRO-LINUX-LITE:~$

then I ran uname -a

Code: [Select]

hugh@DELL-VOSTRO-LINUX-LITE:~$ uname -a
Linux DELL-VOSTRO-LINUX-LITE 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
hugh@DELL-VOSTRO-LINUX-LITE:~$ So looks like I'm still using older kernel.

Not sure how to fix this as I'm still learning linux
EDIT: When I restarted laptop, I couldn't login, just froze after entering password, cursor not moving. So I decided best to re-install as I didn't have any data that was worth keeping. Hopefully it will go better second time round.

[Jerry]

Our distro is aimed at Windows users, so our grub is set up in such a way as to easily identify our OS from grub when they dual boot with Windows.

[hughparker1]

I installed Linux Lite 3.0 successfully on my DELL Inspiron 5559 alongside Windows 10 and it is working great. I noticed the entry in the grub menu looked strange, it had the word *Description: in the menu, it looked like...

*Description:     Linux Lite 3.0 GNU/Linux

But it was working ok so I'm not too bothered about the name as long as it works. I then decided to also install Xubuntu alongside LL3 so I could use both over next few weeks to determine any differences.

Xubuntu is now the default OS in grub menu with an entry for Linux Lite 3.0 beneath as I expected (minus the word *Description: ). Xubuntu is working ok but when I select LL3 I get an error message that says "a filename was expected".

I had a look on google and found this similar incident ....
https://www.linuxliteos.com/forums/installing-linux-lite/dual-booting-ll-2-0-with-other-ubuntu-(14-04)-based-distros/

... where gold_finger suggested

1. Boot computer with live Linux Lite USB

2. Mount the Linux Lite root partition

3. Install grub to the MBR of sda drive

4. Boot computer normally again and Linux Lite should first (default) choice in grub menu, and other OS further down menu.

So I tried this and it worked for me also, so thanks to gold_finger for such an easy solution.

Is there any way to avoid this happening again in the future, or is this the best workaround? It's no big deal, I just wondered if I could avoid the same thing happening again.