Description of problem: The most recent yum update process failed with a gobbledegook unfriendly error that I can't fathom and don't know how to fix. Could you please advise me what to do to remedy the problem? Thanks. Version-Release number of selected component (if applicable): anaconda-yum-plugins-1.0-5.fc12.noarch How reproducible: 100% Steps to Reproduce: 1. Try to update the system 2. 3. Actual results: anaconda 14.22 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1747, in parseFSTab raise Exception("fstab entry %s is malformed: %s" % (devspec, e)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1342, in mountExistingSystem fsset.parseFSTab() File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 229, in upgradeMountFilesystems mountExistingSystem(anaconda, anaconda.upgradeRoot[0], allowDirty = 0) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 235, in currentStep self.gotoNext() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1223, in setScreen (step, anaconda) = self.anaconda.dispatch.currentStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1411, in setup_window self.setScreen() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1425, in run self.setup_window(False) File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1154, in run self.icw.run() File "/usr/bin/anaconda", line 901, in <module> anaconda.intf.run(anaconda) Exception: fstab entry UUID=78493b9d-82ff-435c-8c5b-c0e5d4626bfa is malformed: scanned format (ext3) differs from fstab format (ext2) Local variables in innermost frame: comment: pound: e: scanned format (ext3) differs from fstab format (ext2) dump: 1 devspec: UUID=78493b9d-82ff-435c-8c5b-c0e5d4626bfa I'm then invited save, debug or exit. After typing exit I see: running anaconda 14.22 the fedora system installer 20:56:24 starting graphical instillation install[sic] exited abnormally [1/1] the system will be rebooted when you press ctl-c or ctl-alt-del Expected results: System should update correctly. Additional info:
Make sure your /etc/fstab on the system you are installing references the same filesystem types as are actually on your drives. In particular, it looks like you have one partition that has ext3 on it, but fstab has ext2 down. *** This bug has been marked as a duplicate of bug 577260 ***
As you can tell, /etc/fstab was generated automatically by anaconda. Therefore there is a bug in the way anaconda generates /etc/fstab if it generates one that later it can't use. # /etc/fstab # Created by anaconda on Sun Jul 11 17:12:17 2010 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=14c6136c-6281-4ae9-bdd2-d589ee35ec00 / ext3 noatime 1 1 UUID=78493b9d-82ff-435c-8c5b-c0e5d4626bfa /tmp ext2 noatime 1 2 UUID=de4c666e-12ce-461e-9dd6-b1d615503864 swap swap defaults 0 0 UUID=78a3c714-7d12-4b35-8f4a-6160862f383a swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/sda2 /mnt/windows ntfs-3g defaults,umask=0,nls-utf0 /dev/sdb1 /mnt/windows2 ntfs-3g defaults,umask=0,nls-utf0 gateway:/ /mnt/gateway nfs intr 0 0 gateway:/home /mnt/gateway/home nfs intr 0 0 gateway:/var /mnt/gateway/var nfs intr 0 0
I have manually changed the entry and now the machine hangs at the 'doing a dependency check'. There is no disc activity, indeed no sign of any life now
Re-opening. Was closed by maintainer not by reporter. Situation has gone from irritation (I could boot to an old system) to an unusable system, by following advice. Maintainer then closed without even checking if advice helped.
Bugzilla is not a support system, and individual bugs are used to track individual problems. You had a very specific, narrow problem given by the traceback above. That is solved by the bug I duped this one to. You are now seeing a completely different, likely unrelated problem. You need to open a new bug report, complete with log files, so we can track down your new problem. Reusing a bug for every single problem you encounter makes it impossible to track resolution of individual things. Lastly, maintainers can close bugs whenever they deem fit. Please don't presume to tell me what I may and may not do, or what I have and have not tried. *** This bug has been marked as a duplicate of bug 577260 ***