From nobody Sun Jun 29 14:48:48 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 4bVXH801zBz60JxF; Sun, 29 Jun 2025 14:48:52 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4bVXH71CBXz3HSG; Sun, 29 Jun 2025 14:48:51 +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=0DbzrMPh; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=mn2pqrZn; 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-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfhigh.phl.internal (Postfix) with ESMTP id C65DB1400079; Sun, 29 Jun 2025 10:48:50 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-11.internal (MEProxy); Sun, 29 Jun 2025 10:48:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1751208530; x=1751294930; bh=Lr3dfP4DAhBeS23+xi0lpePntOOLvbq1WQDBZfGxPSc=; b= 0DbzrMPhhuaWN5UBrrgJ6aYjXTfltE+yeWXlp+52KQWnf1CLft4CBe2a6SQCuMl6 wiyGsw+ODcsJ2yYvNICC4xQBr6irFdAM6T0WmxmEVMQHm+6//NRjoXvBi+0/Z6xC nfh83y8HGj+CmQVeMxr2aP8WrKVQjrrLUD2s+CkFuw1yI7kqKvPPFeiNOei6O8bd iWtw9fmfgtj9dKjotAqvSuefJQJuqDISQ6bE/g471alSI494ZVtERsVUY/Uuqaaa Fn0of+sM0MLNBWUZmBZLRbBCIHhudXqkOljGqUElsOCHpQAo/BtPPzB4KRavWgkQ BqJWizu0BnSZzrFhx4KuJA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1751208530; x=1751294930; bh=L r3dfP4DAhBeS23+xi0lpePntOOLvbq1WQDBZfGxPSc=; b=mn2pqrZnoKkaxOz8i 578owKUro8mezT6BMjNf//NEcXZrz63EKMvk1u6yyrolxOxclKiZ5cNPDboH5quP RDmm/jCVAFvLVP85Ki0KexukdJST4FlEmpdGwSF9DDxcP1QZ/UGmXEBuVQGnFhZR yLKiR7XK6WfVPryEwoMTbGPgZ3fKicLosDOCyZ6RaA9UlDbOtj2u+cW7Vh1wGWB8 P9NQFcaek/dT/G3YpY+Jv9TbX7B8zzeXqcU1fs7LGahEJ80UcAadRUbdavnmCiWR HZ/bOBvw7ZLD8C4r7husTCunLxKBGQBQRVdKU1CsDwxjrJFrONTWumP81fDyd92u ANC8A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdeluddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtkeertddttd ejnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrghtthgv rhhnpeduteevgeeggeevieetvdduudetfffffffhteejgffggeevjeffieduteeftedvke enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhi ugesfhdqmhdrfhhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprh gtphhtthhopehfrhgvvggsshguqdgtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhgpdhr tghpthhtohepfhhrvggvsghsugdqfhhssehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 Jun 2025 10:48:50 -0400 (EDT) Date: Sun, 29 Jun 2025 15:48:48 +0100 From: void To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: removing GELI from a zfs-on-root system Message-ID: Mail-Followup-To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: 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=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spamd-Result: default: False [-0.06 / 15.00]; NEURAL_SPAM_SHORT(0.98)[0.985]; NEURAL_HAM_MEDIUM(-0.73)[-0.725]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_SPAM_LONG(0.28)[0.283]; 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:c]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.155:from]; MIME_GOOD(-0.10)[text/plain]; 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: 4bVXH71CBXz3HSG X-Spamd-Bar: / On Sun, Jun 29, 2025 at 08:26:59AM -0600, Alan Somers wrote: >On Sun, Jun 29, 2025 at 8:13 AM void wrote: > >> 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? > > >Nope. One way or another you will need to copy the entire disk. You can't >just remove the encryption sector-by-sector. Oh well :D thanks for the clarification --