Description of problem: HTTP installation initialized by Grub Legacy. No idea why this happened. I've initialized probably at least 40 installation attempts in past 30 hours.I'm guessing these early crashes are happening only slightly less than half the time. The following was filed automatically by anaconda: anaconda 19.30.3-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 626, in unmount raise FSError("umount failed") File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 792, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 745, in _preTeardown self.format.teardown() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 757, in teardown if not self._preTeardown(recursive=recursive): File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 2803, in findExistingInstallations device.teardown() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 420, in reset self.roots = findExistingInstallations(self.devicetree) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 140, in storageInitialize storage.reset() File "/usr/lib/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 168, in run threading.Thread.run(self, *args, **kwargs) FSError: umount failed Version-Release number of selected component: anaconda-19.30.3-1 Additional info: reporter: libreport-2.1.4 cmdline: /usr/bin/python /sbin/anaconda cmdline_file: stage2=hd:/dev/sda13:/squashfs.img repo=http://alt.fedoraproject.org/pub/alt/stage/19-TC3/Fedora/i386/os selinux=0 ip=192.168.0.62::192.168.0.50:255.255.255.0:kt880::none nameserver=192.168.0.50 video=1152x864 vga=794 noapic resolution='1280x960' splash=verbose rd.luks=0 rd.md=0 rd.dm=0 nousb nofirewire noipv6 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.4-301.fc19.i686 product: Fedora release: Cannot get release name. type: anaconda version: 19 Truncated backtrace: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 168, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 140, in storageInitialize storage.reset() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 420, in reset self.roots = findExistingInstallations(self.devicetree) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 2803, in findExistingInstallations device.teardown() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 757, in teardown if not self._preTeardown(recursive=recursive): File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 745, in _preTeardown self.format.teardown() File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 792, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 626, in unmount raise FSError("umount failed") FSError: umount failed
Created attachment 761157 [details] File: anaconda-tb
Created attachment 761158 [details] File: anaconda.log
Created attachment 761159 [details] File: backtrace
Created attachment 761160 [details] File: environ
Created attachment 761161 [details] File: ifcfg.log
Created attachment 761162 [details] File: lsblk_output
Created attachment 761163 [details] File: nmcli_dev_list
Created attachment 761164 [details] File: packaging.log
Created attachment 761165 [details] File: program.log
Created attachment 761166 [details] File: storage.log
Created attachment 761167 [details] File: syslog
I've added some debugging (and a udev settle) in 19.30.7, if you can get it to fail with TC4 (when it is ready) and grab the program.log with the output from lsof that would be great.
I tried using http://alt.fedoraproject.org/pub/alt/anaconda/anaconda-19.30.7-boot.iso but this bug is from a 32 bit system, and that iso appears to be only for 64 bit.
Created attachment 766273 [details] program.log from RC2
Created attachment 766274 [details] RC2 output from lsof No improvement as of F19RC2.
*** This bug has been marked as a duplicate of bug 968833 ***