Thanks. I am using my usual installation procedure, with a recently downloaded FreeBSD installer written to a USB thumb drive. It has almost always worked in the past. I started the installation process by booting the USB drive and connected to the internet with my ethernet device.All those messages talk about mnt so looks like you are trying to install from an (unmounted) mount point.
Good question. I'm assuming that the .txz archive files which are pre-selected in the installer dialog are on the installer USB, whereas the additional archives, such as src.txz, ports.txz, and lib32.txz, need to be downloaded from one of the FreeBSD servers. When I run the installation using only the pre-selected archives, I have no problems.Those messages seem relate to files not found locally - are they definitely on the USB stick and its mounted etc?
e.g. that first path?
I've been trying to do a fresh install of FreeBSD 13.1-RELEASE for about a week, unsuccessfully. I'm guessing that this might be related to the unavailability of package servers, which some people have been reporting recently.
View attachment 15162
View attachment 15163
View attachment 15164
View attachment 15165
If you look closely, you can see that you're using three forward slashes instead of the expected two. (e.g. file://mnt/usr/freebsd-dist/whoops.txz)
file://
with two slashes followed by /mnt/usr/freebsd-dist/src.txz
full path which includes preceding slash.The USB drive has base.txz, kernel-dbg.txz, kernel.txz, lib32.txz, ports.txz, src.txz, and tests.txz in directory /usr/freebsd-dist/.So if you
ls /mnt/usr/freebsd-dist/base.txz
there‘s definitely that file on your USB key?
So far as I can see the network issues accessing FreeBSD repositories were resolved days ago.
Where exactly are these files?Good question. I'm assuming that the .txz archive files which are pre-selected in the installer dialog are on the installer USB, whereas the additional archives, such as src.txz, ports.txz, and lib32.txz, need to be downloaded from one of the FreeBSD servers. When I run the installation using only the pre-selected archives, I have no problems.
Enabling base-dbg and/or lib32-dbg seems to trigger a bug causing the paths to get hosed. The /mnt path isn't correct, that's where the 'destination' filesystems are mounted during the install. The correct path should beIf I untick the boxes for base-dbg.txz and lib32-dbg.txz, the installer proceeds without any noticeable problems. Therefore, I infer that base-dbg.txz and lib32-dbg.txz need to be downloaded from the ftp server, if their boxes are ticked. It is only then that I encounter noticeable problems.
file:///usr/freebsd-dist/base.txz
.Have you installed finally ?The required *.txz files are automatically pre-mounted on the USB installer drive at directory /usr/freebsd-dist/.
Unless I'm sadly mistaken, the files base-dbg.txz and lib32-dbg.txz not being included with the memstick image installer archive:
FreeBSD-13.1-RELEASE-amd64-memstick.img
... whereas they ARE included with the mini-memstick image installer archive file:
FreeBSD-13.1-RELEASE-amd64-mini-memstick.img
... so I'll postpone the process of marking this thread as "Solved" for now.
Have you installed finallyThe required *.txz files are automatically pre-mounted on the USB installer drive at directory /usr/freebsd-dist/.
Unless I'm sadly mistaken, the files base-dbg.txz and lib32-dbg.txz not being included with the memstick image installer archive:
FreeBSD-13.1-RELEASE-amd64-memstick.img
... whereas they ARE included with the mini-memstick image installer archive file:
FreeBSD-13.1-RELEASE-amd64-mini-memstick.img
... so I'll postpone the process of marking this thread as "Solved" for now.
Oh yes. This post is over 3 months old. I apologize for not marking it "Solved," which I'll do right now.Have you installed finally ?