[Bug 1767501] Re: do-release-upgrade leaves the system in a unbootable state

Ubuntu Foundations Team Bug Bot 1767501 at bugs.launchpad.net
Sat Apr 28 00:46:24 UTC 2018


** Tags added: artful2bionic

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

Title:
  do-release-upgrade leaves the system in a unbootable state

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I upgraded my Xubuntu Artful install to Bionic using the following
  command:

  do-release-upgrade -d

  And the entire process went smoothly, when it was asked to reboot the
  system I chose yes. After that, Xubuntu failed to boot with the
  following message:

  Error 0x1A (Security Violation)

  Then I rebooted and pressed F12 to see the available boot options and
  there were two equal entries from the disk where Xubuntu Artful was
  installed.

  Then I chose another install from another disk, and from that system I
  repaired the bootloader using the following command:

  LANGUAGE=C sudo grub-install --efi-directory=/media/usuario/EFI\
  SYSTEM/ --boot-directory=/media/usuario/Linux64/boot/ --uefi-secure-
  boot /dev/sdb

  Its output was:
   
  Installing for x86_64-efi platform.
  GUID Partition Table Header signature is wrong: be5608740128e852 != 5452415020494645
  GUID Partition Table Header signature is wrong: 0 != 5452415020494645
  GUID Partition Table Header signature is wrong: be5608740128e852 != 5452415020494645
  GUID Partition Table Header signature is wrong: 0 != 5452415020494645
  GUID Partition Table Header signature is wrong: be5608740128e852 != 5452415020494645
  GUID Partition Table Header signature is wrong: 0 != 5452415020494645
  Installation finished. No error reported.

  And then the upgraded Xubuntu was able to boot again.

  The HDD on which the system is installed has a MBR partition table, is
  bootable in UEFI and there is no Windows on this disk. I believe this
  combination was not well handled in the upgrade and ended leaving it
  in a unbootable state.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Apr 27 16:59:27 2018
  InstallationDate: Installed on 2017-07-24 (277 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1767501/+subscriptions



More information about the foundations-bugs mailing list