Bug 1337014

Created attachment 1158606 [details]
File: anaconda-tb

Created attachment 1158607 [details]
File: anaconda.log

Created attachment 1158608 [details]
File: environ

Created attachment 1158609 [details]
File: journalctl

Created attachment 1158610 [details]
File: lsblk_output

Created attachment 1158611 [details]
File: lvm.log

Created attachment 1158612 [details]
File: nmcli_dev_list

Created attachment 1158613 [details]
File: os_info

Created attachment 1158614 [details]
File: program.log

Created attachment 1158615 [details]
File: storage.log

Created attachment 1158616 [details]
File: ifcfg.log

Created attachment 1158617 [details]
File: packaging.log

Similar problem has been detected:

I'm installing Fedora 24 beta from scratch. All I have done so far is to repartition the hard drive I want to use with the Disks software. It could not successfully delete two partitions, which I selected to be overwritten using the Anaconda Installer's partitioning options. This appeared to be successful, but the Anaconda Installer crashed when I tried to set up a user account name in the next step of the installation process. The application crashed before I had a chance to type anything in its window.

cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-Cinnamon-Live-24_B-1-6 rd.live.image rd.live.check quiet
hashmarkername: anaconda
kernel:         4.5.2-302.fc24.x86_64
other involved packages: python3-blivet-1.20.1-1.fc24.noarch, system-python-libs-3.5.1-7.fc24.x86_64, python3-pyparted-3.10.7-3.fc24.x86_64
package:        anaconda-core-24.13.4-1.fc24.x86_64
packaging.log:  
product:        Fedora
reason:         _ped.IOException: Partition(s) 3 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
release:        Fedora release 24 (Twenty Four)
reproducible:   Not sure how to reproduce the problem
version:        24

Similar problem has been detected:

This problem is a continuation of the problem I filed previously. I was installing Fedora 24 beta and used the Disks tool to attempt to clear out a hard drive I wanted to use. Two partitions could not be deleted. I selected them to be overwritten in the Anaconda Installer options for partitioning and the installer crashed after I moved on to the next option, which was to set up a user account name.
Another form to file an error report appeared after I reported the error I just mentioned; they may be duplicates. The message Fedora sends me is:
"_ped.IOException: Partition(s) 3 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes."

cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-Cinnamon-Live-24_B-1-6 rd.live.image rd.live.check quiet
hashmarkername: anaconda
kernel:         4.5.2-302.fc24.x86_64
other involved packages: python3-blivet-1.20.1-1.fc24.noarch, system-python-libs-3.5.1-7.fc24.x86_64, python3-pyparted-3.10.7-3.fc24.x86_64
package:        anaconda-core-24.13.4-1.fc24.x86_64
packaging.log:  
product:        Fedora
reason:         _ped.IOException: Partition(s) 3 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
release:        Fedora release 24 (Twenty Four)
reproducible:   Not sure how to reproduce the problem
version:        24

You should need to use any other utility to delete partitions, but if you do you need to make sure something in the live environment hasn't mounted them before starting anaconda. Best way to do this is to reboot and run anaconda from the initial welcome dialog.

It's difficult to tell what's holding the mount in the original report, lsof isn't reporting anything. Could you:

1. Start the installer from the welcome screen
2. run the installation w/o doing anything else in the live environment
3. when it crashes open a terminal and run:
  fuser /mnt/sysimage

maybe that will give us more details.

I also see a traceback in the logs from creating a user named 123, as well as what looks like multiple runs. It's easier to tell what's going on if the logs contain a single attempt.

Brian, 

I ran this scenario again and noted a few extra things: When I ran the install like you suggested above (don't use anything in the Live image), and selected standard US English for language and layout, everything installed correctly. However, when I installed using the Russian language and the 'ru' keyboard layout, after the files copy to the dis, the progress bar stops about 1/3 of the way through and zits for several minutes before crashing. Whether this has anything to do with the language settings themselves or because I used '"123" as the username and password/root password, I don't know. Follwing this message, you will find the logs from a virgin install that exhibited this error. 

Also, when I ran 'fuser /mnt/sysimage', nothing showed. There are contents in the /mnt/sysimage directory, but no output from the fuser command.

Let me know what else I can do that will help with debugging.

Geoff

Created attachment 1159710 [details]
anaconda.log

Created attachment 1159711 [details]
dnf.log

Created attachment 1159712 [details]
dnf.rpm.log

Created attachment 1159713 [details]
journal.log

Created attachment 1159714 [details]
ks-script-5pepjbk3.log

Created attachment 1159715 [details]
ks-script-huo8ag6_.log

Created attachment 1159716 [details]
ks-script-xfr7kjrt.log

Created attachment 1159717 [details]
packaging.log

Created attachment 1159718 [details]
program.log

Created attachment 1159719 [details]
storage.log

To: Brian Lane in Comment 15

Unfortunately, I can't follow your directions; I've received them too late, however, I successfully attempted the installation again on the same disk. I did not use the Disks tool and Anaconda wrote over the partitions and installed the OS successfully.

The username creation problem is bug 1339237 and this one may be helped by my patch for bug 1330820 so I'm going to close it as a dupe of that even though it isn't exactly the same.

*** This bug has been marked as a duplicate of bug 1330820 ***