[gentoo-user] Excessive digest failures in portage

[gentoo-user] Excessive digest failures in portage

[Saphirus Sage]

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:

Calculating dependencies   * Digest verification failed:
 * /usr/portage/dev-libs/libgpg-error/libgpg-error-1.7.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 895
 * Expected: 899
 * Digest verification failed:
 * /usr/portage/app-admin/syslog-ng/syslog-ng-2.1.4.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 2523
 * Expected: 2521
 * Digest verification failed:
 * /usr/portage/dev-libs/libmcrypt/libmcrypt-2.5.8-r1.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 870
 * Expected: 875
 * Digest verification failed:
 * /usr/portage/dev-db/sqlite/sqlite-3.6.14.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 2285
 * Expected: 2286
 * Digest verification failed:
 * /usr/portage/app-admin/eselect/eselect-1.0.12.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 1694
 * Expected: 1700
 * Digest verification failed:
 * /usr/portage/dev-db/sqlite/sqlite-3.6.14.1.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 2262
 * Expected: 2263
 * Digest verification failed:
 * /usr/portage/dev-db/sqlite/sqlite-3.6.13.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 2408
 * Expected: 2404
 * Digest verification failed:
 * /usr/portage/dev-db/sqlite/sqlite-3.6.12.ebuild
 * Reason: Filesize does not match recorded size
 * Got: 2321
 * Expected: 2320

So, is this just the crying screams of a failing drive, or is there some
other problem at hand here?

[gentoo-user] Re: Excessive digest failures in portage

[Nikos Chantziaras]

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+.

Re: [gentoo-user] Re: Excessive digest failures in portage

[Saphirus Sage]

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?

Re: [gentoo-user] Excessive digest failures in portage

[Arttu V.]

On 5/25/09, Saphirus Sage <saphirus497@gmail.com> wrote:
> So, is this just the crying screams of a failing drive, or is there some
> other problem at hand here?

If the drive is SMART-capable, you could try smartmontools, enable
smart and see what the tests say. It might help to diagnose whether it
is the drive or some other part.

-- 
Arttu V.

Re: [gentoo-user] Re: Excessive digest failures in portage

[Stroller]

On 25 May 2009, at 07:55, Saphirus Sage wrote:
> ...
> 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?

I think an Apple hardware diagnostics bootable CD should have been  
supplied with your machine. There are also 3rd party ones  
(TechToolPro?) that are supposed to be better.

But nothing beats actually swapping RAM.

Stroller.