Description of problem: Using F18 smoke 9 on a 4 disk F14 VM. Previous install attempts led to not enough space to install, so selected reclaim, btrfs, and custom. Deleted all paritions except the swaps (why 2 I don't know) and created /boot as standard parition and / and /home as btrfs and selected striping. Error occured after entering root password. The following was filed automatically by anaconda: anaconda 18.37.5 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 630, in mount raise FSError("mount failed: %s" % e) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 860, in setup return self.mount(**kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2866, 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: mount failed: (32, 'mount: wrong fs type, bad option, bad superblock on /dev/sda1,\n missing codepage or helper program, or other error\n In some cases useful info is found in syslog - try\n dmesg | tail or so') Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.5 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 666945 [details] File: anaconda-tb
Created attachment 666946 [details] File: anaconda.log
Created attachment 666947 [details] File: environ
Created attachment 666948 [details] File: ifcfg.log
Created attachment 666949 [details] File: packaging.log
Created attachment 666950 [details] File: program.log
Created attachment 666951 [details] File: storage.log
Created attachment 666952 [details] File: syslog
Tried again. This time installer said enough space available to install Fedora, but I went ahead and selected btrfs, and customize. Deleted all partitions and then selected automatic configuration. Tried to explicitly size / to 20GB and saw that /home as at 20GB. Tried to set /home to 10GB, but then / dropped to 10GB. So, put / back to 20GB and clicked finished. Error occurred again after entering root password.
Tried again duplicating Comment 9, except let auto configuration stand. Errored out creating file system on /dev/sda2.
Never mind. Back VM storage configuration.
s/back/bad/
I have to reopen this bug as anaconda said my bug is reported as 889332. Anaconda was unhappy with my pre-created f18test LV to be formatted as ext3 and my pre-existing ext2 /boot. I donloade the kernel and initramfs from current f18 pxeboot subdirectory and the squashfs.img from LiveOS. Booted with this grub entry: title f18 netinst kernel /vmlinuz selinux=0 panic=-1 root=live:/dev/sdb1 rd_LVM_LV=vg_pinky/f18test LANG=en_US.UTF-8 initrd /initrd.img and anaconda was unable to mount the /boot. (I checked the "do not install bootloader" checkbox) Do you have a better idea to install a fresh f18 info my pre-existing VG? Endre/Ondra
Yes, I have the same proble. And Afetr I had tried to install Fedora18 and failed, I have tried to install Fedora17. But it's failed too. After I have installed Fedora17, the problem is I can't boot my computer: grub loadingread error. I have tried anything that I can find from internet. It doesn't work. But when I was installing Fedora18's package (/dev/mapper/home or other things: decided to the mount point of home), I faced the same problem as you.
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.
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days