Bug 901408 - FSError: filesystem has not been created
Summary: FSError: filesystem has not been created
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:da965e7c915039056d5ee5433e2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 06:24 UTC by vikram goyal
Modified: 2014-02-05 15:09 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:09:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (710.78 KB, text/plain)
2013-01-18 06:25 UTC, vikram goyal
no flags Details
File: anaconda.log (26.59 KB, text/plain)
2013-01-18 06:26 UTC, vikram goyal
no flags Details
File: environ (776 bytes, text/plain)
2013-01-18 06:26 UTC, vikram goyal
no flags Details
File: ifcfg.log (2.77 KB, text/plain)
2013-01-18 06:26 UTC, vikram goyal
no flags Details
File: packaging.log (346.98 KB, text/plain)
2013-01-18 06:26 UTC, vikram goyal
no flags Details
File: program.log (32.80 KB, text/plain)
2013-01-18 06:26 UTC, vikram goyal
no flags Details
File: storage.log (143.53 KB, text/plain)
2013-01-18 06:27 UTC, vikram goyal
no flags Details
File: syslog (92.03 KB, text/plain)
2013-01-18 06:27 UTC, vikram goyal
no flags Details

Description vikram goyal 2013-01-18 06:24:09 UTC
Description of problem:
I wanted to install f18 like this:
/boot btrfs /dev/sda1 /dev/sdb6 raid1
/        btrfs /dev/sda2 /dev/sdb7 raid1

But the installer does not let me do it.
1} If I create the fs myself prior to installation, then the mount point for / is not selected as it requires
     reformat but reformat option is greyed, so it won't let me install.
2} If I create the partitions but do not format them prior to installation then the options for mount points
     & formatting etc remain greyed & cannot be selected. Clicking + sign asks for desired size which I interpret
     as creating a new partition. Basically one cannot select a prior partition table for installation if it is to be btrfs.
3} Also one cannot have boot & root or any other mount point on different partitions if one goes by creating mount
     points from the GUI for btrfs. The logic just bunches up togather all btrfs mounts on single volume - here- partition
4} If a partition does not have recognizable fs then it is not possible to select btrfs as fs from filesystems in reformat.

So What I did was that I created btrfs on /dev/sda1 as label boot & /dev/sda2 as label root prior to installation.
Booted the install disk. Selected only one disk. Selected BTRFS & manual partition.

I could now select sda1 for boot & also could click reformat as btrfs. So I selected the partition & selected mount
point /boot & reformat as btrfs

Same I did with the second partition for /

Started installation & it crashed
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 594, in mount
    raise FSError("filesystem has not been created")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 1140, in setup
    return self.mount(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2881, in mountFilesystems
    chroot=rootPath)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1655, in mountFilesystems
    readOnly=readOnly, skipRoot=skipRoot)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 193, in turnOnFilesystems
    skipRoot=False)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall
    turnOnFilesystems(storage)
  File "/usr/lib64/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
    threading.Thread.run(self, *args, **kwargs)
FSError: filesystem has not been created

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.x86_64
other involved packages: 
package:        anaconda-18.37.11
product:        Fedora
release:        Cannot get release name.
type:           libreport
version:        18

Comment 1 vikram goyal 2013-01-18 06:25:54 UTC
Created attachment 682159 [details]
File: anaconda-tb

Comment 2 vikram goyal 2013-01-18 06:26:00 UTC
Created attachment 682161 [details]
File: anaconda.log

Comment 3 vikram goyal 2013-01-18 06:26:03 UTC
Created attachment 682162 [details]
File: environ

Comment 4 vikram goyal 2013-01-18 06:26:05 UTC
Created attachment 682163 [details]
File: ifcfg.log

Comment 5 vikram goyal 2013-01-18 06:26:35 UTC
Created attachment 682165 [details]
File: packaging.log

Comment 6 vikram goyal 2013-01-18 06:26:44 UTC
Created attachment 682166 [details]
File: program.log

Comment 7 vikram goyal 2013-01-18 06:27:05 UTC
Created attachment 682167 [details]
File: storage.log

Comment 8 vikram goyal 2013-01-18 06:27:22 UTC
Created attachment 682168 [details]
File: syslog

Comment 9 Fedora End Of Life 2013-12-21 10:30:44 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 10 Fedora End Of Life 2014-02-05 15:09:34 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.