From nobody Sun Jun 29 14:13:02 2025 X-Original-To: freebsd-current@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 4bVWTt6QLCz60HWZ; Sun, 29 Jun 2025 14:13:06 +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 4bVWTs74D1z49ps; Sun, 29 Jun 2025 14:13:05 +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=Kmrfl8Lt; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="d ogCKYe"; 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-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id A4B1314000DE; Sun, 29 Jun 2025 10:13:04 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Sun, 29 Jun 2025 10:13:04 -0400 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=1751206384; x=1751292784; bh=rYsMJVtBDXIaZZNHcuKo+q23kBnLszWp pXWSfgd0cgU=; b=Kmrfl8Lt26D/rS9mYmCGzhFmdb9ueYy0pdsPMpaoswjZca8U HLAL0cixne/qdLQM4QPRkPzmNjx/c2CX9fNbTYCBOn9mG+79W+1HjJBcgVhGJz1Y xQvNbymmHVTPx6kaz58XjLGqJYeiCOvmOUZi6MkIGjsQBZr0VadkVl2fp5nQWVQj OIY1zvcAQWczicziPT5JvvQWKI2MHfLGDT2KNCxPpRsMNqg8Sfsna0FkploQCcI0 RzRYoIcbxIXb/0d5AyBGkdu0olu8vLy6OgcHHNEVV/HQ2/BSbpHO2DFzZg6XioG6 CxsFQGboeANcwNFo9gnQ4hXHSDNZh2CXqaftsA== 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=1751206384; x= 1751292784; bh=rYsMJVtBDXIaZZNHcuKo+q23kBnLszWppXWSfgd0cgU=; b=d ogCKYe4WDgruK1B4Kn1ZyT4vun7PPls0m+knI4KfMMbSldSvLUr/9FbnciS5ZteX Thks1G27mkoVkh6crfq3t3zxvYjtdYBXHhoXk5C6b5bJMmEmelh2Ghub8zb6fVRD C1vJ+d6J/LU4SKLjBe5Ink233TgBdJMBuiutB0f8nF9eyBSdOw2o6pTbF6t88g6J +TBHk9oxWxCNvmv52emZH19sAXVLHrBBSG+Qv9jLxkRCprFLegui3pUSBiqL2+aI 6XyVYdGCGgFvJLAvTFjjJ1sohezo7L5vb8sHl+jhOzbUktgNMcv7UDNvzsaJzfYD 8oqnDbZXaUnW4uB6MvLdA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdeltdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfggtggusehttdertddttddvne cuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrghtthgvrhhn peeukeejhfeludeitdethfffjeeiuefghedtfeelvefgudeiueevvdeiudejhfdtleenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiuges fhdqmhdrfhhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtph htthhopehfrhgvvggsshguqdhfshesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehf rhgvvggsshguqdgtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 Jun 2025 10:13:04 -0400 (EDT) Date: Sun, 29 Jun 2025 15:13:02 +0100 From: void To: freebsd-fs@freebsd.org Cc: freebsd-current@freebsd.org Subject: removing GELI from a zfs-on-root system Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-0.17 / 15.00]; NEURAL_SPAM_SHORT(0.97)[0.971]; NEURAL_HAM_MEDIUM(-0.72)[-0.717]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; 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]; NEURAL_SPAM_LONG(0.18)[0.181]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.155:from]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-fs@freebsd.org]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4bVWTs74D1z49ps X-Spamd-Bar: / Hi, I'd like to remove the GELI prompt/functionality from a root-on-zfs system. How can I do this without re-initialising the whole system? It's not a redundant array - it's just one disk. There are some methods turning up in a search, but from years ago, and zfs is a fast-moving target. They're all using redundant arrays in their examples. What I'm after is the latest approved/proper method to remove GELI from the booted, unlocked, single-disk zfs system. Is this possible in-situ? OS is FreeBSD 15.0-CURRENT #0 main-n277432-bada3811884c: Sun May 25 15:02:38 BST 2025 GENERIC-NODEBUG amd64 1500043 1500043 # zfs version zfs-2.3.99-323-FreeBSD_g246e5883b zfs-kmod-2.3.99-323-FreeBSD_g246e5883b # lsblk DEVICE MAJ:MIN SIZE TYPE LABEL MOUNT da0 0:104 838G GPT - - da0p1 0:105 512K freebsd-boot gpt/gptboot0 - -:- 492K - - - da0p2 0:106 8.0G freebsd-swap gpt/freebsd-swap SWAP da0p3 0:107 830G freebsd-zfs gpt/freebsd-zfs da0p3.eli 0:110 830G zfs - - -:- 772K - - - thanks in advance for any help/tips --