Bug 1175041 - Anaconda doesn't warn user correctly about /boot mount point on btrfs partitions
Summary: Anaconda doesn't warn user correctly about /boot mount point on btrfs partitions
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-17 03:18 UTC by Ali AlipourR
Modified: 2015-03-19 20:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-29 12:48:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ali AlipourR 2014-12-17 03:18:09 UTC
Description of problem:
Anaconda doesn't warn user when He/She tries to use btrfs for /boot

Version-Release number of selected component (if applicable):
fc21.x86_64 workstation live

How reproducible:


Steps to Reproduce:
1.put machine in UEFI mode (without CSM)
2.initialize a disk in GPT layout to be used for instalaltion
3.boot live cd and in anaconda partitioning page make a btrfs file system for root 
4-make a "EFI system partition" for /boot/efi
5-begin installation

Actual results:
system wont boot, gives kernel panic, "can't mount VFS"

Expected results:
anaconda warn user to select a ext4 file system for /boot 

Additional info:
if I install with this layout system will boot correctly after installation:
"EFI system partition" on /boot/efi
ext4 on /boot
btrfs on /

but if I use this layout it will give me kernel panic "can't mount VFS":
"EFI system partition" on /boot/efi
btrfs on /

Comment 1 David Shea 2014-12-17 15:22:50 UTC
Please attach the log files from the installation, available in /var/log/anaconda in the installed system or /tmp in the installer environment, to this bug as individual, text/plain attachments.

Comment 2 HLFH 2015-03-19 18:57:33 UTC
I have exactly the same issue in Fedora 21 AND in Fedora 22 alpha. This is the /tmp/anaconda.log : http://pastebin.com/yBbXzMZ7

Comment 3 HLFH 2015-03-19 18:59:45 UTC
Please reopen.

Comment 5 HLFH 2015-03-19 20:53:47 UTC
Thanks David Shea. Before the installation via a Fedora LiveUSB, the needed command 'yum update anaconda' fixed the issue on Fedora 22 Alpha.

Also according to this: https://bugzilla.redhat.com/show_bug.cgi?id=1200539


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