From nobody Mon Dec 30 15:45:43 2024 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YML6N42NRz5k5nX; Mon, 30 Dec 2024 15:45:48 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh-a4-smtp.messagingengine.com (fhigh-a4-smtp.messagingengine.com [103.168.172.155]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YML6M2Y4yz4l8W; Mon, 30 Dec 2024 15:45:47 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=fAUvTcIS; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="c Dkdwsa"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.155 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id 2C93511401A1; Mon, 30 Dec 2024 10:45:46 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Mon, 30 Dec 2024 10:45:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm2; t=1735573546; x=1735659946; bh=QVMFRef7NCFDlUk+/B7lrQM4ofMwGMGu /n9hCjr+Wio=; b=fAUvTcISjfcA/fIozlwSsUwlM3aEyLb228G6I6PJ+KYaBHO/ jZd3nyP5p2FVbRpfMnilVcgL4vj8w1Yyf9eBkASlCbTIt2v0Ni656gY8Vda+E7DD Uhr6y3CoWK2T2UGkqL3OLqyW8RvHxSzh6akaCS3zdPXeWvxJIkjEf2bpp94bT8ZN 7EdMd3PmHWk0liXL7E1NpuvXXQEz8xTIN/2CQ194WFgdzBOvqOuMG7oxKFCrGuP7 gm5lUVdHhXDiuYczInn3ViE/e8ZJewg4zAdUTOK8j+EbqhrN4KS/2XnqE1FBYv+v 1eyJ+fE2YlRB6JSA4dpt3CP1Ot0MRDhexKvmNg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1735573546; x= 1735659946; bh=QVMFRef7NCFDlUk+/B7lrQM4ofMwGMGu/n9hCjr+Wio=; b=c Dkdwsaht3e96uc0G7Yp0n24rKw9KspF7bRens27+dkBk+GPsR4OEgiwPez3RIqsw mHjOZo/LeZAyx3skcu31kV8cB8WX0Vbd+FPEBrmf+MiOddUYeaVFvJvSu5o/XsV1 rEchBhmH69OSO/zRSUE4BsXwNjIdgkhtP5RBUQDjaDDhkoRfH7LrF6mqPv6eqYaq IEBvhWbvBEwbnf0ToAUseYZEXwT+HPBtytL2AREQyKOj3eo0hnhTZxgjPT9j16UE eNjepN98Er4nNT2xc3i2eAszPVDl4kZbpzp4c7vDc3npEmulBLJHUgwFoAOMXUJX YMVNuRkY/cIwZfm5nqmvA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddruddviedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvve fukfggtggusehttdertddttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdr fhhmqeenucggtffrrghtthgvrhhnpeeggefhteevgeeiffduteevteejgeehveeikedtgf ekteffieekhfffhfevfeffffenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfh dqmhdrfhhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtphht thhopehfrhgvvggsshguqdhfshesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehfrh gvvggsshguqdhsthgrsghlvgesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 Dec 2024 10:45:45 -0500 (EST) Date: Mon, 30 Dec 2024 15:45:43 +0000 From: void To: freebsd-fs@freebsd.org Cc: freebsd-stable@freebsd.org Subject: "Loader needs to be updated" (azure guest context) Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-3.57 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.973]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.155:from]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org,freebsd-stable@freebsd.org]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4YML6M2Y4yz4l8W X-Spamd-Bar: --- Hi, context is freebsd amd64 vm on Azure (initially installed via azure marketplace several years ago (12-releng)), and has been upgraded as updates became available with freebsd-update over the years all the way up to 13.4-p1 now. System updates/upgrades have *always* been managed with freebsd-update. Latest upgrade from 13.3-p6 to 13.4-p1 shows "loader needs to be updated" in the beastie menu in the console now. This is new. # zfs --version zfs-2.1.14-FreeBSD_gd99134be8 zfs-kmod-2.1.15-FreeBSD_gd99134be8 (perhaps side issue - different version numbers, same -FreeBSD_gd99134be8 ?!!) This system is *not* root-on-zfs. There is zfs, but it's data on a non-boot virtual disk. "zpool status" invites me to upgrade the pool. I've not done this (have never done it with this vm, either), and don't want to unless I'm absolutely certain upgrading the pool won't break everything. I note from a (similar, but different context) thread last September https://lists.freebsd.org/archives/freebsd-current/2024-September/006378.html that FreeBSD uses "the guest's boot loader and the host's /boot/lua files" but I'm clueless how this would apply in an amd64 context with Azure as the host. What do i have to do? Also, is the warning safe to ignore in this context? --