Agreed, boot repair would have been my first choice.I really can't think of a good reason to do so and I missed the boot-repair recommendation. I wonder if they tried. It's surprisingly successful in many situations and, if not, it has a great report you can share with us to help diagnose the issue. It's actually one of the first tools I'd reach for in this situation.
As long as you have that many partitions and instances of Ubuntu Grub is confused about which to boot.OK, no need to cry over spilled milk - I am after a solution - rehashing / speculating what MAY have caused the problem is now pointless.
But I need to have a better reason then just "try it , it won't hurt.
As I said before , I am paranoid.
I rather live with this than risk loosing access to all current packages. I do not keep record of them, and I am sure there is a command to get a list of them...but why bother ? ( i do not need a list , i need to be able to use them...)
In reality - I do not have a boot problem , my system boots just fine, - it is grub who is having an issue not having an access to an image it claims to have found.
Because it *may* just do the trick and, if not, there's an option to export your boot information to share with us so that we can see if the problem is easily fixed.But I need to have a better reason then just "try it , it won't hurt.
I'm not sure they actually want help at this point. I'm gonna bow out.Agreed, boot repair would have been my first choice.
Where? On your /dev/sda drive or on one of the 2 TB drives?I tried to clean-up a decent size partition to do the backup.
You will have received something like thisgparted did not cooperate - would not let me delete "busy" partition.