Description of problem: Maybe should not have used btrfs for all except swap? Just trying things.... Version-Release number of selected component: anaconda-18.12 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.0-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.12 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 590, in mount : raise FSError("filesystem has not been created") : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 1129, in setup : return self.mount(*args, **kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2711, in mountFilesystems : chroot=rootPath) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1641, in mountFilesystems : readOnly=readOnly, skipRoot=skipRoot) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 218, in turnOnFilesystems : skipRoot=False) : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 101, 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 87, in run : threading.Thread.run(self, *args, **kwargs) :FSError: filesystem has not been created
Created attachment 622439 [details] File: anaconda-tb
Created attachment 622440 [details] File: product
Created attachment 622441 [details] File: type
Created attachment 622442 [details] File: ifcfg.log
Created attachment 622443 [details] File: storage.log
Created attachment 622444 [details] File: version
Created attachment 622445 [details] File: environ
Created attachment 622446 [details] File: anaconda.log
Created attachment 622447 [details] File: syslog
Created attachment 622448 [details] File: hashmarkername
Created attachment 622449 [details] File: packaging.log
Created attachment 622450 [details] File: cmdline_file
Created attachment 622451 [details] File: release
Created attachment 622452 [details] File: program.log
Can you expand a bit on your original comment? Do you remember exactly which steps you took that resulted in this traceback?
Pretty sure it went something like this: selected a virtual disk checked the custom partitioning created /, sized it and selected btrfs fs created /home, sized it and selected btrfs fs created swap, sized it, created /boot, sized it and selected btrfs then clicked ??finished?? I don't recall. Will try to recreate later today.
Well, rc3 works fine in a VM with btrfs for / and /home. There may have been VM issues that caused this bug originally. I would close this, but defer to you.
Thanks for retesting.
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
Created attachment 637532 [details] screenshot of abrt screen Please reopen bugreport. I selected one of those '0 byte disks' i have am still having trouble in other bug-reports. First, i cannot do anything with automatic partitioning (there is a already a bugreport for that) i went to manual partitioning and reformated it as / and anaconda just let me start installing (these are reported in another bugreport somewhat. The '0 byte disks' was part of a previous BTRFS, but i believe that only some disks have survived... a partial BTRFS? Could a partial BTRFS account for these '0 byte' disks? (and the associated issues that -in my case- have spanned a couple of bugreports? In this case, i started installing and then ABRT showed this bugreport, but it seems ABRT does nothing in reopening.
Created attachment 637533 [details] storage.log
Created attachment 637534 [details] program.log
Created attachment 637535 [details] anaconda error
Created attachment 637536 [details] anaconda.log