Description of problem: I run anaconda from live workstation beta rc4. I booted in uefi. /dev/sda had mbr so I had to delete all partitions. I had to go to reclaim space twice to do it (I wanted to delete just one partition which doesn't work with mbr on UEFI). Original layout was: /dev/sda1 - /boot on ext4. /dev/sda2 - / and swap on lvm. This error occured after I started the installation. Version-Release number of selected component: anaconda-core-21.48.13-1.fc21.x86_64 The following was filed automatically by anaconda: anaconda 21.48.13-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 213, in commit return self.__disk.commit() File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 41, in new ret = fn(*args, **kwds) File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 270, in commit self.partedDisk.commit() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 1878, in _destroy self.disk.originalFormat.commit() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 964, in destroy self._destroy() File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 336, in execute self.device.destroy() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 361, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 364, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 216, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 190, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) 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/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) IOException: Partition(s) 2 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. Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Workstation-x86_64-2 ro rd.live.image quiet rhgb rd.live.check executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.1-302.fc21.x86_64 other involved packages: python-blivet-0.61.8-1.fc21.noarch, python-libs-2.7.8-4.1.fc21.x86_64, pyparted-3.9.5-2.fc21.x86_64 product: Fedora" release: Fedora release 21 (Twenty One) type: anaconda version: Fedora
Created attachment 952222 [details] File: anaconda-tb
Created attachment 952223 [details] File: anaconda.log
Created attachment 952224 [details] File: environ
Created attachment 952226 [details] File: journalctl
Created attachment 952227 [details] File: lsblk_output
Created attachment 952228 [details] File: nmcli_dev_list
Created attachment 952229 [details] File: os_info
Created attachment 952230 [details] File: program.log
Created attachment 952231 [details] File: storage.log
Created attachment 952232 [details] File: ifcfg.log
I propose this bug as beta blocker as it vioalates the criterion: "When using the guided partitioning flow, the installer must be able to: * Complete an installation using any combination of disk configuration options it allows the user to select * Remove existing storage volumes to free up space, at the user's direction and THIS one probably the most: * Reject or disallow invalid disk and volume configurations without crashing."
Discussed at 2014-10-30 Go/No-Go meeting: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-10-30/f21_beta_gono-go_meeting.2014-10-30-17.00.log.txt . This is rejected as a blocker on the basis that it requires multiple trips through the disk selection workflow and an incorrect selection, and can easily be 'worked around' by re-doing the install but picking the right option in the first place. We have a consensus that we're not really on board with the "Reject or disallow invalid disk and volume configurations without crashing." as written, as a Beta criterion, and I'll look at revising that.
I doubt this has anything to do with multiple trips through the storage spoke. Is it reproducible? It looks like something outside of the installer has reactivated one or more logical volumes in fedora-server_dhcp-29-208: 11:33:14,185 INFO program: Running... lvm vgchange -a n --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] filter=["r|/sdc1$|","r|/sdc2$|","r|/sdc3$|"] } fedora-server_dhcp-29-208 11:33:14,221 INFO program: 0 logical volume(s) in volume group "fedora-server_dhcp-29-208" now active 11:33:14,222 DEBUG program: Return code: 0 <snip> 11:35:59,765 INFO program: Running... udevadm settle --timeout=300 11:35:59,787 DEBUG program: Return code: 0 11:35:59,791 INFO program: Running... lvm pvremove --force --force --yes --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] filter=["r|/sdc1$|","r|/sdc2$|","r|/sdc3$|","r|/fedora-server_dhcp-29-208-swap$|","r|/fedora-server_dhcp-29-208-root$|","r|/fedora-server_dhcp-29-208-home$|","r|/fedora-server_dhcp-29-208$|","r|/sdb1$|","r|/sdb$|","r|/sdc$|"] } /dev/sda2 11:35:59,838 INFO program: No device found for PV wrkNXf-xomR-3fhr-B3i0-m7gL-JNrW-4od5qS. 11:35:59,839 INFO program: No device found for PV wrkNXf-xomR-3fhr-B3i0-m7gL-JNrW-4od5qS. 11:35:59,839 INFO program: WARNING: Wiping physical volume label from /dev/sda2 of volume group "fedora-server_dhcp-29-208" 11:35:59,840 INFO program: Can't open /dev/sda2 exclusively - not removing. Mounted filesystem? 11:35:59,840 DEBUG program: Return code: 5
dlehman: in case it helps, we clarified the case a bit in the review meeting. It was a UEFI-native boot of anaconda on a system with an existing MBR-formatted volume. On the first trip through the storage spoke, Petr just chose to delete one existing partition to free up sufficient space for installation. Of course that's not good enough, because we can't do a UEFI-native install to an MBR-formatted volume. Apparently the free-up-space screen was OK with this choice (arguably possibly a bug?) but Peter saw an error/warning condition on the storage spoke when he got back to the hub, so he went into it again, and *this* time chose to delete the entire disk. The spoke completed successfully and there was no warning this time, but the installer crashed during initial partitioning after he kicked off the actual installation. (Still might not actually be what caused the problem, but I thought it was worth providing the more detailed explanation.)
Another user experienced a similar problem: starting installation process, before entering passwords for root and user cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Workstation-x86_64-2 ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 3.17.2-300.fc21.x86_64 other involved packages: python-blivet-0.61.8-1.fc21.noarch, python-libs-2.7.8-5.fc21.x86_64, pyparted-3.9.5-2.fc21.x86_64 package: anaconda-core-21.48.13-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 6 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Tried to reproduce bug 1158533 and bug 1158911. Installed Fedora on two disks (first had /boot and first part of LVM, second had second part of LVM), then booted anaconda again, selected both disks again, "delete all" on reclaim dialog, then changed my mind, unselected first disk (so that only second disk, with LVM, remained for installation), again clicked on "delete all" on reclaim dialog, started installation and this showed up. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-21_T1-x86_64 quiet hashmarkername: anaconda kernel: 3.17.2-300.fc21.x86_64 package: anaconda-21.48.13-1 product: Fedora" reason: IOException: Partition(s) 1 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: Cannot get release name. version: Fedora
I'm seeing exactly the same error. I'm trying to install from the workstation live CD. I have a 750 GB Intel RAID mirror. About 1/2 the disk is a Fedora 20 install, the other half is free space (unpartitioned). The error occurs when I take the most vanilla path possible, allowing the installer to do automatic partitioning (and boy, is it a leap of faith to hit `install' on that one; some way to inspect the partition allocation would be really nice). This is a relatively old system, MSI P55-GD65 motherboard, to my knowledge uefi is definitely not involved. Seems to me this is about as vanilla as it gets, so the notion that this is an exotic error seems misplaced. More information on request, if it'll help (I'll need to bone up on the instructions for exporting information).
Created attachment 971513 [details] anaconda exception report Anaconda exception report to go with comments #17, #18.
I had good backups, so I forged ahead with some (ultimately) destructive experimentation. It appears that the presence of an LVM PV is the problem. The disk had a standard ext4 partition (Fed 20 /boot) and an LVM PV partition (Fed 20 root, home, swap). After quite attempts, with different permutations of disk partition options, I gave the installer the whole disk to work with. It deleted the Fed 20 /boot, but still could not delete the LVM PV. Eventually I deleted the PV using parted from a Fed 21 Live command window. Parted reported the same error (... unable to inform the kernel ...) but offered me the opportunity to ignore the error and deleted the PV. At that point, the installer had a clear disk and worked correctly. From what I observed, David Lehman's suspicions seem likely to be correct. So ... this is no longer a problem for me, as I have a Fedora 21 installation. On the other hand, I was hoping for a more leisurely transition :-)
It won't be as straightforward as simply having an LVM PV, we do many, many install tests that involve overwriting an LVM config. This error message is by its nature kind of generic - whenever someone hits it, we need to figure out what exactly about their disk layout and anaconda's operations on it got to this point. dlehman should hopefully be able to figure something out from the log.
Another user experienced a similar problem: Set up manual partitioning with no LVM (so I can see this disk from my windows partition) and got this error very soon after clicking the button to allow installation. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 3 on /dev/sdb 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: I chose custom partitioning, did it, then proceeded with the installation. Before I could even set the root password, it failed. /dev/sda5 was indeed mounted (I did that in a terminal, to check something before the installation). Perhaps anaconda could fail more gracefully? For example, back in the partitioning spoke, anaconda could check those partitions I'm marking for deletion, and if they are mounted, warn that the installer won't be able to proceed? cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 rd.live.check hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 5 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 21 (Twenty One) version: Fedora
"For example, back in the partitioning spoke, anaconda could check those partitions I'm marking for deletion, and if they are mounted, warn that the installer won't be able to proceed?" What would be the benefit, though? It'd still be broken, only we wouldn't know about it, because no-one would file a crash. The general design of anaconda is that it doesn't go out of its way to avoid crashing, so people file the crash and we get to try and fix it.
> What would be the benefit, though? It'd still be broken, only we wouldn't know about it, because no-one would file a crash. Well, if Anaconda told me it couldn't proceed because the partition was mounted, then I'd just go and unmount it. Then Anaconda could see that, and proceed as usual. It wouldn't crash, it wouldn't make me to redo everything.
Another user experienced a similar problem: After selecting the various installation settings, I clicked on the "Begin Installation" button. I began to enter the root password I wanted to use for this new install, and the error dialog appeared. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-21-x86_64 quiet hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 package: anaconda-21.48.21-1 product: Fedora" reason: IOException: Partition(s) 2 on /dev/md/Volume0_0 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: Cannot get release name. version: Fedora
Another user experienced a similar problem: Installing Fedora 21 on HP Omen; Went through language, keyboard, network, and storage configuration just fine, but when I clicked Begin to start installation it immediately bombs. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=ext4 ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 1 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: After customizing the creation of a partition on an external harddrive I began the installation of Fedora and it automatically gave me this error. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 1 on /dev/sdb 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 21 (Twenty One) version: Fedora
*** Bug 1180913 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: I can't install. Get error every time I begin installation cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition map has no partition map entry! release: Fedora release 21 (Twenty One) version: Fedora
*** Bug 1202813 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Attempting to install F22 KDE to a 16GB SD Card mounted as /dev/sdc. The system is a Samsung NP550P5C laptop with an Intel Core i3 processor and Intel graphics. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-KDE-x86_64-22_B-T5 ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 4.0.0-0.rc4.git0.1.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-blivet-1.0.5-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 package: anaconda-core-22.20.6-1.fc22.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 5 on /dev/sdc 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 22 (Twenty Two) version: Fedora
Another user experienced a similar problem: Not sure. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 2 on /dev/mapper/ddf1_4c53492020202020808627c3000000004711471100001450 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: default Server install selected disk, reclaimed all space, default partitioning. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: inst.repo=http://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC1/Server/armhfp/os/ dnf.rpm.log: Jan 01 00:06:18 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.armv7hl+lpae package: anaconda-22.20.9-1 product: Fedora reason: IOException: Partition(s) 2 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: Cannot get release name. version: 22
in my case the hard drive previously was used in a x86_64 laptop and had a uefi install. I told the installer to delete evrything. when I rebooted and tried again the ESP partition was still intact. but everything else was removed. selecting delete all the second time appears to have succeeded. the gpt partition table was replaced witha msdos one.
Looking at the logs from comment 18, that one looks like an lvm2/udev problem: 20:45:08,176 INFO program: Running... lvm pvs --unit=k --nosuffix --nameprefixes --unquoted --noheadings -opv_name,pv_uuid,pe_start,vg_name,vg_uuid,vg_size,vg_free,vg_extent_size,vg_extent_count,vg_free_count,pv_count --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } global {locking_type=4} 20:45:08,219 INFO program: LVM2_PV_NAME=/dev/sdb3 LVM2_PV_UUID=qUc710-JaQa-r2lx-gY8s-U5Qd-UMXw-rZ5E2k LVM2_PE_START=192.00 LVM2_VG_NAME=vg_spare LVM2_VG_UUID=FjcqlW-lmVM-GycS-MOJo-1bi6-Nuvr-FTzxz5 LVM2_VG_SIZE=120516608.00 LVM2_VG_FREE=0 LVM2_VG_EXTENT_SIZE=4096.00 LVM2_VG_EXTENT_COUNT=29423 LVM2_VG_FREE_COUNT=0 LVM2_PV_COUNT=1 20:45:08,220 INFO program: LVM2_PV_NAME=/dev/sdd2 LVM2_PV_UUID=1dxYgZ-gAEz-c2CF-HEwE-wrwA-dTAo-7NP82Q LVM2_PE_START=1024.00 LVM2_VG_NAME=fedora_zaphod LVM2_VG_UUID=RmAVSb-qsTU-GS2w-2Rfv-EnNo-x1Vz-Vx4fC7 LVM2_VG_SIZE=392163328.00 LVM2_VG_FREE=897024.00 LVM2_VG_EXTENT_SIZE=4096.00 LVM2_VG_EXTENT_COUNT=95743 LVM2_VG_FREE_COUNT=219 LVM2_PV_COUNT=1 20:45:08,220 DEBUG program: Return code: 0 That's lvm telling us, when we ask it for a list of the PVs on the system, that the PVs are sdb3 (instead of /dev/md/Windows_0p3) and sdd2 (instead of /dev/md/Fedora_0p2). It looks like there are a variety of ways this kind of situation can arise. Who knows how many different scenarios would be found if all of the duplicate reports contained logs.
Another user experienced a similar problem: Trying to install Fedora over a non booting version I cannot repair. Want to use the same partitions on a dual boot system and avoid LVM that has screwed me in the past, cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz0 root=live:UUID=F677-0EDD ro rd.live.image quiet rhgb rd.live.check hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 10 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: It happened when I entered the root password setting dialog. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: ro vnc noeject dnf.rpm.log: Apr 15 12:41:16 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.0-0.rc1.git0.1.fc22.ppc64 package: anaconda-22.20.8-1 product: Fedora" reason: IOException: Partition(s) 2 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: Cannot get release name. version: Fedora
Another user experienced a similar problem: I tried to install the Fedora 22 prebeta Live CD (nightly 2015-04-19). After manual partioning it began to install the system and asked the root password. During click to the root password it occured the crash. The boot layout is: / on sda (90GB); swap on sda (5GB). An USB harddisk is plugged in but not used for installation. The Laptop is a Sony Vaio VGN-FS415S. I used the partitions before I began the installation. I didn't unmount them. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-22-20150419 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 nomodeset hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.i686 other involved packages: python-blivet-1.0.7-1.fc22.noarch, pyparted-3.10.3-1.fc22.i686, python-libs-2.7.9-5.fc22.i686 package: anaconda-core-22.20.9-1.fc22.i686 packaging.log: product: Fedora reason: IOException: Partition(s) 5 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 22 (Twenty Two) version: 22
*** Bug 1214039 has been marked as a duplicate of this bug. ***
(In reply to Robin Laing from comment #36) > Another user experienced a similar problem: > > Trying to install Fedora over a non booting version I cannot repair. > > Want to use the same partitions on a dual boot system and avoid LVM that has > screwed me in the past, Under the partitioning scheme used, this should have been a swap partition. It may have occurred that the boundary ran into a hidden Windows partition on this drive that was Partition 11. Anaconda may have not set the boundaries correctly to be placed into the position that it was assigned. This was one of many install crashes on this date trying to install Fedora. I cannot remember if this was the Live Workstation or the KDE Live spin.
(In reply to Rolle from comment #38) > I used the partitions before I began the installation. I didn't unmount them. You have to unmount them before running the installer.
In my case, shutting the computer down should unmount the partitions.
(In reply to David Lehman from comment #41) > (In reply to Rolle from comment #38) > > I used the partitions before I began the installation. I didn't unmount them. > > You have to unmount them before running the installer. OK. I understand that. But it isn't very user friendly that the installation process interupts with a crash. The user should be informed about this problem. Maybe a solution could be: 1. Is it better to unmount the needed partitions automatically? Maybe with a warning dialog before? 2. A list of mounted partitions could be presented with each entry has an unmount-button. The required partitions to unmount could be marked. So the user could easily unmount the partitions and then the installtion process goes on?
*** Bug 1152581 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Just Clicking "Begin Installation" - as soon as the page showing I need to set a root password and create a user is displayed, the progress bar at the bottom moves a variable amount and the page becomes unresponsive - this 'error' alert then appears. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 2 on /dev/mapper/pdc_jafbbijhh 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: I just did a fresh install of Fedora 21 on new disk drives with hardware RAID 1. I let it default the partitioning and didn't like it after I rebooted. I was going to install again, but I first tried to resize the logical volumes after booting the install media. The lvreduce ran for several hours (5-6) before I canceled it and just used the installer GUI to delete the existing setup, create a new default, change the sizes to what I wanted. I then started the install and selected my package groups. It appeared to be working, so I went to work. The error displayed 6 hours later. It appears to be some sort of LVM failure, but I couldn't figure out exactly what the problem was. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-21-x86_64 quiet hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 package: anaconda-21.48.21-1 product: Fedora" reason: IOException: Partition(s) 2 on /dev/md/Volume0_0 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: Cannot get release name. version: Fedora
Another user experienced a similar problem: I was trying to install Fedora 22 with normal configuration and It's crash when I saw "Setting yp the installation environment" when I tried with update version "anaconda" but still crashed. Thank you cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:LABEL=UUI NULL=Fedora-Live-WS-x86_64-22_B-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-blivet-1.0.7-1.fc22.noarch, python-libs-2.7.9-5.fc22.x86_64 package: anaconda-core-22.20.12-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 2 on /dev/sdb 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: When I installed Fedora 21 via LIve CD, i encountered this problem cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=fedora21LiveCD rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.19.3-200.fc21.x86_64 other involved packages: python-blivet-0.61.15-1.fc21.noarch, pyparted-3.9.5-2.fc21.x86_64, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: IOException: Partition(s) 2 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 21 (Twenty One) version: Fedora
Another user experienced a similar problem: kickstart install addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/boot/vmlinuz_koan ks=http://cobbler.cora.nwra.com/cblr/svc/op/ks/system/amakihi ksdevice=link kssendmac lang= text hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 package: anaconda-21.48.21-1 product: Fedora" reason: IOException: Partition(s) 8 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: Cannot get release name. version: Fedora
Another user experienced a similar problem: I set a custom partitioning scheme and then continued with the install. Then as I was setting my password I got the error message "An unknown error has occured". cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 6 on /dev/sdb 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 22 (Twenty Two) version: 22
I got the same error when trying to install Fedora 22: "IOException: Partition(s) [*] on /dev/sd[*] 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." The problem was that I told the installer when I was setting up the custom partitioning to reformat the swap partition. When I proceeded with the installation, anaconda tried to format the swap partition but couldn't because the live OS was using it! To get around this (after rebooting the live CD when I finished troubleshooting so that I would have a fresh environment), I opened a terminal and ran "swapoff -av" as root. Then I started anaconda from the Gnome Activities screen, and all went well. I think that the live CD should not use the swap partition by default.
Nice find. Also, it may be possible to do a check if the swap partition is marked for formatting and have Anaconda turn it off. Anaconda should be checking to see if any partition is is use and flag an error instead of just crashing. Maybe a message to ask to confirm that this partition in use is actually supposed to be deleted.
Another user experienced a similar problem: Installation from live USB stick, manual partitioning. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22-3 ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 1, 2, 3, 4, 5 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 22 (Twenty Two) version: 22
There is little I can do with all these duplicate reports that do not include logs. I know that anaconda is vulnerable to users activating things while it is running. Don't do that. Apparently something in the system was automatically activating swap devices at some point. I don't know if that is still happening or not. It shouldn't be happening during OS installation. I think if the swap were active when anaconda started we would simply deactivate it. Anyone who experiences this bug, please attach the logs if you would like your issue to be addressed.
(In reply to David Lehman from comment #54) > Apparently something in the system was automatically activating swap devices > at some point. I don't know if that is still happening or not. Think that part is done on livecd's by default action "Enabling swap partition \$s" swapon \$s https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-base.ks
Another user experienced a similar problem: I am running fedora 22 (robotics) installation. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Robo-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 rd.live.check hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 9 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: I launched a Fedora 22-3 KDE Spin LiveUSB, created with rufus 2.2 in order to install the mentioned system. Connected to Wi-Fi, selected my time zone and created 3 mount points, 1 general, 1 swap and 1 encrypted. All three LVM. I've created a very lond password, over 32 characters long, and it may have exceeded the maximum amount of charecters. Except for that, I did nothing else irregular. I don't know if it can be reproduced, but now I will try another time and let you know if it can. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=FEDORA-LIVE rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 1 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: I selectet the usb-stick, where my live-syste is installed as installation target cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 1 on /dev/sdb 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: Dans la 2em etape de l'installation de fedora 22 sur mon ordinateur portable , c'est a dire la configuration du mot de passe administrateur , j'ai obtenu l'erreur suivant : An unknown error has occured -intf.storage.iscsi.instance , containing members: --intf.storage.iscsi.initiatorSet: False - - - cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Xfce-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 6 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: Keep getting an error message whenever I try to install. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.i686 other involved packages: python-libs-2.7.9-6.fc22.i686, python-blivet-1.0.9-1.fc22.noarch, pyparted-3.10.3-1.fc22.i686 package: anaconda-core-22.20.13-1.fc22.i686 packaging.log: product: Fedora reason: IOException: Partition(s) 1 on /dev/sdb 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: bug au niveau du partionement cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Xfce-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: Problem while installation cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: pyparted-3.10.3-1.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: IOException: Partition(s) 1 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 22 (Twenty Two) version: 22
Another user experienced a similar problem: During installation the install stopped with "This program has encountered an unknown error. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet dnf.rpm.log: Oct 19 14:39:10 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 package: anaconda-22.20.13-1 product: Fedora reason: IOException: Partition(s) 2 on /dev/md/Volume0_0 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: Cannot get release name. version: 22
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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.
Not sure if this bug is just collecting unrelated issues that hit the same error, but we have dupes up to 22, so...
Anyone who has hit this on F22, please attach the logs to this report. Otherwise I have no way of seeing what exactly has happened.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.