Problem running hbsd-update

[Pawel Kraszewski]

I have 2 fresh HardenedBSD devices. Everything went OK, but I can't hbsd-update them. Each attempt ends with:

hbsd-v1300061-1b8f98e0dc43779ceefacc1774c386f70c0d5d49

/tmp/tmp.oQXHvxYP/update.tar                           530 MB 1132 kBps 07m59s

./efi/: Can't restore time

tar: Error exit delayed from previous errors.

Partitions are default for EFI install:

 

# cat /etc/fstab

# Device        Mountpoint      FStype  Options Dump    Pass#

/dev/ada0p2     /               ufs     rw      1       1

/dev/ada0p1     /boot/efi       msdosfs rw      2       2

/dev/ada0p3     none            swap    sw      0       0

# mount

/dev/ada0p2 on / (ufs, local, journaled soft-updates)

devfs on /dev (devfs)

/dev/ada0p1 on /boot/efi (msdosfs, local)

Free space is plenty:

# df -h

Filesystem     Size    Used   Avail Capacity  Mounted on

/dev/ada0p2    111G    2.3G    100G     2%    /

devfs          1.0K    1.0K      0B   100%    /dev

/dev/ada0p1    256M    1.7M    254M     1%    /boot/efi

installed packages don't go beyond mc/rsync/tmux/zsh with dependencies.

[Balazs Toth]

I have the same problem, I do not know the final solution but you will be able to update if you umount the EFI partition until you execute the hbsd-update. I can not guarantee your system will boot afterwards but mine did, and I think yours will boot as well as there only the EFI loader how far I know.

[Shawn Webb]

I remember reading a FreeBSD commit that enforces the mount of
/boot/efi. This probably conflicts with how hbsd-update untars the
base tarball.

I'll take a look this week. Thanks for the report, Pawel, and the
confirmation it applies to multiple systems, Balazs.

I'll report back when I have more info.

Thanks again,

--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc

[Shawn Webb]

Also, can either one of you file a bug report on our GitLab[0]? It'll
be easier for me to track and give proper attribution.

[0]: https://git.hardenedbsd.org/

Thanks,

--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc

[Balazs Toth]

Hi,

I have created one (copied the conversation there)

https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/issues/43

B

[Shawn Webb]

Thanks a bunch!

On Tue, May 11, 2021 at 06:44:07PM +0200, Balazs Toth wrote:
> Hi,
>
> I have created one (copied the conversation there)

> https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/issues/43 <https://git.hardenedbsd.org/hardenedbsd/HardenedBSD/-/issues/43>

[Pawel Kraszewski]

Thank you for transmuting my post into a bug report. 

I can confirm unmounting /boot/efi allows the process to complete.