Created attachment 733302 [details]
File: anaconda.log

Created attachment 733303 [details]
File: backtrace

Created attachment 733304 [details]
File: environ

Created attachment 733305 [details]
File: ifcfg.log

Created attachment 733306 [details]
File: lsblk_output

Created attachment 733307 [details]
File: nmcli_dev_list

Created attachment 733308 [details]
File: program.log

Created attachment 733309 [details]
File: storage.log

Created attachment 733310 [details]
File: syslog

Created attachment 733311 [details]
File: anaconda-tb

Created attachment 733312 [details]
File: packaging.log

Without digging too far into it I can see that parted is reporting that the preexisting gpt disklabel on sda is invalid.

Shouldn't anaconda create a fresh GPT when it partitions the disk?
The existing GPT came from Anaconda (RHEL6), so I'm not sure why it's corrupt.

In any case, I used gdisk to re-build the the backup GPT (r for recovery options, d to load main GPT and rebuild backup, w to write to disk), then I tried again, and anaconda still crashed in the same spot.


I then pushed the big red button and wiped the beginning and end of the disk:
dd if=/dev/zero of=/dev/sda bs=512 count=34
dd if=/dev/zero of=/dev/sda bs=512 count=34 skip=$(( $( cat /sys/block/sda/size ) - 34 ))

And finally it installed!


It seems the interactive installer needs a checkbox or something to do an equivalent to 'clearpart --all --initlabel'

It's also curious that only LVM had a problem with the corrupt backup GPT.

When I used btrfs, it happily installed.

Argh, it installed, but now it won't boot...  See bug 949761

Description of problem:
Whenn selected to enter root password, it returned failure

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

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Alpha-TC6\x20x86_64 rd.live.check quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-0.rc6.git2.1.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Alpha-TC6

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run
    threading.Thread.run(self, *args, **kwargs)
  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/install.py", line 119, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 162, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 303, 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/lvmpv.py", line 113, in create
    lvm.pvcreate(self.device)
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 172, in pvcreate
    raise LVMError("pvcreate failed for %s: %s" % (device, msg))
LVMError: pvcreate failed for /dev/sda2: running lvm pvcreate --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  --dataalignment 1024k /dev/sda2 failed

Description of problem:
installing to hole disk 250 gb

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

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta-TC4\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-301.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Beta-TC4

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 126, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 162, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 303, 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/lvmpv.py", line 113, in create
    lvm.pvcreate(self.device)
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 172, in pvcreate
    raise LVMError("pvcreate failed for %s: %s" % (device, msg))
LVMError: pvcreate failed for /dev/sda2: running lvm pvcreate --config  devices { filter=["r|/sdd1$|","r|/sdd2$|","r|/sdd3$|","r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|","r|/sdd$|","r|/sdb1$|","r|/sdb2$|","r|/sdb5$|","r|/sdb$|","r|/sdc1$|","r|/sdc10$|","r|/sdc11$|","r|/sdc12$|","r|/sdc13$|","r|/sdc2$|","r|/sdc3$|","r|/sdc4$|","r|/sdc5$|","r|/sdc6$|","r|/sdc7$|","r|/sdc8$|","r|/sdc9$|","r|/sdc$|"] }  --dataalignment 1024k /dev/sda2 failed

Description of problem:
1. Choose 4 1TB devices as install target.
2. Manual partitioning: click automatic partitioning link
3. Click on /home, and change to Btrfs device type.
4. Begin installation.
Crash.

Version-Release number of selected component:
anaconda-19.25-1.fc19.x86_64

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file:   initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-19-Be rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 single BOOT_IMAGE=vmlinuz0 
core_backtrace: 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-301.fc19.x86_64
other involved packages: python-libs-2.7.4-4.fc19.x86_64, python-blivet-0.13-1.fc19.noarch
packaging.log:  
product:        Fedora
release:        Fedora release 19 (Schrödinger’s Cat)
type:           anaconda
ureports_counter: 1
version:        19

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 126, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 162, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 303, 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/lvmpv.py", line 113, in create
    lvm.pvcreate(self.device)
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 172, in pvcreate
    raise LVMError("pvcreate failed for %s: %s" % (device, msg))
