If by chance Boot Repair doesn't work, as long as the /home partition is separate, there's a way to perform a 'fresh upgrade', creating & formatting the existing root partition, and marking /home & Swap as these are, yet do not place a check in the Format box of /home. Just choose it as ext4 (or whatever it currently is) & select /home from the dropdown list, same with Swap if installed & reinstall the OS. As long as you've followed instruction, you have a new OS. I once 'fresh upgraded in this manner from Mint 12 (maybe 11) to 17.1, though when adding a new data /Linux /home drive, saved all of my folders inside of /home to an external & installed the entire OS clean. The OS was much faster, and before wiping the former drive, searched it's contents, there were over 2GiB of useless junk, 4 OS's before MInt 17. Back to your situation.
This gives you a fresh OS, and your documents in /home are saved. All you'll need to do is update the OS & you'll be ready to go. One thing you may notice, is that if you've chosen custom wallpapers, these may still be there. So a fresh upgrade is the way to go when all else fails. That's also why it's a bad idea to have root only w/out a /home partition. Preferably on an entirely different drive, that way, should the drive with the root partition goes, you've lost nothing. I always run root on a SSD, and /home & swap on a HDD. One wouldn't know if a VM is created that it's on a HDD, if a Windows install, will surpass the 5.9 WEI mark & run much faster than a new $500-600 computer out of the box, on a HDD. Only the VMware client is running on the SSD, the virtual OS folder & drive is within the /home folder on a HDD.
Backups are also important, while I once supported Timeshift, my recent success at cloning with Macrium Reflect to another SSD has shown me there's other tools to use. Chances are, if the clone tool works, so does the backup one. All I had to do was reinstall Grub, and this was done within the session. The computer is running fine, is the one my wife uses. I just wanted for the first time since ownership in 2012, place the 128GiB m4 SSD on a SATA-3 port & see how fast it is, turned out to be a lot of work for nothing, while the read speeds are over 500MB/sec, writes are barely over 200MB/sec. The 180GiB Intel 330 SSD purchased a few months later reads & writes at over 500MB/sec. Though the experiment did prove something, that Macrium Reflect can clone Linux OS's.
The only catch to using Macrium Reflect, is that one needs a Windows computer, or borrow one to download Macrium Reflect from File Hippo (OEM site leads one to Download.com, a scummy site), have provided the best one below. The File Hippo version is clean and has no PUP's, safe to install on any Windows version. The only catch when creating bootable media is that the one for the matching bit version (32 or 64 bit) must be the same, or the operation may fail. Normally this is no issue, since the majority of computer in use today are 64 bit. The Windows installer will select the proper bit version for the computer, so if used for Linux, be sure to keep this in mind. Use a computer of the same bit version or higher (64 bit preferred). While the installed Macrium Reflect can create a 32 bit ISO for booting on a 64 bit computer, it doesn't work the other way around, the 32 bit computer is incapable of creating the proper WinPE ISO because the needed components aren't there.
Yet this is just one example of how a tool designed for Windows, also does the same with Linux, just as there are many Linux based tools (MiniTool Partition Wizard being one, if bootable CD version) for Windows. It's a two-way streak that many Windows users knows & accepts, yet many Linux users will refuse to use a Windows tool for the same operations. In the case of MiniTool Partition Wizard, it can create Linux partitions, just not alter these afterwards. Some still uses GParted Live, what this lacks is the function to rebuild the MBR, which can make many Windows computers that once dual booted with Linux & now doesn't, bootable again.
Macrium Reflect is a lot easier to work with than Clonezilla, and just two days back, seen it with my own eyes, as far as cloning goes. I've backed up Linux Mint installs, though have yet to restore one, that will be my next task, being that there's no EULA to abide by (can have the same copy on another like machine with similar hardware). Though I'd recommend if restoring on a different computer, try & stick with one where the CPU is of the same family, and avoid restoring images from Intel computers onto AMD ones & vise versa. This would apply to any OS. Though there is an option to restore to dissimilar hardware, don't know if this would be effective with a Linux OS.
BTW, am about to perform a 2nd clone, am going to upgrade my 1TiB Seagate Data drive to a 1TiB WD RE4, which is made to run for years on end, perfect for servers. So hopefully all will turn out OK, and will have a HDD with more warranty than the current, these were new pulls from servers that were upgraded to much larger 8TiB (helium filled) HDD's for long term use.
Edited by cat1092, 11 July 2016 - 04:08 AM.