Hi Tobias and Felix,

the posix file was actually pointing to the correct parent directory (my bad)
and as Felix mentioned probably not the root of my issue.

The `guix gc --verify=contents,repair` unfortunatly did not help either.

I looked a bit around and found this in /var/guix/profiles

drwxr-xr-x 4 root root 4096 Jan 21 16:28 per-user/
lrwxrwxrwx 1 root root   14 Mar  8 16:20 system -> system-53-link
lrwxrwxrwx 1 root root   50 Feb 12 14:58 system-49-link -> /gnu/store/r048wnvv5wb792d0h29147j4q2m874d0-system
lrwxrwxrwx 1 root root   50 Mar  8 15:17 system-50-link -> /gnu/store/99kgb2jh7jdjcvqac81dj0gd2nkhanmw-system
lrwxrwxrwx 1 root root   50 Feb 20 12:30 system-51-link -> /gnu/store/cwk04xkh3zf7vb5bg3cpjr8jyviv5b2f-system
lrwxrwxrwx 1 root root   50 Feb 25 14:16 system-52-link -> /gnu/store/aqxlpw468wvnardbb8dmyxj1qghv68ah-system
lrwxrwxrwx 1 root root   50 Mar  3 16:33 system-53-link -> /gnu/store/1xdmrafzscrpi34rynag71my6nw3w8w2-system
lrwxrwxrwx 1 root root   50 Mar  8 15:53 system-54-link -> /gnu/store/cjdabnlk74irjh3xwqh9d31kza3c78a0-system

Right now I rolled back to generation 53, which is still
working. Generation 54 is the broken one, which does boot up, but
logging in fails with the too many levels of symbolic link issue.

Is it correct to look for the problematic files in the directory to
which system-54-link links to?

I run the problematic commands from that directory and they seem to run
from the non-broken system

I'm thinking of re-installing my system completely. Do I have any other
option, even an unsupported one?

Thanks again for your help,

Roman.

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> [[PGP Signed Part:Undecided]]
> Hi Roman,
>
> Roman Scherer 写道：
>>   /gnu/store/097dmm40lhcf777acqh5i660j4i09k85-tzdata-2022a/share/zoneinfo/posix
>>
>> links to itself.
>
> FYI, it should link to its parent:
>
>  /gnu/store/097dmm40lhcf777acqh5i660j4i09k85-tzdata-2022a/share/zoneinfo
>
> (So, yes, you could …/posix/posix/posix/posix/… all night long.)
>
>> Since I read I should not mess with the store, any
>> ideas how to get rid of that file system loop in a safe way?
>
> You could try
>
>  # guix gc --verify=contents,repair
>
> and Guix should detect the mismatch and refresh tzdata from a
> substitute server.
>
> The unsupported alternative would be to bind-mount /gnu/store
> somewhere and manually relink the file.
>
>> I already tried re-installing it, but that had no effect.
>
> It wouldn't.
>
> Kind regards,
>
> T G-R
>
> [[End of PGP Signed Part]]