Description of problem: Started installation in graphics safe mode and went to install using anaconda. Bug happens after clicking "Continue" in the very first screen. Version-Release number of selected component: anaconda-core-26.21.11-1.fc26.x86_64 The following was filed automatically by anaconda: anaconda 26.21.11-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/livepayload.py", line 84, in setup raise PayloadInstallError("Failed to mount the install tree") File "/usr/lib64/python3.6/site-packages/pyanaconda/payload/__init__.py", line 1432, in _runThread payload.setup(storage, instClass) File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self) pyanaconda.payload.PayloadInstallError: Failed to mount the install tree Additional info: addons: com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=FEDORA-WS-L rd.live.image nomodeset quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 other involved packages: system-python-libs-3.6.1-8.fc26.x86_64 product: Fedora release: Fedora release 26 (Twenty Six) type: anaconda version: 26
Created attachment 1296547 [details] File: anaconda-tb
Created attachment 1296548 [details] File: anaconda.log
Created attachment 1296549 [details] File: environ
Created attachment 1296550 [details] File: journalctl
Created attachment 1296551 [details] File: lsblk_output
Created attachment 1296552 [details] File: nmcli_dev_list
Created attachment 1296553 [details] File: os_info
Created attachment 1296554 [details] File: program.log
Created attachment 1296555 [details] File: storage.log
Created attachment 1296556 [details] File: ifcfg.log
*** Bug 1471408 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Start fedora installation from desktop icon Select English (United States) in language selector addons: com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-KDE-Live-26-1-5 rd.live.image quiet hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 other involved packages: system-python-libs-3.6.1-8.fc26.x86_64 package: anaconda-core-26.21.11-1.fc26.x86_64 packaging.log: product: Fedora reason: pyanaconda.payload.PayloadInstallError: Failed to mount the install tree release: Fedora release 26 (Twenty Six) version: 26
seems to happen as an exmaple select english as the language and select english india for the keybaord
Similar problem has been detected: After starting the installation procedure for Fedora 26 from the Live Session (booting from USB), it hung for a very long time after clicking "Continue" on the lanuage screen. I'm not exactly sure how long since I left it and took the dog for a walk. But once I returned there was the python exception stating it could not mount the install tree. I'm not sure if it is related or not, but I did notice in the journal while it was hanging it, that fsck was being run on some of the larger volume I have on my disk. So perhaps it was running the checks, and just taking a long time to complete before finally timing out? It does appear that the "Installation Summary" screen is now up, and I will attempt to proceed with the installation to see if the issue was transient. addons: com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-26-1-5 rd.live.image quiet hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 other involved packages: system-python-libs-3.6.1-8.fc26.x86_64 package: anaconda-core-26.21.11-1.fc26.x86_64 packaging.log: product: Fedora reason: pyanaconda.payload.PayloadInstallError: Failed to mount the install tree release: Fedora release 26 (Twenty Six) version: 26
(In reply to Troy Curtis from comment #14) > Similar problem has been detected: > > After starting the installation procedure for Fedora 26 from the Live > Session (booting from USB), it hung for a very long time after clicking > "Continue" on the lanuage screen. I'm not exactly sure how long since I > left it and took the dog for a walk. But once I returned there was the > python exception stating it could not mount the install tree. > > I'm not sure if it is related or not, but I did notice in the journal while > it was hanging it, that fsck was being run on some of the larger volume I > have on my disk. So perhaps it was running the checks, and just taking a > long time to complete before finally timing out? > > It does appear that the "Installation Summary" screen is now up, and I will > attempt to proceed with the installation to see if the issue was transient. > > addons: com_redhat_kdump > cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst > --method=livecd:///dev/mapper/live-base > cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz > root=live:CDLABEL=Fedora-WS-Live-26-1-5 rd.live.image quiet > hashmarkername: anaconda > kernel: 4.11.8-300.fc26.x86_64 > other involved packages: system-python-libs-3.6.1-8.fc26.x86_64 > package: anaconda-core-26.21.11-1.fc26.x86_64 > packaging.log: > product: Fedora > reason: pyanaconda.payload.PayloadInstallError: Failed to mount the > install tree > release: Fedora release 26 (Twenty Six) > version: 26 Quick follow up: While the "Installation Summary" seemed to be displayed, it was not accessible, presumably since the underlying system had the attached python exception.
*** Bug 1456207 has been marked as a duplicate of this bug. ***
*** Bug 1403980 has been marked as a duplicate of this bug. ***
FYI - bug https://bugzilla.redhat.com/show_bug.cgi?id=1403980 was opened last year (2016) so really this bug is a duplicate of that one. That ticket DOES show some potential workarounds that MAY help some users.
Similar problem has been detected: tal vez porque elimine una particion con Gnome-Disk- Util.. estando con el instalador pero cerre el instalador y lo voli a abrir addons: com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-26-1-5 rd.live.image rd.live.check quiet hashmarkername: anaconda kernel: 4.11.8-300.fc26.x86_64 other involved packages: system-python-libs-3.6.1-8.fc26.x86_64 package: anaconda-core-26.21.11-1.fc26.x86_64 packaging.log: product: Fedora reason: pyanaconda.payload.PayloadInstallError: Failed to mount the install tree release: Fedora release 26 (Twenty Six) version: 26
*** Bug 1507211 has been marked as a duplicate of this bug. ***
Has there been any progress towards fixing the anaconda bug with LVM on top of an IMSM RAID-1? As noted in the #1403980 (which was closed as a duplicate), there is what SEEMS like a big clue in the error message "Not using lvmetad because duplicate PVs were found". Also noted in that ticket was a WORKAROUND (at least for F25 of selecting a SERVER install).
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.