Remove 2.8 and dual boot 3.4 with Ubuntu

[phil66]

Code:

Ray-Kudu-Pro:~$ sudo os-prober
[sudo] password for ray:
/dev/sda3:Linux Lite 3.4 (16.04):Ubuntu:linux
Ray-Kudu-Pro:~$ cat /boot/grub/grub.cfg | grep "menuentry '"
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-83-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-83-generic-advanced-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-83-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-83-generic-init-upstart-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-83-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-83-generic-recovery-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-81-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-81-generic-advanced-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-81-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-81-generic-init-upstart-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-81-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-81-generic-recovery-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-79-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-79-generic-advanced-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-79-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-79-generic-init-upstart-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-79-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-79-generic-recovery-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-78-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-78-generic-advanced-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-78-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-78-generic-init-upstart-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
    menuentry 'Ubuntu, with Linux 4.4.0-78-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-78-generic-recovery-5dbc3e00-edb2-4b6c-a2b8-bc024e5000e1' {
menuentry 'Memory test (memtest86+)' {
menuentry 'Memory test (memtest86+, serial console 115200)' {
menuentry 'Linux Lite 2.8 (14.04) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-2c94c91e-503b-40c8-99a1-7fbf06d54273' {

[phil66]

Code:

Ray-Kudu-Pro:~$ sudo mount /dev/sda3 /mnt
[sudo] password for ray:
Ray-Kudu-Pro:~$ cat /mnt/etc/issue
Linux Lite 3.4 LTS \n \l
Ray-Kudu-Pro:~$ sudo umount /dev/sda3
Ray-Kudu-Pro:~$
Ray-Kudu-Pro:~$ sudo update-grub
[sudo] password for ray:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-83-generic
Found initrd image: /boot/initrd.img-4.4.0-83-generic
Found linux image: /boot/vmlinuz-4.4.0-81-generic
Found initrd image: /boot/initrd.img-4.4.0-81-generic
Found linux image: /boot/vmlinuz-4.4.0-79-generic
Found initrd image: /boot/initrd.img-4.4.0-79-generic
Found linux image: /boot/vmlinuz-4.4.0-78-generic
Found initrd image: /boot/initrd.img-4.4.0-78-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done

[gold_finger]

Output confirms LL3.4 installed, os-prober command sees it, but update-grub command does not.  Ubuntu's grub.cfg file still has old LL2.8 entry.


If memory serves me, LL2.8 is a version that did not play well with others if its grub was not the one in control of booting.  (I believe that is no longer the case with newer versions of LL.)  So my best guess is that you must have had to manually do something special in Ubuntu to make an entry that would boot LL2.8 and to de-activate the os-prober script from running when performing an update to grub (eg. for new Ubuntu kernels) so that grub updates would not break ability to boot LL2.8.


Boot into Ubuntu and post back with output from this command please:

Code:

ls -la /etc/grub.d

[phil66]

ray[member=5018]Ray[/member]-Kudu-Pro:~$ ls -la /etc/grub.d
total 96
drwxr-xr-x  2 root root  4096 Jun 16 20:53 .
drwxr-xr-x 146 root root 12288 Jul  1 09:29 ..
-rwxr-xr-x  1 root root  9791 Dec 19  2015 00_header
-rwxr-xr-x  1 root root  6258 Mar 15  2016 05_debian_theme
-rwxr-xr-x  1 root root 12512 Mar  1 14:52 10_linux
-rwxr-xr-x  1 root root 11082 Jun 17  2016 20_linux_xen
-rwxr-xr-x  1 root root  1992 Mar 12  2014 20_memtest86+
-rw-r--r--  1 root root 11692 Apr 11  2014 30_os-prober
-rwxr-xr-x  1 root root  1418 Jun 17  2016 30_uefi-firmware
-rwxr-xr-x  1 root root  905 Mar  5 20:09 40_custom
-rwxr-xr-x  1 root root  216 Apr 11  2014 41_custom
-rw-r--r--  1 root root  483 Apr 11  2014 README
ray[member=5018]Ray[/member]-Kudu-Pro:~$

[gold_finger]

As suspected, the os-prober script has been de-activated in Ubuntu so it doesn't run when doing an update to grub, therefore doesn't add entry for new LL3.4.  You'll need to re-activate it by running this command from a terminal in Ubuntu:

Code:

sudo chmod 755 /etc/grub.d/30_os-prober

Now run command to update grub:

Code:

sudo update-grub

Reboot and you should see an entry for LL3.4 and be able to boot into it.


In all likelihood you'll still see an old (non-working) entry for LL2.8 as one of the choices.  I suspect that 40_custom script in Ubuntu's /etc/grub.d folder may have been used for that.  Post back output of this command from a terminal in Ubuntu:

Code:

cat /etc/grub.d/40_custom

[phil66]

ray[member=5018]Ray[/member]-Kudu-Pro:~$ sudo cat /etc/grub.d/40_custom
[sudo] password for ray:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Linux Lite 2.8 (14.04) (on /dev/sda3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-2c94c91e-503b-40c8-99a1-7fbf06d54273' {
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos3'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  2c94c91e-503b-40c8-99a1-7fbf06d54273
    else
      search --no-floppy --fs-uuid --set=root 2c94c91e-503b-40c8-99a1-7fbf06d54273
    fi
    linux /boot/vmlinuz-3.13.0-24-generic root=UUID=2c94c91e-503b-40c8-99a1-7fbf06d54273 ro quiet splash $vt_handoff --
    initrd /boot/initrd.img-3.13.0-24-generic
}
ray[member=5018]Ray[/member]-Kudu-Pro:~$

[gold_finger]

You didn't say, but I'm assuming you ran the chmod command on os-prober script and can now boot into LL3.4.  Correct?


Now you just need to get rid of old entry for LL2.8.  To do that you'll need to open the 40_custom script with a text editor as root/admin and delete the custom menu entry.  I don't know what text editor you have on Ubuntu, but I think it might be gedit.  So, I'll use gedit in commands below.  If that's not the text editor you have on Ubuntu, substitute the correct one in place of gedit in the command.  (If you're not sure, just open the text editor and go to Help->About and it should say what name of editor is.)


To open the file as root in the text editor use this command in a terminal:

Code:

gksu gedit /etc/grub.d/40_custom

In the opened file, delete everything after the line:  # the 'exec tail' line above.  You should then only have this in the file:

Code:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.

Save the file, then close the text editor.


Back in the terminal, now update grub one more time.

Code:

sudo update-grub

Now you should only have Ubuntu and LL3.4 choices for booting in grub menu and Ubuntu will be first (default) choice.

[phil66]

All three items returned positive comment as you stated.
I booted ll-3.4 and now was getting to update and use synaptic
But I no longer have a valid password
Looked in help session and found a program for resetting password
This program written by Jerry for ll-3.0
Can i use to reset the password in ll3.4

[gold_finger]

I'm not familiar with program you mentioned for resetting password.  You can try to use it and if it works, great.  Otherwise, you can follow this tutorial to reset your password.  Tutorial is for Mint, but will work same way in LL.
Reset lost/forgotten/non-working Password


P.s.
Before trying to reset password, double-check that you didn't accidentally enable the <CapsLock> key before you tried entering password.  Passwords are case-sensitive, so that would cause it to fail if you accidentally hit it.

[phil66]

Tried both reset password programs..The only difference is one spells passwd and the other spells password
Using passwd both units entering password twice and confirming password was completed
In the ll3.4 when opening with e and erasing ro splash quiet $ vt-handoff and adding rw init=/bin/bash
after unable to use password went back to where I made the change and ro splash quiet $ vt-handoff was in the edit of ll3.4