#412 aarch64 qcow won't boot when installed from testing tree
Closed: Fixed 3 years ago Opened 3 years ago by dustymabe.

The updates tree works fine. The testing tree yields a non-bootable machine with the following message after passing the grub menu:

error: failed to create kernel parameters.

  Failed to boot both default and fallback entries.

Press any key to continue...

After trying again I see:

error: failed to install/update FDT.

Press any key to continue...

The current difference between the updates and testing aarch64 trees is:

ostree diff commit old: 2f78eaf5c843a3a8c03b21ba9db41073864e8a6b941679a126ac27b910fe66dc
ostree diff commit new: 40a4fdfb17242b97bffb1da84c127f60131ca49c1705a407e327ffe32357c39d
Upgraded:
  NetworkManager 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27
  NetworkManager-libnm 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27
  NetworkManager-team 1:1.8.4-7.fc27 -> 1:1.8.6-1.fc27
  cloud-utils-growpart 0.27-18.fc27 -> 0.30-1.fc27
  criu 3.6-1.fc27 -> 3.7-3.fc27
  glib2 2.54.2-1.fc27 -> 2.54.3-2.fc27
  glibc 2.26-21.fc27 -> 2.26-24.fc27
  glibc-all-langpacks 2.26-21.fc27 -> 2.26-24.fc27
  glibc-common 2.26-21.fc27 -> 2.26-24.fc27
  gnutls 3.5.16-4.fc27 -> 3.5.17-1.fc27
  grub2-common 1:2.02-19.fc27 -> 1:2.02-21.fc27
  grub2-efi-aa64 1:2.02-19.fc27 -> 1:2.02-21.fc27
  grub2-tools 1:2.02-19.fc27 -> 1:2.02-21.fc27
  grub2-tools-extra 1:2.02-19.fc27 -> 1:2.02-21.fc27
  grub2-tools-minimal 1:2.02-19.fc27 -> 1:2.02-21.fc27
  libassuan 2.4.3-6.fc27 -> 2.5.1-1.fc27
  libcrypt-nss 2.26-21.fc27 -> 2.26-24.fc27
  libgcrypt 1.8.1-3.fc27 -> 1.8.2-1.fc27
  libtasn1 4.12-3.fc27 -> 4.13-1.fc27
  oci-register-machine 0-5.12.git3c01f0b.fc27 -> 0-5.13.git66691c3.fc27
  ostree 2017.15-1.fc27 -> 2018.1-1.fc27
  ostree-grub2 2017.15-1.fc27 -> 2018.1-1.fc27
  ostree-libs 2017.15-1.fc27 -> 2018.1-1.fc27
  python3 3.6.3-2.fc27 -> 3.6.4-3.fc27
  python3-libs 3.6.3-2.fc27 -> 3.6.4-3.fc27
  rpm-ostree 2017.11-1.fc27 -> 2018.1-1.fc27
  rpm-ostree-libs 2017.11-1.fc27 -> 2018.1-1.fc27
  sed 4.4-3.fc27 -> 4.4-4.fc27
  timedatex 0.4-5.fc27 -> 0.5-2.fc27
  vim-minimal 2:8.0.1427-1.fc27 -> 2:8.0.1428-3.fc27
Removed:
  python-rhsm-certificates-1.20.1-3.fc27.aarch64
Added:
  gdbm-devel-1:1.13-6.fc27.aarch64
  subscription-manager-rhsm-certificates-1.21.1-1.fc27.aarch64

I suspect grub is the problem but it will need more testing.


confirmed. I built a tree with only this new grub from updates testing and the aarch64 system fails to boot in the same way as shown above. Here is a link to the image: https://dustymabe.fedorapeople.org/new-grub-aarch64.qcow2

One wrinkle here is https://github.com/projectatomic/rpm-ostree/issues/853 AKA https://github.com/projectatomic/rpm-ostree/pull/969

Basically we don't update /boot. This usually shouldn't matter but it's a wrinkle to be aware of.
It'd be useful to know whether you upgraded an existing install, or if you built a fresh qcow2.

It'd be useful to know whether you upgraded an existing install, or if you built a fresh qcow2.

fresh install. I think when I was playing around with this updating an existing install did not show the problem.

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata