Having taken in the relevant advice re: fresh installing - from my previous post - (thanks to everyone who contributed), I decided not to wait for the KDE version to come out and install Mint 17 Cinnamon on my main HDD. I downloaded the ISO, burned it to disk and the MD5 Sum is correct.
Given the mix up I had previously with a slave HDD installed (with Zorin on) - as a precaution - I disconnected the slave and installed Mint 17 to the main HDD, letting Mint use the whole disk (no manual setting of partitions this time). Installation seemed to go ok with the disk ejecting at the end as per normal. However…
On boot I get this error - attempt to read or write outside of disk ‘hd0’. Entering rescue mode…grub rescue> then nothing further.
To test, I shutdown, reconnected the slave and restarted with the installation disk in. I checked with GParted and both HDD’s are seen and show the following -
(this is the HDD set as Master ) /dev/sda1 ext4 147.05GiB 6.10GiB used 140.95GiB unused boot
/dev/sda2 extended 2.00 GiB
/dev/sda5 linux-swap 2.00 Gib 4.00KiB 2.00Gib
I won’t show the slave (sdb1) as I don’t want to boot from it yet anyway. I’m assuming once Mint 17 is running ok, I can update Grub and get the choice of o/s at the start, as per normal?
I then opened Terminal and tried to update Grub but got this - ‘update: command not found’.
Any ideas, please? Have I missed something obvious?
I now want to update/upgrade (if that is necessary) and add a few apps that I use regularly. Before that, I’ll re-connect the slave HDD with Zorin on it. Will Grub automatically recognise the second drive? If not, what is the procedure for updating Grub?
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 980991 489472 83 Linux
/dev/sda2 983038 312580095 155798529 5 Extended
/dev/sda5 983040 304691199 151854080 83 Linux
/dev/sda6 304693248 312580095 3943424 82 Linux swap / Solaris
Disk /dev/sdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x09ae09ad
Device Boot Start End Blocks Id System
/dev/sdb1 63 39078143 19539040+ 83 Linux
/dev/sdb2 39079934 78163967 19542017 5 Extended
/dev/sdb5 * 39079936 73973759 17446912 83 Linux
/dev/sdb6 73975808 78163967 2094080 82 Linux swap / Solaris
I want to configure grub so it opens showing all available kernels. At the mo, I have to hold down the ‘shift’ key to get the menu up and all I get is the 17 installation + it’s related bits and bobs. No sign of sdb at all.
Hadn’t heard of Nemo - I’d been using KDE version for the last year or so, the file manager there is ‘Dolphin’ ;D
output as requested -
richard@richard-Ei-306 ~ $ sudo os-prober
[sudo] password for richard:
No volume groups found
/dev/sdb5:Ubuntu 12.04.4 LTS (12.04):Ubuntu:linux This is Zorin
richard@richard-Ei-306 ~ $ sudo update-grub
Searching for GRUB installation directory … found: /boot/grub
Searching for default file … found: /boot/grub/default
Testing for an existing GRUB menu.lst file … found: /boot/grub/menu.lst
Searching for splash image … none found, skipping …
Found kernel: /vmlinuz-3.13.0-24-generic And this is Mint 17?
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst … done
richard@richard-Ei-306 ~ $
Now that’s interesting… Grub finds Mint 17 (on sda) but not Zorin (on sdb) but os-prober is the opposite?? Am I mis-reading something here or is the output what would be expected?
And why no drive letter for Mint? It’s there on sda - and is what I’m using to post this… weird or what?
Edit: Just did a reboot and Grub still only showing Mint
I can’t say why there are 2 Linux partitions on sdb. I fitted the 2nd Hdd in Mint 13 some time ago and installed Zorin on it. When I was trying out the old Hdd (which messed everything up) I disconnected sdb and hooked the old drive on that cable instead.
When ditching 13 and replacing with 17, I again disconnected sdb (for safety), expecting it to be found once 17 was on and set up. I can easily re-install Zorin on sdb (if needs be) rather than waste everyone’s time - but I think it would be useful to find out why Grub is behaving in this way - if only to increase the knowledge pool?
So from Mint, if you navigate onto the sdb partitions in Nemo, can you identify a /boot folder on one/more of them? Can you post back where you find them, and their contents (might be best to do this from the terminal, or a screenshot)