Bug 1051603 - Feature request: include fat & vfat drivers in "hostonly" initramfs
Summary: Feature request: include fat & vfat drivers in "hostonly" initramfs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 20
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-10 16:45 UTC by alweiner7
Modified: 2015-06-29 14:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:20:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description alweiner7 2014-01-10 16:45:58 UTC
Description of problem: Fresh install of F20 fell into dracut emergency shell. Message is displayed "You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them". I tried to manually mount a fat-format USB stick. The mount failed with message "unknown filesystem type vfat". The initramfs of the F20 fresh install was automatically created with the dracut default "hostonly". I confirmed on a second PC that the mount failure was due to the absence in the initramfs of the fat and vfat drivers. This problem may also exist for release upgrades via fedup.


Version-Release number of selected component (if applicable):


How reproducible: Whenever boot falls into a dracut emergency shell, if the initramfs was generated with the dracut default "hostonly" option, a manual mount of a fat-format usb stick will fail with the message "unknown filesystem type vfat"


Steps to Reproduce:
1. insert a fat-format USB stick in PC
2. edit grub "linux" command line to a nonexistent UUID for root
3. when dracut emergency shell is entered, try to manually mount the USB stick

Actual results: mount fails with message "unkonown filesystem type vfat


Expected results: mount succeeds


Additional info:

Comment 1 Fedora End Of Life 2015-05-29 10:25:56 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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-06-29 14:20:20 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.