[Bug 1313408] Re: Total Crash at logo screen with new cloned hard drive

[pbea]

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
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1313408

Title:
  Total Crash at logo screen with new cloned hard drive

Status in “grub2” package in Ubuntu:
  Invalid

Bug description:
  Good Day . . .

  KDE SC 4.13 - Kubuntu 14.04

  An apology. I do not know who wants to clain ownership of this issue.
  Please transfer this to the appropriate department. If you find that
  this is a KDE issue then please advise. Thank You.

  I changed my ssd boot hard drive after cloning the old ssd hard drive.
  This process went flawlessly.

  I changed the UUID and labels of the new hard drive so that if both
  hard drives were installed my computer would not have a heart attack
  after finding two identical storage devices.

  With the new hard drive installed I booted. The boot process went as
  far as the Kubuntu logo screen and it then dropped to a terminal with
  a crash message. I rebooted in safe mode and the following appeared
  eventually:

  ALERT! /dev/disk/by-uuid/. . . does not exist. Dropping to a shell!

  I checked fstab and nothing is referred to by UUID. I am set up for
  labels.

  The old hard drive works as I am sending this on it.

  I cannot report his any other way since your apport documentation says
  "Most of this information is gathered when you use apport to report
  the bug". Unfortunately this hard drive works while the problem one
  does not boot.

  Please contact me for further information such as where does the
  incorrect UUID come from so I can get up and running.

  Thank You.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1313408/+subscriptions