05-02-2015, 07:25 PM
Thanks goldfinger. I have to say something very strange has just happened, following everything going so smoothly.
I removed the sda/sdb drives for the setup where LL was only bound to sdb's /mnt/DATA (ext4 formatted). It was working very well in UEFI as I mentioned in previous post. I replaced this with the sda/sdb drives for the setup where sdb's /mnt/DATA was ntfs formatted. They were then changed around a second time and now neither setup boots to the grub screen. How is it possible that when I remove the drives and put them back, after using drives for another setup, that the grub screen doesn't show on booting? Most peculiar ...
In order to supply you with the information you asked for in the last post I need to obviously reinstall grub and then hopefully boot into LL. I know how to do this with MBR (you showed me previously) , but is this different for GPT with the EFI setup? The instructions for MBR that you gave me previously were as follows, where X is the partition number for LL's root partition:
sudo mount /dev sdaX /mnt
sudo grub-install --boot-directory=/mnt/boot /dev/sda
sudo umount /dev/sdaX
then sudo-update-grub on reboot.
Shall I run this on my setup?
Regards
Mike
I removed the sda/sdb drives for the setup where LL was only bound to sdb's /mnt/DATA (ext4 formatted). It was working very well in UEFI as I mentioned in previous post. I replaced this with the sda/sdb drives for the setup where sdb's /mnt/DATA was ntfs formatted. They were then changed around a second time and now neither setup boots to the grub screen. How is it possible that when I remove the drives and put them back, after using drives for another setup, that the grub screen doesn't show on booting? Most peculiar ...
In order to supply you with the information you asked for in the last post I need to obviously reinstall grub and then hopefully boot into LL. I know how to do this with MBR (you showed me previously) , but is this different for GPT with the EFI setup? The instructions for MBR that you gave me previously were as follows, where X is the partition number for LL's root partition:
sudo mount /dev sdaX /mnt
sudo grub-install --boot-directory=/mnt/boot /dev/sda
sudo umount /dev/sdaX
then sudo-update-grub on reboot.
Shall I run this on my setup?
Regards
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work