Thanks Tim, that was right on the money! Indeed my „/bsd“ was a symbolic link, pointing to „/bsd.mp“. Because the target path of the symlink was absolute, when it tried to write the new kernel to „./mnt/bsd“ it of course pointed to the ramdisk.
After removing that symlink, the upgrade process went through without a hitch. TL;DR: Use relative paths when you symlink „/bsd“. Nicolas > Am 20.02.2018 um 15:42 schrieb trondd <tro...@kagu-tsuchi.com>: > >> On Tue, February 20, 2018 8:34 am, Nicolas Schmidt wrote: >> Hey, >> >> it's me again, still trying to upgrade to 6.2. >> >> After choosing to skip verification and continue the upgrade process, I >> now immediately get the following error: >> >> Installing bsd 0% | >> id 0 on /: file system full >> >> /: write failed, file system full >> ftp: Writing -: No space left on device >> >> Going to a shell, "df" reveals >> >> Filesystem 512-blocks Used Avail Capacity Mounted on >> /dev/rd0a 6143 6116 27 100% / >> /dev/sd2a 2057756 179068 1775804 9% /mnt >> . >> . >> . >> >> To me it seems, the install script is trying to install the kernel on the >> ram disk mounted on / instead of the actual root partition mounted on /mnt >> (sd2 is the volume I chose for installation; it's a RAID 1). Since the ram >> disk is full, this of course has to fail. >> >> Any suggestions? >> >> Best regards and thanks for your help, >> Nicolas >> > > This just came up on Daemonforums. The user had a symlink pointing to an > absolute path starting with /. The installer follows that symlink to the > ramdisk / instead of /mnt. > > http://daemonforums.org/showthread.php?p=63885 > > Tim.
