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

[pbea]

I still don't know what package this is associated to but I have found a
workaround with grub.cfg. I am going to assign it to grub if that is a
package.

Using a rescue disk I searched the non-functioning hard drive boot
directory for the not found UUID. It appeared over a dozen times. The
problem was was that this file is auto-generated by something.

Taking a chance (not that much of a chance with a non-functioning hard
drive) I used a text editor and replaced all the not found UUIDs with
the new UUID of the cloned hard drive's root partition.

That non-functioning drive now boots. Since boot.cfg was auto-generated,
I tried "sudo update-grub" to see if the UUIDs stayed the same. They did
so my messy workaround works.

Unfortunately Kubuntu still has a nasty problem with what caused this.

Hope this helps.

** Package changed: ubuntu => grub (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub in Ubuntu.
https://bugs.launchpad.net/bugs/1313408

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

Status in “grub” package in Ubuntu:
  New

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/grub/+bug/1313408/+subscriptions