Bug 573467
| Summary: | SystemError: (2, None) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Miller <cjm> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | anaconda-maint-list, hdegoede, jonathan, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | anaconda_trace_hash:87652f6e3c3a74ba459b5dca45f2f0eb519f59bef33c2b5bd3f84a56c55a0115 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-11-08 20:57:08 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 400061 [details]
Attached traceback automatically from anaconda.
Could you provide some info on what sort of install you were doing please ? Looking at the logs it seems that: 1) you were doing a kickstart install 2) stag2 was living on a harddisk partition 3) The install completed successfully, but traced back when you pressed reboot at the end of the installation Is this correct ? Could you provide some more details about the kind of install (upgrade or install, etc.) ? 1) Yes. 2) Yes. 3) No. The Install fails very early in the cycle. I have done so many that I have lost track, but for a short time, I have a complete setup and I am willing to run diagnostic versions or perform experiments. And I can boast a nearly 100% repeatability. Don't delay, order your traceback today! :^) This is an unusual install because I have the iso on the harddrive, not on optical media. I am not entirely sure about precisely what boots what, but I think my MBR loads EXTLinux from the boot sector on the partition, which then reads the config file, offers me a menu and when I select "Install", boots ISOlinux with the following stanza: /Fedora-12/isolinux/vmlinuz initrd=/Fedora-12/isolinux/initrd.img ro ks=hd:/dev/sdb1:/Fedora12/ks.cfg headless vnc Are you doing something unusual where you re-use an existing / filesystem but without mounting it? I see a lot of references to packages already existing in your log files. When you hit the traceback, can you jump over to tty2, see what's mounted, and attach that to this bug report? Also, you don't have a shell active in /mnt/sysimage/dev from doing some earlier investigation on tty2 do you? This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** This bug has been marked as a duplicate of bug 548592 *** |
The following was filed automatically by anaconda: anaconda 12.46 exception report Traceback (most recent call first): File "/usr/lib/anaconda/isys.py", line 173, in umount rc = _isys.umount(what) File "/usr/lib/anaconda/storage/formats/fs.py", line 600, in unmount rc = isys.umount(self._mountpoint, removeDir = False) File "/usr/lib/anaconda/storage/formats/fs.py", line 790, in teardown return self.unmount(*args, **kwargs) File "/usr/lib/anaconda/storage/__init__.py", line 1855, in umountFilesystems device.format.teardown() File "/usr/lib/anaconda/storage/__init__.py", line 1052, in umountFilesystems self.fsset.umountFilesystems(ignoreErrors=ignoreErrors, swapoff=swapoff) File "/usr/lib/anaconda/packages.py", line 90, in turnOnFilesystems anaconda.id.storage.umountFilesystems() File "/usr/lib/anaconda/dispatch.py", line 200, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 119, in gotoPrev self.moveStep() File "/usr/lib/anaconda/gui.py", line 1186, in prevClicked self.anaconda.dispatch.gotoPrev() File "/usr/lib/anaconda/iw/progress_gui.py", line 114, in getScreen self.intf.icw.prevClicked() File "/usr/lib/anaconda/gui.py", line 1279, in setScreen new_screen = self.currentWindow.getScreen(anaconda) File "/usr/lib/anaconda/gui.py", line 1196, in nextClicked self.setScreen () File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1216, in handleRenderCallback self.currentWindow.renderCallback() SystemError: (2, None)