Thank You for the replies. They are appreciated. The comment about update-grub is invalid. I did exactly what you wrote as a workaround.
The new ssd hard drive will not boot. Running update-grub is not an option. It was necessary to use a rescue disk and modify text files with find and replace. If what you are suggesting is what I did as reported in my first comment then this is really messy and is only for very experienced users. It appears that Grub2 cannot adapt to a cloned hard drive with a modified UUID until the above is completed. I did also mention that I use labels in fstab so that I can get around the annoyance of modifting files when I format a storage hard drive whch happens quite often as they become full. As long as I keep the same label. No problems. Unfortunately this was the first time that I was forced to clone my boot drive. Thank You for your attention to this matter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313408 Title: Total Crash at logo screen with new cloned hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1313408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs