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