Bug 1174440 - fedup uefi System can not mount vfat on boot upgrading from f19 to f21
Summary: fedup uefi System can not mount vfat on boot upgrading from f19 to f21
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 20:27 UTC by oscarcontreras
Modified: 2015-02-18 11:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 11:54:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description oscarcontreras 2014-12-15 20:27:51 UTC
Description of problem:
Upgrading from fedora19 to fedora21 with fedup in a Sony Vaio laptop with UEFI. After preparation with the commands:

  sudo yum update fedup fedora-release
  sudo fedup --network 21 --product=workstation

I have a new entry in grub2: "Fedora, with Linux fedup."

I reboot to this entry. After booting to finish upgrade from Fedora 19 to 21 mounting of /boot/efi fails:

Mounting /boot/efi...
boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since sáb 2014-12-13 12:29:10 CET; 3min 0s ago
Where: /boot/efi
What: /dev/disk/by-uuid/CA08-7D51
Process: 859 ExecMount=/bin/mount /dev/disk/by-uuid/CA08-7D51 /boot/efi -t vfat (code=exited, status=32)

dic 13 12:29:10 localhost.localdomain mount[859]: mount: unknown filesystem type 'vfat'
dic 13 12:29:10 localhost.localdomain systemd[1]: boot-efi.mount mount process exited, code=exited status=32
dic 13 12:29:10 localhost.localdomain systemd[1]: Failed to mount /boot/efi.
dic 13 12:29:10 localhost.localdomain systemd[1]: Unit boot-efi.mount entered failed state.


Version-Release number of selected component (if applicable):
fedup-0.9.0-2.fc19


How reproducible:
Always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
This seems a similar problem to Bug 1044346. However I am using fedup-0.9.0-2.fc19.

The fedup preparation gives the following result (I get a message referring to rpmfusion GPG keys but fedup says "exiting cleanly".

YumBaseError: The GPG keys listed for the "RPM Fusion for Fedora 21 - Free" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

Failing package is: kmodtool-1-23.fc20.noarch
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-21

2734.264 fedup:() /bin/fedup exiting cleanly at Fri Dec 12 22:59:05 2014

Comment 1 Fedora End Of Life 2015-01-09 21:34:22 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-18 11:54:16 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.