Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1706094 - Failed to keep volume group name during upgrade
Summary: Failed to keep volume group name during upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 1652806
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-upgrade
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-03 14:26 UTC by developer@typeset.net
Modified: 2019-05-07 15:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-07 08:04:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description developer@typeset.net 2019-05-03 14:26:26 UTC 
Description of problem:
using dnf upgrade plugin, after reboot system hangs on unable to find root/disk.


How reproducible:
Unknown.  Only did upgrade once.


Steps to Reproduce:
1. sudo dnf system-upgrade download --refresh --releasever=30
2. sudo dnf system-upgrade reboot


Actual results:
Hangs on locating root disk/volume


Expected results:
Normal boot


Additional info:
Apparently /etc/default/grub had the wrong name for my volume group.  It had "fedora" instead of my volume group name.

To fix the problem I had to edit the /etc/default/grub and replace "fedora" volume group with the name of my volume group.  Rebuild grub configuration (EFI) via: grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.  I was then able to boot into Fedora 30.
Comment 1 Miroslav Suchý 2019-05-07 08:04:33 UTC 
See https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade

*** This bug has been marked as a duplicate of bug 1652806 ***
Comment 2 developer@typeset.net 2019-05-07 15:26:48 UTC 
I really don't think this is the same bug.  Here are some of the reasons I believe it isn't:

1) The grub entries WERE populated in the grub configuration, it was able to boot with the updated grub entry.  It only failed to complete the boot while looking for the root filesystem.  (wasn't able to find it because it had a misnamed volume group entry)

2) BUG 1652806 appears to be non-EFI boot issues.  My issue is EFI boot.  And the issue wasn't a corrupt grub config, or grub config missing boot entries.  Upgrade process had modified /etc/default/grub and changed the root volume group from mine to a default "fedora" entry


It is interesting that it happened during the upgrade of Fedora 30, I didn't have this issue when I upgraded to 29.
Note You need to log in before you can comment on or make changes to this bug.