Need help with Linux Lite boot issue please

[N4RPS]

Hello!

Cheers Firenice, no problem with the live-DVD (have that already) but would be nice to get some instructions on how to use it to repair LL though.  Any pointers?

You asked, so...

Boot into LL LiveCD/USB and type the following into a terminal window [CTRL-ALT-T]:

Code: [Select]

sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
After many uses, it's never failed ME yet. Using the UEFI Ubuntu flavor of your choice instead can repair UEFI boot issues...

73 DE N4RPS
Rob

[aviceda]

OK, many thanks to all who have helped today, much appreciated!

....have sort of sorted-out my Grub issues, but still think an optional default location would be better than the current one. I have another installation question regarding dual-monitors but will start another thread.

Tom

[aviceda]

Thx gold_finger,

Just followed your advice but it 'fell-over' here, and I haven't got a clue what it means 

linux@linux:~$ sudo grub-install --boot-directory=/mnt/boot /dev/sdc
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/cow'.

Tom

[firenice03]

Sorry I was accessing from phone earlier...
Here's a LL link..
https://www.linuxliteos.com/forums/installing-linux-lite/help!!!!-deleted-grub-by-mistake/msg14247/#msg14247

[aviceda]

Thanks truckerjay, the ubuntu advice didn't work for me, I get the following output (in red)when I try to apply the text in italics below.

linux@linux:~$ sudo mount /dev/sdc /mnt
mount: /dev/sdc already mounted or /mnt busy

linux@linux:~$ sudo mount --bind /dev /mnt/dev &&
> sudo mount --bind /dev/pts /mnt/dev/pts &&
> sudo mount --bind /proc /mnt/proc &&
> sudo mount --bind /sys /mnt/sys
mount: mount point /mnt/dev does not exist
linux@linux:~$


Mount the partition your Ubuntu Installation is on. If you are not sure which it is, launch GParted (included in the Live CD) and find out. It is usually a EXT4 Partition. Replace the XY with the drive letter, and partition number, for example: sudo mount /dev/sda1 /mnt.
sudo mount /dev/sdXY /mnt

Now bind the directories that grub needs access to to detect other operating systems, like so.
sudo mount --bind /dev /mnt/dev &&
sudo mount --bind /dev/pts /mnt/dev/pts &&
sudo mount --bind /proc /mnt/proc &&
sudo mount --bind /sys /mnt/sys

Now we jump into that using chroot.

[truckerjay]

http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd  this explains how to use live media to repair or reinstall grub.

[aviceda]

Thanks AVJ, appreciate the advice,  I am currently attempting to repair Grub using the live-DVD but am a bit concerned about ownerships (root, chown etc) Just wonder if you are aware of any previous useful advice available out there? (....will do some 'searches'  )

[avj]

The best place to look while waiting for someone to answer would be the help manual under "Installation Issues":

https://www.linuxliteos.com/manual/hardware.html#installissues

If you scroll past the first section you will see this:

"Dual Boot Install on Systems with More Than One Hard Drive?
When choosing to install Linux Lite alongside Windows on a computerwith more than one hard drive, the default action of the installer is to install the Linux boot loader to the MBR of the first hard drive. Since Windows is likely installed to the first drive, its boot loader will be replaced on the MBR with the Linux boot loader. The Linux boot loader will see the Windows installation and add it to the boot menu on start-up. This is how most people do the installation.
However, some people prefer to keep the Windows boot loader intact on its own drive and install the Linux boot loader to its own drive. (There are various reasons for doing that, the most common being that it makes booting Windows easier if they decide to remove the Linux installation.) After the installation completes, they then set the computer's BIOS to boot from the Linux drive. Even though the Linux boot loader is installed to a separate drive, it will see the Windows installation and add a boot choice for it. By booting from the Linux drive, you get the choice to boot either OS. If you later remove Linux, simply reset the BIOS to boot from the Windows drive and it will boot Windows as it did before your installation of Linux.
To accomplish this, you must choose the "Something else" option from the "Installation Type" screen during installation. On the following screen you will set-up your partitions and mount points manually. Then, near the bottom of the window, you need to set the "location for boot loader installation" to the MBR of the drive containing Linux Lite. For example, if you had two hard drives - /dev/sda (Windows) and /dev/sdb (Linux) - you would set the location to /dev/sdb (without any partition number at the end)."

[truckerjay]

I am dual boot I did the sudo update grub from the system I could boot into.  I normally have at times 4 different linux systems on hard drive.  Currently dual boot LL 2.6 and 2.8 beta.

[aviceda]

Cheers Firenice, no problem with the live-DVD (have that already) but would be nice to get some instructions on how to use it to repair LL though.  Any pointers?

[firenice03]

With what boot repair did you may need to do bit more..
But the sudo update grub as described above by gold-finger would need to be done with a LL live USB... It'll be the only option to get into LL... With grub repair writing to all boot disk may need additional configuration.

Not saying anything bad has occurred, I'm not familiar with repair, still new myself 

[aviceda]

Thx Truckerjay, I would if I could boot into LL 

[aviceda]

Don't believe that UEFI is involved (certainly haven't noticed it on previous distro installations) and it was the last distro (should be on sdc4). Boot-Repair inserted same config in all sda, sdb, sdc (I believe  )

This is part of the last 'Boot-Repair' report, have only posted the first bit but can send more if required.

============================= Boot Info Summary:

 => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    for /boot/grub and uses an embedded config file:
   
    ---------------------------------------------------------------------------
    search.fs_uuid b0523ff6-ecce-442d-83dc-c195540f410a root hd2,msdos2
    set prefix=($root)'/boot/grub'
   
    ---------------------------------------------------------------------------
 => Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    for /boot/grub and uses an embedded config file:
   
    ---------------------------------------------------------------------------
    search.fs_uuid b0523ff6-ecce-442d-83dc-c195540f410a root hd2,msdos2
    set prefix=($root)'/boot/grub'
   
    ---------------------------------------------------------------------------
 => Grub2 (v2.00) is installed in the MBR of /dev/sdc and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    for (,msdos2)/boot/grub.

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /bootmgr /Boot/BCD

sda2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 7/2008: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 7
    Boot files:        /bootmgr /Boot/BCD /Windows/System32/winload.exe

sdb1: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info:
    Mounting failed:   mount: unknown filesystem type ''

sdb2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  Debian GNU/Linux 8
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sdb3: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info:
    Mounting failed:   mount: unknown filesystem type ''
mount: unknown filesystem type ''

sdb4: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  elementary OS Freya
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sdc1: __________________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info:
    Mounting failed:   mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''

sdc2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of
                       sdc2 and looks at sector 3004160720 of the same hard
                       drive for core.img, but core.img can not be found at
                       this location.
    Operating System:  Linux Mint 17.3 Rosa
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sdc3: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:

sdc4: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  Linux Lite 2.6 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

[truckerjay]

Have you tried opening a terminal and putting in sudo update-grub ?  Worked for me.  If not there are other ways but a little more complicated.  After doing the update reboot.  Should come up with screen listing the different operating systems.

[firenice03]

A few questions, it'll help the gurus 
Is this an UEFI install (if you installed without additional configuration it was probably legacy)?
What order of distro installs, was LL last or most recent? If not grub may need updated.