Keep getting error when upgrading to release 13.3

B

bxbzq

Hi,
As title. I keep getting error
gunzip: (stdin): unexpected end of file
metadata is corrupt.
when upgrading to release 13.3 from 13.2. I believe this is because the network problem, if you know where I live. I figure the solution may be:
- use VPN. The VPN I'm using is not a system wide VPN, so where do I fill VPN info for freebsd-update?
- use 13.3 ISO image file I downloaded to upgrade. I don't know the steps. Instructions would be great.

Thanks.
 
When I get error, I delete some gz files under /var/db/freebsd-update and run freebsd-update again until error comes up in a few minuets. If I don't delete those gz files, running freebsd-update gives me error very soon.
Does this count as additional detail?
I think download being too slow causes the upgrade process error.
 
One more try after my last post took me a few steps further, until an error of same type came up after 6 hours downloading.
IMG_6328.jpeg
 
This question is still open.
I come across this article, but the note in the article
"At a minimum, updates require building on a FreeBSD release greater than or equal to the target release version for distribution."
Click to expand...
makes it much less useful. I managed to upgrade to R13.3. Now when I try to upgrade to R14.0, the situation is even worse than upgrading to R13.3 from R13.2. I don't think I will sit around the computer and keep checking the corrupted cache files and repeat the freebsd-update command for a whole day. But if I'm to follow the instructions, I need to first have a machine running R14.0. It's a deadlock.
It looks the only viable solution for me is to find a machine dedicated as an update server. I download iso file of latest release and do fresh install on the server machine then configure it as the update server. Do I have to go this path?
 
"Unexpected end of file", I suspect you're simply running out of disk space. Especially if you have a ZFS system, you may have a whole bunch of old boot environments lingering if you've never cleaned those up.
 
SirDice said:
"Unexpected end of file", I suspect you're simply running out of disk space. Especially if you have a ZFS system, you may have a whole bunch of old boot environments lingering if you've never cleaned those up.
Click to expand...

Disk space is not the problem.
Code: 
root@bsd_t400:/var/db/freebsd-update # zfs list
NAME                                            USED  AVAIL     REFER  MOUNTPOINT
zroot                                          87.5G  54.9G       96K  /zroot
zroot/ROOT                                     73.4G  54.9G       96K  none
zroot/ROOT/13.2-RELEASE-p10_2024-03-13_065637     8K  54.9G     34.2G  /
zroot/ROOT/13.2-RELEASE-p1_2023-08-11_065315      8K  54.9G     28.4G  /
zroot/ROOT/13.2-RELEASE-p2_2023-09-26_222140      8K  54.9G     29.8G  /
zroot/ROOT/13.2-RELEASE-p3_2023-11-26_045421      8K  54.9G     30.4G  /
zroot/ROOT/13.2-RELEASE-p5_2023-12-15_151758      8K  54.9G     32.4G  /
zroot/ROOT/13.2-RELEASE-p8_2024-01-21_161912      8K  54.9G     32.6G  /
zroot/ROOT/13.2-RELEASE-p9_2024-02-19_233133      8K  54.9G     34.6G  /
zroot/ROOT/13.2-RELEASE_2023-07-06_224747         8K  54.9G     27.5G  /
zroot/ROOT/13.3-RELEASE_2024-03-13_073611         8K  54.9G     34.3G  /
zroot/ROOT/13.3-RELEASE_2024-04-03_202223         8K  54.9G     35.1G  /
zroot/ROOT/default                             73.4G  54.9G     32.3G  /
zroot/tmp                                       136K  54.9G      136K  /tmp
zroot/usr                                      13.9G  54.9G       96K  /usr
zroot/usr/home                                 12.2G  54.9G     12.2G  /usr/home
zroot/usr/ports                                 814M  54.9G      814M  /usr/ports
zroot/usr/src                                   915M  54.9G      915M  /usr/src
zroot/var                                      22.0M  54.9G       96K  /var
zroot/var/audit                                  96K  54.9G       96K  /var/audit
zroot/var/crash                                  96K  54.9G       96K  /var/crash
zroot/var/log                                  1.98M  54.9G     1.98M  /var/log
zroot/var/mail                                 19.7M  54.9G     19.7M  /var/mail
zroot/var/tmp                                    96K  54.9G       96K  /var/tmp
 
Maybe unrelated, but for all filesystems that currently have a mountpoint value of / the value should be none

The same for /zroot, should be none
 
grahamperrin said:
Maybe unrelated, but for all filesystems that currently have a mountpoint value of / the value should be none

The same for /zroot, should be none
Click to expand...
If I remember correctly, I selected auto zfs during installation. What difference does it make? How do I change it?
 
Concisely (reference): zfs-set(8).

bectl(8) includes a section for boot environment structures.

An explanation of why we "don't need a mount point" is in Discord for FreeBSD. Realistically, I can't share the link in The FreeBSD Forums without the risk of an idiotic response. Sorry.
 
Last edited:
Like this one?:)
The problem, if I have to guess, is the f**king great wall, not how far the server is from china.
Screenshot 2024-07-20 172844.png
 
bxbzq said:
… when I try to upgrade to R14.0, the situation is even worse …

… Do I have to go this path?
Click to expand...

No.

pkgbase is an alternative path. I'll test 13.3-RELEASE-p4 to 14.1-RELEASE-p2 (base_release_1).

pkg.freebsd.org may have fewer mirrors than download.freebsd.org (according to Appendix A.1 of the FreeBSD Handbook), but any waste of time should be less intensely frustrating than

bxbzq said:
… a whole day. …
Click to expand...
 
You must log in or register to reply here.
Back
Top