This does not look right to me, but if I try to continue anyway and attempt to update my packages, I get errors whenever something is related to flash:
One particular example is the xorg server:
[code]Calculating dependencies / * Missing digest for '/usr/portage/x11-misc/slim/slim-1.3.5-r3.ebuild'
/ * Missing digest for '/usr/portage/x11-base/xorg-server/xorg-server-1.14.3.ebuild'[/code]

I searched the forums and the only thing that resembles to my problem is this:
[url]http://gentoo.2317880.n4.nabble.com/timezone-data-missing-digest-for-timezone-data-2010d-ebuild-td153047.html[/url]

According to that post, the solution is simply to wait and redo the
[code]emerge --sync[/code]

I did that two days ago, but I still got the same errors.
My problem is, I am relatively new to gentoo and do not really understand the error messages. Can you help me understand it better?

Thanks in advance,
Max

Last edited by commander-keen on Sat Mar 01, 2014 3:37 pm; edited 1 time in total

I assume you ran this emerge --sync from an unrestricted root shell, right? What is the output of stat -f /usr/portage? When was the containing filesystem last checked? Have you experienced any events that could cause filesystem corruption?

Concerning file system corruption. I am not quite sure. I installed Gentoo on a HDD and later dumped it to an SSD. I partitioned the SSD so that "/" and "/boot" would have exactly the same size as before. For my home-directory I simply copied the content, for the drives do not have the same capacity. I am pretty sure I used the same FS-types as before. This has already been a while, but now that you say it, I doubt that I ran an emerge --sync since then.

Is this a typical error message related to file system corruption? How can I verify or fix that?
On which parition should I run a FS-check? All portage related things are in "/" right?

You only need to match size if you plan to use dd or equivalent to clone the filesystem, which you should never do when the destination is an SSD. It is bad practice even when the destination is not flash based.

Filesystem corruption can show one of several different errors, depending on the nature of the corruption. When in doubt, check all filesystems. You cannot safely do a full check of a filesystem while it is mounted.

I found out what went wrong. When I transfered the files from HDD to the SSD I (somehow) missed /var. I then copied the missing files from a precedent backup. This way the content of /var did not correspond to the packages installed ion the system. Therefore the confusing error messages. My bad. Thanks for your help anyways!