On Fri, Jan 7, 2011 at 10:41 AM, Simon <[email protected]> wrote: > This issue happend after a 'emerge -uDN world' after I had not done > any updates for a bit over 60 days. (I was just too busy) > > I already have: > sys-apps/portage-2.1.9.25 > > and I don't have smartctl, what pkg is it in? I'm not sure it will > give valid info though as this is a VPS and everything is XENified. > My root device is /dev/xvda to give you an idea... > > But I did run an fsck, a pretty thorough one like fsck.ext3 -c -c -f > or something like that... I also added another option that made it > super verbose, so I don't know if anything was found, just that > *filesystem was modified* by it... > > I just did the following emerge, these packages had not been > recompiled by the emerge -e system that crashed. They all compiled > top shape, but the problem doesn't happen on every package, so it's > hard to tell... > > emerge app-shells/bash sys-apps/util-linux sys-fs/e2fsprogs > dev-lang/python sys-apps/portage sys-apps/baselayout sys-fs/udev > sys-apps/busybox > > I will redo a simple fsck.ext3 -c -c -f /dev/xvda and see what it says > exactly (if it says anything). And then i will --sync and -e @system > again... I'll reply to the list with my results... > > Thanks, > Simon >
smartctl is in smartmontools. Possibly consider the ~ version of portage. I'm currently at 2.2.0_alpha13. It works well for me. __Definitely__ check out Dale's suggestion that possibly python-3 got selected. Good luck, Mark
