Nikos Chantziaras wrote:
> Saphirus Sage wrote:
>> This has been a consistent problem on one of my computers, to no avail
>> thusfar, even after changing sync server settings or redigesting
>> individual failed ebuilds. In running emerge -uavDN world, it will take
>> at least an hour to generate a list of packages to be merged, but not
>> before ouputting a TON of failed digests. Example below.
>>
>> gentoog4 proc # emerge -uavDN world
>>
>> These are the packages that would be merged, in order:
>>
>> [...]
>>
>> So, is this just the crying screams of a failing drive, or is there some
>> other problem at hand here?
>
> Does dmesg say anything about disk I/O errors? Also, try something
> like this:
>
> cp -a /usr/portage /tmp/
> diff -r /usr/portage /tmp/portage
>
> If the diff claims something differs, then it's pretty certain your
> disk or RAM might be failing. For RAM, try memtest86+.
>
>
Followed the instructions and checked with diff, absolutely no
difference, which leads me to believe it's failing memory; but there's a
problem. This is a PowerPC machine (eMac G4), and memtest86+ seems to be
dependent upon an x86 architecture. So, is there any good way to test
this, or do I just pull out one of the 512 DIMMS and hope for the best?
