Hide Forgot
The following was filed automatically by anaconda: anaconda 15.20.1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 261, in writeGrubConf f = open(cf, "w+") File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 227, in writeGrub cfPath) File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 528, in write not self.useGrubVal) File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 217, in writeBootloader kernelList, otherList, defaultDev) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext self.moveStep() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1278, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 2] No such file or directory: '/mnt/sysimage/boot/grub/grub.conf'
Created attachment 481147 [details] Attached traceback automatically from anaconda.
Seen while testing https://fedoraproject.org/wiki/QA/TestCases/PartitioningExt4OnNativeDevice
Are you doing something strange like installing over top an already installed system? There's some messages like this that are puzzling: [2011-02-26 09:15:40,860] WARN : Package 1:grub-0.97-71.fc15.i686 already installed and latest version
I don't remember exactly what the conditions were, but yes, I was doing repeated installs in a test VM and am pretty sure that was the case. I also saw another instance where it claimed there were file conflicts and wouldn't start installing packages (even though this was a fresh RC2 DVD install with no external repos enabled), but that wasn't reproducible either after I started with a fresh VM.
We really shouldn't be allowing not formatting /. I think there's already a bug for that, though I can't find it offhand.
Created attachment 493069 [details] Attached traceback automatically from anaconda.
Wait, what's wrong with not formatting /? I have exactly a situation where I need to save / because that's where /home is, and I need to do an install because my previous attempt at an install failed and left the system in a mess. Surely that's not uncommon???
With an unformatted /, you're going to have all the old libraries and config files laying around. None of the old packages' contents will be removed, but I think the RPM db entries will be screwed up by the reinstall. So you'll have a lot of stuff laying around cluttering the system that you can't really do anything about. Then, the config files are going to create problems during installation. Really, it's just best to start with a fresh system. It's unfortunate about the /home problem, but that's why you should make it as a separate partition or LV. It's true we did not used to set that up in the default partitioning but that's really only because we were busy arguing about how best to divy up the space. You will need to do a backup.