Many thanks for the hint, that helped
/usr/share/relink was a symlink to /home/relink due to capacity issues.
Exists since May, so must have been the result of the last upgrade.
I did remove it and replaced with a plain directory after a bit resizing
my partitions - now it works. I was not aware this can cause such troubles
On 28.10.2025 04:15, Anthony J. Bentley wrote:
Armin Baumgarten writes:
I boot from bsd.rd and
run (U), it works fine until the step of installing (extracting) the
system. Then it fails like this (after mount of FS I dropped out using
ctrl+Z to show the available free space, yet behavior is anyways same
when I do not put in background for a few seconds):
...
Why is it writing to / on ramdisk? Obviously there is not enough space.
Do you have a directory somewhere on your system that's been symlinked
to an absolute path?
