Description of problem: 1. USB stick target contains a previous Fedora 25 installation (auto part) installation. 2. Use auto part, reclaim space, Delete All, to do a new installation. 3. Click Done at Installation Destination, returned to the hub UI and then crash before Begin Installation changes from gray to blue. Regression: if the USB stick is wipefs'd first, autopart succeeds and the resulting installation is bootable, which is the state the stick was in at step 1 above. Version-Release number of selected component: anaconda-core-25.20.4-1.fc25.x86_64 The following was filed automatically by anaconda: anaconda 25.20.4-1 exception report Traceback (most recent call first): File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 706, in _set_format raise errors.DeviceError("cannot replace active format", self.name) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 751, in <lambda> lambda d, f: d._set_format(f), File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/deviceaction.py", line 687, in apply self.device.format = None File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/actionlist.py", line 75, in add action.apply() File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 243, in recursive_remove self.actions.add(ActionDestroyFormat(leaf)) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 611, in recursive_remove self.devicetree.recursive_remove(device) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 425, in _recursive_remove self.storage.recursive_remove(device) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 447, in _scheduleActions self._recursive_remove(device) blivet.errors.DeviceError: ('cannot replace active format', 'sdc1') Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-25-20161008-n-0 rd.live.image quiet elevator=noop executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.0-0.rc7.git0.1.fc25.x86_64 other involved packages: anaconda-gui-25.20.4-1.fc25.x86_64, python3-blivet-2.1.6-1.fc25.noarch product: Fedora release: Fedora release 25 (Twenty Five) type: anaconda version: 25
Created attachment 1209429 [details] File: anaconda-tb
Created attachment 1209430 [details] File: anaconda.log
Created attachment 1209431 [details] File: environ
Created attachment 1209432 [details] File: journalctl
Created attachment 1209433 [details] File: lsblk_output
Created attachment 1209434 [details] File: lvm.log
Created attachment 1209435 [details] File: nmcli_dev_list
Created attachment 1209436 [details] File: os_info
Created attachment 1209437 [details] File: program.log
Created attachment 1209438 [details] File: storage.log
Created attachment 1209439 [details] File: ifcfg.log
Proposed as a Blocker for 25-final by Fedora user chrismurphy using the blocker tracking app because: Not sure which one is better, but if installing to USB sticks is invalid then it shouldn't crash and they also shouldn't be offered as an installation destination. If USB sticks are a valid destination, then installation should succeed. Beta criterion: Reject or disallow invalid disk and volume configurations without crashing. Final criterion: The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.
Bug 1371661 - no boot possible from 64GB usb 3.0 flash medium This bug describes the situation on my Acer E15 E5-571G, EFI, Win 8.1 on the internal disk. I can not install F25 Alpha, Beta, also when I reset the 64GB 3.0 USB flash medium with Media Writer (restore function, followed by Gparted, to make the flash medium generally usable again), I found now way to install F25, whether automatic partitioning with reclaim space nor on an other offered way. Possibly this additional info is helpful to solve this problem.
I also have seen this using a mediawriter USB of f25 workstation beta 1.1: Installation halted after restore disk step with error message I was trying to install to a usb external HD with a previous install of f25 workstation beta 1.1. anaconda was confused and could not discriminate between the booted live usb and the external usb HD. A warning popped up saying install could not proceed. Install worked after I used another computer to format the usb external HD with gnome disks and retried install.
Does anyone know what has it mounted? 22:19:28,620 INFO program: `-sdc1 209715200 root disk brw-rw---- `-sdc1 hfsplus Linux HFS+ ESP c7f20a48-bc9b-33dc-a1ef-4e14185f5be6 /run/media/liveuser/Linux HFS+ ESP
That's an HFS+ volume being used as an EFI system partition because it's Apple hardware.
Chris: for you, did this only start happening with 25.20.4-1.fc25 ?
Discussed during the 2016-010-17 blocker review meeting: [1] The decision to classify this bug as an "AcceptedBlocker" was made as it does violate the criteria, however we're aware that the Anaconda team may differ in opinion on classification and we are open to their suggestion either as a comment here or at next weeks meeting. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-10-17/f25-blocker-review.2016-10-17-16.02.txt
The problem doesn't occur with netinstall, Fedora-Workstation-netinst-x86_64-25-20161017.n.0.iso. The problem does occur with F24 live, Fedora-Workstation-Live-x86_64-24-1.2.iso. Abrt sends me to duplicate bug 1381757, parent bug 1330820.
Hi, by case I tried to install F25 Beta in legacy mode on an 64GB flash medium. And surprise it works. This means Anaconda problem when installing F25 on an USB flash medium in EFI mode, but in Legacy mode ok. I run an Acer laptop with Win 8.1 on the internal disk. I think this is good news to find a way to solve this EFI - Anaconda problem. Kind regards (this a copy of a thread in the test lists)
Hi Richard, this is strange. I am now in F25 EFI on an 32GB USB 3.0 flash medium. I have made the following tests with the 64GB USB 3.0 flash medium (both 32GB and 64GB are Sandisk Ultra) Legacy mode: F25 and F24 installation ok EFI mode: F25 to F22 dracut error, no installation possible on the 64GB stick and F25 installation ok on the 32GB stick What is confusing for me with F25 Alpha I tried to install on an external Pata disk (some hundred GB) connected with an usb adapter (I use always used internal disks from ebay - one of my hobbies is collecting TV films, a disk space consuming job), there also no "EFI installation" was possible. I need now an other TB disk for my hobby, and will it first use for an F25 installation test, but this will take some days to get it. Strange results, the 64GB stick should be ok, because the "Legacy installation" works. I copy this mail to the 2 Bug reports related to Anaconda. Kind regards Joerg
This has a workaround (non-live installs) and this existed in F24. This is also not a supported use case. This isn't a blocker.
Discussed during the 2016-10-24 blocker review meeting: [1] The decision to reclassify this bug as a RejectedBlocker and was made per the Anaconda Team's input as well as the conditionality of this bug. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-10-24/f25-blocker-review.2016-10-24-16.01.txt
*** Bug 1426877 has been marked as a duplicate of this bug. ***
*** Bug 1459595 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.