Created attachment 737944 [details]
File: anaconda.log

Created attachment 737945 [details]
File: backtrace

Created attachment 737946 [details]
File: environ

Created attachment 737947 [details]
File: ifcfg.log

Created attachment 737948 [details]
File: lsblk_output

Created attachment 737949 [details]
File: nmcli_dev_list

Created attachment 737950 [details]
File: packaging.log

Created attachment 737951 [details]
File: program.log

Created attachment 737952 [details]
File: storage.log

Created attachment 737953 [details]
File: syslog

Created attachment 737954 [details]
File: anaconda-tb

We deactivate the array after wiping the old filesystem from it. When we try to activate it just before creating the new filesystem on it, it's status is reported as already active, which is a lie. We proceed to try to format it, but the device node does not exist since the device is not active.

*** Bug 967686 has been marked as a duplicate of this bug. ***

Description of problem:
Been attempting to install too many times tonight. Opted to simply reformat existing partitions created by Anaconda on an earlier attempt. 

Version-Release number of selected component:
anaconda-19.30-1

Additional info:
reporter:       libreport-2.1.4
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta\x20x86_64 rd.live.check extlinux BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.2-301.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Beta

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run
    threading.Thread.run(self, *args, **kwargs)
  File "/usr/lib64/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 138, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 165, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 306, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 471, in execute
    options=self.device.formatArgs)
  File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 779, in create
    DeviceFormat.create(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/blivet/formats/__init__.py", line 310, in create
    raise FormatCreateError("invalid device specification", self.device)
FormatCreateError: ('invalid device specification', '/dev/md/root')

(In reply to rangerwreck from comment #14)
> Description of problem:
> Been attempting to install too many times tonight. Opted to simply reformat
> existing partitions created by Anaconda on an earlier attempt. 


WARNING this method can result in user inflicted data loss 

do not attempt to activate any md device with existing user personal data  by example /home because user DATA LOSS WILL HAPPEN

because this method detects the raid devices but do not recognize the existing format so cannot give a mount point without reformat them

so don't activate the user data devices if any you can mount them manually editing the fstab after the install

but if you select reformat you will lose your data

the method:

I have existing md raids level 1 (linux kernel raid) and a workaround to install Fedora 19 Beta x86_64 over the existing raid devices is:

customize the install but leave to last the partitioning.
before to enter partitioning

change to virtual terminal 2 (ctrl alt f2) and assemble your md devices as /dev/mxN by example mine are (/boot /dev/md1, / /dev/md5, swap /dev/md6):

mdadm --assemble /dev/md1 /dev/vda3 /dev/vdb3
mdadm --assemble /dev/md2 /dev/vda5 /dev/vdb5
mdadm --assemble /dev/md3 /dev/vda6 /dev/vdb6

return to install program ctrl alt F7

select partitioning
and select your 2 disks
and in installation options select:
custom partitioning
in the next dialog "manual partitioning" select "reload storage configuration from disk" is the button with the circle arrow
and in the next dialog press scan disks after a while the installation program go to installation options
press done
press custom partitioning that show manual partitioning
there click in unknown and your md device shows as 0 1 2 3 by the example md devices above

select reformat (NOT REFORMAT EXISTING DATA DEVICES), and give a mount point to each of them

REVIEW YOUR PARTTION IF AT THIS POINT YOU SELECTED A MD DEVICE WITH EXISTING DATA ABORT THE INSTALL

click done
before you click begin install
go to virtual terminal 2 and stop your md devices with:

mdadm --stop /dev/md1
mdadm --stop /dev/md2
mdadm --stop /dev/md3

if you don't stop the md devices the installer will show a error

return to installer with ctrl alt F7

and click begin install

A fix for this will be in the next build of python-blivet (0.15-1).

python-blivet-0.15-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.15-1.fc19

Package python-blivet-0.15-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-blivet-0.15-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9977/python-blivet-0.15-1.fc19
then log in and leave karma (feedback).

(In reply to David Lehman from comment #16)
> A fix for this will be in the next build of python-blivet (0.15-1).

I tested Fedora-19-TC2-x86_64-DVD installing over existing 4 RAID1 partitions (/boot, /, swap /var/lib/lh/syslinux) and worked well thanks.

also tried the resulting kickstart from the above install, so the only step I did was select the existing 4 RAID1 partitions and formating (/boot /) and mounting /var/lib/lh/syslinux

so python-blivet (0.15-1) solves the bug for me, thanks

python-blivet-0.15-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

*** Bug 958916 has been marked as a duplicate of this bug. ***