Summary: | GLI fails, unable to emerge grub-> EmergePackageError :FATAL: emerge: Could not emerge sys-boot/grub-0.96-r2 | ||
---|---|---|---|
Product: | Gentoo Release Media | Reporter: | Dan Delgado <dandelgado> |
Component: | Installer | Assignee: | Gentoo Linux Installer <gli-bugs> |
Status: | RESOLVED CANTFIX | ||
Severity: | critical | CC: | synergy6 |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
install profile from tmp
install log from var/log |
Description
Dan Delgado
2006-05-03 18:27:23 UTC
Created attachment 86101 [details]
install profile from tmp
Created attachment 86102 [details]
install log from var/log
I'm sorry, this is my first bug report. All the text I thought I entered did not appear. Attached are the 2 files as requested in the error report. Basically, the GLI was unsuccessful when I checked it after setting it up overnight. The last info in the OUTPUT tab was: ... --- /boot/ Traceback (most recent call last): File "/usr/bin/emerge", line 3228, in ? mydepgraph.merge(pkglist) File "/usr/bin/emerge", line 1912, in merge retval=portage.doebuild(y,"merge",myroot,self.pkgsettings,edebug,tree="porttree") File "/usr/lib/portage/pym/portage.py", line 2771, in doebuild return merge(mysettings["CATEGORY"],mysettings["PF"],mysettings["D"],mysettings["BUILDDIR"]+"/build-info",myroot,mysettings,myebuild=mysettings["EBUILD"],mytree=tree) File "/usr/lib/portage/pym/portage.py", line 2946, in merge return mylink.merge(pkgloc,infloc,myroot,myebuild) File "/usr/lib/portage/pym/portage.py", line 6984, in merge return self.treewalk(mergeroot,myroot,inforoot,myebuild,cleanup=cleanup) File "/usr/lib/portage/pym/portage.py", line 6593, in treewalk if self.mergeme(srcroot,destroot,outfile,secondhand,"",cfgfiledict,mymtime): File "/usr/lib/portage/pym/portage.py", line 6849, in mergeme if self.mergeme(srcroot,destroot,outfile,secondhand,offset+x+"/",cfgfiledict,thismtime): File "/usr/lib/portage/pym/portage.py", line 6841, in mergeme os.mkdir(mydest) OSError: [Errno 5] Input/output error: '/boot/grub' Exception received: EmergePackageError :FATAL: emerge: Could not emerge sys-boot/grub-0.96-r2! Please submit a bug report (after searching to make sure it's not a known issue and verifying you didn't do something stupid) with the contents of /var/log/install.log and /tmp/installprofile.xml and the version of the installer you used The LOG tab: ... --- /boot/ Traceback (most recent call last): File "/usr/bin/emerge", line 3228, in ? mydepgraph.merge(pkglist) File "/usr/bin/emerge", line 1912, in merge retval=portage.doebuild(y,"merge",myroot,self.pkgsettings,edebug,tree="porttree") File "/usr/lib/portage/pym/portage.py", line 2771, in doebuild return merge(mysettings["CATEGORY"],mysettings["PF"],mysettings["D"],mysettings["BUILDDIR"]+"/build-info",myroot,mysettings,myebuild=mysettings["EBUILD"],mytree=tree) File "/usr/lib/portage/pym/portage.py", line 2946, in merge return mylink.merge(pkgloc,infloc,myroot,myebuild) File "/usr/lib/portage/pym/portage.py", line 6984, in merge return self.treewalk(mergeroot,myroot,inforoot,myebuild,cleanup=cleanup) File "/usr/lib/portage/pym/portage.py", line 6593, in treewalk if self.mergeme(srcroot,destroot,outfile,secondhand,"",cfgfiledict,mymtime): File "/usr/lib/portage/pym/portage.py", line 6849, in mergeme if self.mergeme(srcroot,destroot,outfile,secondhand,offset+x+"/",cfgfiledict,thismtime): File "/usr/lib/portage/pym/portage.py", line 6841, in mergeme os.mkdir(mydest) OSError: [Errno 5] Input/output error: '/boot/grub' Exception received: EmergePackageError :FATAL: emerge: Could not emerge sys-boot/grub-0.96-r2! Please submit a bug report (after searching to make sure it's not a known issue and verifying you didn't do something stupid) with the contents of /var/log/install.log and /tmp/installprofile.xml and the version of the installer you used This isn't really an installer program. It was portage that failed. However, it looks like it failed due to an I/O error, which is typically caused by a failing drive. You may want to run a badblocks scan on your drive before doing anything else. If you still have the LiveCD booted, check the output of `dmesg` for anything pointing to the problem. Badblock reported nothing after full check (hours) GLI install fails at different points when tried a couple more times. Manual install has not failed yet (other than a mysql incl needed for qt - seems this failed for others, workaround install mysql first if qt mysql use flag in use) - I now believe it was some sort of connectivity problem but one that occurs based on GLI settings detected? Feel free to reclose this - just opened it so you would read the addendum. Will try the GLI again in future release, have another pc to do but will stick to manual ;) Re-closing *** Bug 135459 has been marked as a duplicate of this bug. *** |