Search results

Hi Understudy, Is your suggestion to clean out /var/db/freebsd-update or /var/db/etcupdate? Following the link you provided it seems perfectly safe to clear out /var/db/freebsd-update, but I don't see guidance on /var/db/etcupdate. I did find in the handbook...

Hello, I've got a dozen 13.1-RELEASE-p1 amd4 instances that I'm attempting to update to 13.1-RELEASE-p5. When I run freebsd-update fetch I get... The following files are affected by updates. No changes have been downloaded, however, because the files have been modified locally...

As of 2022, I figured it out by selecting the "Edit" link at the bottom of the initial post, then back near the top, under "Title" one sees a dropdown with the default label "No Prefix". Click on that and select "Solved".

Thanks for the info. In the future, should I monitor (or post) in a different location for updates/issues of this nature?

Curious, I tried with the freebsd-update -s update.freebsd.org and it ignored that switch, choosing mirror1 and mirror2 instead. Also curious, /etc/freebsd-update.conf has ServerName update.FreeBSD.org as the default.

Yes, as of 24 Apr 22 @ 1035 US/Central

Hello, Given 13.1-RC4 was just released, I tried freebsd-update on a raspberry pi4. It looks like the "metadata signature" is missing? pi4-f579% uname -a FreeBSD pi4-f579 13.1-RC3 FreeBSD 13.1-RC3 releng/13.1-n250110-ec2fbe4b1ec GENERIC arm64 pi4-f579% sudo freebsd-update upgrade -r 13.1-RC4...

Ok, that makes sense. Thank you both for the information.

I have a number of system recently update (via source) to 12.2 p10 (amd64). uname -a and freebsd-version -rku all agree the system is 12.2-RELEASE-p10. I've been trying to force myself to use freebsd-update (with boot environments) to simplify and speed-up upgrading. After updating to p11...

I'm experiencing the same issue. Did you find a solution or a viable workaround?

Hello! I just ran freebsd-update fetch install on a 12.2-RELEASE-p4 system to get to p5 (amd64). I received a rather confusing output from freebsd-update: The following files will be added as part of updating to 12.2-RELEASE-p5: /etc/ssl/blacklisted/2c543cd1.0 /etc/ssl/blacklisted/2e4eed3c.0...

true, thanks for the tip

That leaves me with few options. What's especially insidious is I seen nothing in the output logs of my backup script that there was a failure, either with ssh or zfs send. Are you aware of any technique that would detect or alleviate issues like this? Right now doing a zfs recv on the remote...

I suppose there's no option or sysctl that would force a receive to go as far as it can, rather than abandoning the whole operation?

It takes quite some time before it fails, like it's reading most of the file then quits. The backup I care most about was made months ago.

A further observation... I keep four backups of each ZFS filesystem. The newest three all error out in a similar manner. I was able to successfully receive the oldest of the four files. So it would seem something went wrong, silently, with the original zfs send.

Thanks for the response... I'm trying to read from a file created from zfs send. So the original command, more accurately, was zfs send -pv $pool/$filesystem@$snap | ssh $user@$remotehost "cat > $filesystem.zfs". The receive operation is attempted sometime later and is cat $filesystem.zfs |...

Small typo in my command... my backup script has a redirect ">". i.e., ssh $remotehost "cat > $filesystem.zfs"

Hello, I backup zfs filesystem from one server (11.1R) to another with the command zfs send -p $pool/$filesystem | ssh $remotehost "cat $filesystem.zfs". When attempting to receive the zfs filesystem I'm getting the error message (1) cannot receive: failed to read from stream. Is there a way...

Hello, I have a SUN FIRE X4200 M2 running FreeBSD 11.2Rp10. I was doing some ZFS snapshot cleanup when the OS panicked. Upon reboot I was greeted with... Starting file system checks panic: solaris assert: offset + asize <= msp->ms_start + msp->ms_size (0x2d67daa00 <= 0x200000000), file...