LVMError: pvcreate failed for /dev/sdb1: running lvm pvcreate --config  devices { filter=["r|/sda1$|","r|/sdb1$|","r|/sdc1$|","r|/sdd1$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  --dataalignment 1024k /dev/sdb1 failed

In my case none of the devices ever had a GPT. Before starting the installer, I'd used wipefs -a on each partitioning and on each whole device.

Created attachment 746691 [details]
c19 anaconda-tb

Created attachment 746692 [details]
c19 anaconda.log

Created attachment 746693 [details]
c19 program.log

Created attachment 746694 [details]
storage.log

Created attachment 746695 [details]
c19 storage.state

Created attachment 746696 [details]
c19 storage.log

Proposing as beta blocker: "When using the custom partitioning flow, the installer must be able to Reject or disallow invalid disk and volume configurations without crashing."

It seems rather like at least some of these reports are not of the same bug. I think any failure of pvcreate is going to show up as a dupe of this bug, but they're not all necessarily failing for the same reason.

19:08:03,411 INFO program: Running... lvm pvcreate --config  devices { filter=["r|/sda1$|","r|/sdb1$|","r|/sdc1$|","r|/sdd1$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  --dataalignment 1024k /dev/sdb1
19:08:03,434 INFO program:   Device /dev/sdb1 not found (or ignored by filtering).

it looks kinda like the pvcreate command filtered out the partition it was trying to run on?

It looks like the partitioning didn't even complete. sdc and sdd aren't partitioned. sdb only has one partition, which should be only for btrfs, as LVM only needs one PV to meet the installation requirements. Yet the installer seems confused, trying to create multiple PVs, and before all partitions are made.

Description of problem:
Just tried to run an install with http://www.happyassassin.net/extras/ks/minimal_unattended.ks , a kickstart that usually works OK.

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

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta-TC4\x20x86_64 quiet ks=http://www.happyassassin.net/ks/minimal_unattended.ks BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-301.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Beta-TC4

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 126, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 162, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 303, 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/lvmpv.py", line 113, in create
    lvm.pvcreate(self.device)
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 172, in pvcreate
    raise LVMError("pvcreate failed for %s: %s" % (device, msg))
LVMError: pvcreate failed for /dev/vda2: running lvm pvcreate --config  devices { filter=["r|/loop3$|","r|/loop4$|","r|/loop5$|","r|/loop6$|","r|/loop7$|"] }  --dataalignment 1024k /dev/vda2 failed

I reproduced this simply by using the ks mentioned in comment #31 on Beta TC4. It works fine on Beta TC3. Looks like something broken between the two, and that's a very simple ks with a default layout. +1 Beta blocker.

OK - this is reliably reproducible for me *if I start with a blank disk*. So to reproduce:

1. Boot anaconda
2. Go to VT2, do 'fdisk /dev/vda', 'd' all partitions, 'w', and reboot
3. Boot anaconda with 'ks=http://www.happyassassin.net/ks/minimal_unattended.ks'

and that reproduces it. If I start with a populated disk - with F19 already on it - then it works OK.

I still can't reproduce it on TC3 following the above steps. I note that TC4's installer says something like "Waiting for 4 threads..." before it starts partitioning; TC3's just seems to run straight into it.

Discussed at 2013-05-13 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-13/f19beta-blocker-review-5.2013-05-13-16.00.log.txt . Accepted as a blocker: my reproducer violates "When using the guided partitioning flow, the installer must be able to ...Cleanly install to a disk with a valid ms-dos or gpt disk label and partition table which contains existing data and sufficient unpartitioned space for a Fedora installation" , and probably other reproducers violate other of the partitioning criteria too. This is clearly a bad enough issue.

http://bcl.fedorapeople.org/updates/950145.img should fix this by writing zeros to the first 10M of the partition location before creating it.

That's a hell of a fugly fix, but it seems to work here: my reproducer doesn't reproduce, with that updates= in place. (I tested that it _is_ a reliable reproducer without the updates= in place.)

https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.28-1.fc19 was pushed stable; closing.

Is there a deficiency in wipefs that causes the need to write 10MB of zeros to fix this bug?