Maybe this should be asked on an Ubuntu resources page – but thought you guys could help direct me to a solution – since it relates to booting and/or bios (I guess).
I’ve wiped out windoze and installed 16.04 on my HDD many weeks ago; I had problems with portions of the drive that seem to be dead.
I then installed 17.04 on a Kingston SSD with a view to eventually install in lieu of the HHD. So, I’ve been booting from the SSD (via USB) ‘til now. And I was getting a Grub (grey page) with a choice between the 16.04 on HD and the 17.04 on sdb2. Which was fine and enjoying 17.04 fully. I was putting on suspend most of the time when not using but re-boot never was a problem…so far.
Now suddenly when trying to reboot… nothing. If I use my flashdisk to boot, I can see in Places both the HDD and the SSD. I can get to the files and Disks/GParted do identify the drives… so they are alive. And they are mounted – if not I click and re-mount right then.
You can see I’m a newbie…some way. So…how do I get the SSD to reboot…and reboot again?
Do I have to use Boot Repair from a USB-key on the SSD? Any risks or things to know?
Would one of you having worked the tranches happen to just know a link to a resource that would just be the right thing to do?
Thanks in advance !
What disk is set to boot from in your bios? Maybe it wants to boot from your broken hdd? If it does, set it to boot from your sdd. If it still doesn’t work try reinstalling grub.
See this this for reference.
I tried re-installing Grub. Didn’t work
SO I went for reinstalling UM…not get ‘stuck’ at Configuring apt step - seems to be caught in a loop.
Stuck as in: your install application freezes? Or do you get error messages.
Also, have looked at your bios boot options yet?
USB was set to boot first in the Bios and as I said, it did work well for a while, but then went to a stop one morning.
Tried a boot repair but got a message that Grub was missing !
Tried a few other things with no result.
So decided to go for a clean reinstall (not an issue, all docs and stuff in the cloud)
But… it gets stuck at ‘Configuring Apt…’ with msgs like:
usr/lib/ubiquity/frontend/gtk_components/nm widgets.py:131: Warning: Source ID XXXXXX was not found when attempting to remove it
Glib.source_remove (self.rows_changed_id)
Yeah weird message. Something wrong with the installer (its called ubiquity). Did you choose automatic partioning in the installer? Are you sure you chose the right disk?
In the live system running from the usb you can look in gnome-disks and check the disks health with SMART.
Indeed. Automatic partitioning, yes.
SSD health is OK on all fronts. Did check that. The HDD has some bad sector (les then 5%)
Made sure the right disk was selected for boot loader (i.e. SSD)
But maybe is it checking the HDD in any case ?..just wonder.
.
Life makes wonder… I did a reinstall from the very beginning
This time around it all worked well. I’m amazed.
What either the system, the weather or myself did wrong?
No idea. Thanks for listening… 
