Red Hat Bugzilla – Bug 438446
Last modified: 2008-03-29 18:57:30 EDT
anaconda 184.108.40.206 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/isys.py", line 263, in lochangefd
File "/usr/lib/anaconda/yuminstall.py", line 362, in systemMounted
File "/usr/lib/anaconda/yuminstall.py", line 1301, in doPreInstall
if self.ayum.systemMounted (anaconda.id.fsset, anaconda.rootPath):
File "/usr/lib/anaconda/backend.py", line 203, in doPreInstall
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 131, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1246, in nextClicked
File "/usr/lib/anaconda/iw/progress_gui.py", line 80, in renderCallback
File "/usr/lib/anaconda/gui.py", line 1267, in handleRenderCallback
SystemError: (22, 'Invalid argument')
Created attachment 298753 [details]
This is without my patch in bug #438377, btw -- I'm booting from the CD this time.
19:42:06 DEBUG : isys.py:mount()- going to mount /dev/VolGroup00/LogVol00 on
19:42:10 DEBUG : isys.py:mount()- going to mount /dev/VolGroup00/LogVol01 on
19:42:10 DEBUG : isys.py:mount()- going to mount /dev/ps3da1 on /mnt/sysimage
In my BZ438646 I had the same issue, /mnt/sysimage double mounted. At least this
one found VolGroup00 to mount
This started happening a little after 6pm, on a machine which had been working
fine earlier (I'd started another install, which had died when I unplugged the
keyboard due to the evdev thing).
My daily rawhide rsync kicks in at 6pm.
This went away when I burned the new boot.iso and booted from that instead of
the previous day's version.
Those three facts are probably enough for us to close it without further
Closing on the basis of comment #4.