Created attachment 1168234 [details] log files found in /tmp related to the issue I was trying the pre-release of LXDE 24 Spin in my 64bit machine, it boots without any issues, but when I try to install to hard disk, it halts at the storage device probing step. I tried waiting for like 20 minutes but nothing more happens. In the first attempt I created the live image with unetbootng, then I tried with liveusb-creator as well, but I still get the same issue. I have attached the log files found in /tmp for reference.
Created attachment 1168515 [details] anaconda.log (extracted from tarball)
Created attachment 1168516 [details] storage.log (extracted from tarball)
Created attachment 1168518 [details] program.log (extracted from tarball)
you might just have to wait longer, but I'm not sure at present whether it's expected that this fsck should be run or not. From the versions in the logs, you tried with F24 Beta - could you try with Final RC2 and see if it's any better? you can find download links at https://fedoraproject.org/wiki/Test_Results:Fedora_24_RC_1.2_Installation . Thanks!
I tired with [1], still I get the same issue. [1] https://kojipkgs.fedoraproject.org/compose/24/Fedora-24-20160614.0/compose/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-24-1.2.iso
There's no reason that e2fsck should run for 20 minutes with no output. This might be the deadlock that was fixed by anaconda commit f4bcb317. Is the GUI responsive after a minute or so of waiting?
The GUI is stuck for a while, but can interact with after a while, but the response is not so smooth as before. Once I terminate anaconda, the rest of the applications work fine.
Now that Fedora 24 is released, I will check with the released LXDF live CD and update with the results.
Ahh seems it is the same RC I tried earlier (the iso file name is the same). So no point of testing again, Do we have a workaround for this issue?
(In reply to Kalpa Welivitigoda from comment #7) > The GUI is stuck for a while, but can interact with after a while, but the > response is not so smooth as before. > > Once I terminate anaconda, the rest of the applications work fine. I mean the anaconda GUI specifically. Is it responsive or is it frozen?
It's frozen.
Try passing this to liveinst on the command line: inst.updates=https://dlehman.fedorapeople.org/updates-1346674.0.img Please let me know how it goes.
$liveinst inst.updates=https://dlehman.fedorapeople.org/updates-1346674.0.img % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4025 100 4025 0 0 1425 0 0:00:02 0:00:02 --:--:-- 1425 25 blocks Starting installer, one moment... Traceback (most recent call last): File "/sbin/anaconda", line 665, in <module> from pyanaconda.addons import collect_addon_paths File "/tmp/updates/pyanaconda/addons.py", line 28, in <module> from pyanaconda.progress import progress_message File "/tmp/updates/pyanaconda/progress.py", line 28, in <module> from pyanaconda.queuefactory import QueueFactory File "/tmp/updates/pyanaconda/queuefactory.py", line 22, in <module> from pyanaconda.iutil import lowerASCII, upperASCII File "/tmp/updates/pyanaconda/iutil.py", line 59, in <module> from pyanaconda.anaconda_log import program_log_lock File "/tmp/updates/pyanaconda/anaconda_log.py", line 31, in <module> import wrapt ImportError: No module named 'wrapt' I tried installing wrapt with $pip install wrapt it got installed but I see the same error when I retry liveinst. Further as per the help of liveinst I tried, $liveinst updates=https://dlehman.fedorapeople.org/updates-1346674.0.img still I got the same error, No module named 'wrapt'
Try installing it via dnf: dnf install python3-wrapt
It worked and I could successfully install Fedora 24 LXDE spin. It took around 10 minutes to complete storage device probing though.
I'm glad you were able to get it installed, but that sounds like a really long time to detect storage. If you have the logs (/var/log/anaconda/*.log) I would be interested to see what took so long.
I don't have the logs now, I will try starting with the live image again and get the logs.
The logs get copied into /var/log/anaconda/ on your installed system, so you should still have them.
Created attachment 1173213 [details] anaconda.log after successful installation
Created attachment 1173214 [details] storage.log after successful installation
Created attachment 1173215 [details] program.log after successful installation
I didn't new that the logs are still preserved. anaconda.log, storage.log and program.log files are attached. Please let me know if you need more log files.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.