From nobody Thu Dec 28 09:28:22 2023 X-Original-To: freebsd-fs@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 4T139719kTz55SN6 for ; Thu, 28 Dec 2023 09:28:43 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [135.125.211.209]) (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 4T139572Nfz3QWm for ; Thu, 28 Dec 2023 09:28:41 +0000 (UTC) (envelope-from trashcan@ellael.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ellael.org header.s=dkim header.b=o15lrpFP; spf=pass (mx1.freebsd.org: domain of trashcan@ellael.org designates 135.125.211.209 as permitted sender) smtp.mailfrom=trashcan@ellael.org; dmarc=pass (policy=quarantine) header.from=ellael.org Received: from smtpclient.apple (p5b2e5747.dip0.t-ipconnect.de [91.46.87.71]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 4T138x2pBLz1JSk; Thu, 28 Dec 2023 10:28:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellael.org; s=dkim; t=1703755713; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dnHPPFSaODMwe+sBLIeQDCUKGF0vfM2BYnfHLe3fQh8=; b=o15lrpFPrx4SwQNFYbWWTCsV3aI3fMGlCBPvpAj/2+3QB4m9oI5MztgPLfbYSibCH4p8os 3TF9G0zzfDWHh1Rb+BNZ7MF/+RhNIBhQmnYziwS0YBP8GWHdg++o87Zz0BsrumNhzZ3NY8 8t/X6m67bfOkmlEgVsNUoRENc7XrkV1TFrEfl3b3P7JwkhNO4k8iIo7UXDe01TrN01VBU5 ICybxxXbK2gPovo8bJDr3A9WPVfU2spj2944IIdWJREuUStzw3DPRDwzAuchcokSoPnIIa GfDiAp8cZpEbrq9gcYpZvYrNO5rS9WDN38ld9FDhcsjzQ43pFzKYbgoHgy/+Hw== Content-Type: text/plain; charset=utf-8 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: Howto migrate a FreeBSD cloud instance to another one without native FreeBSD support? From: Michael Grimm In-Reply-To: Date: Thu, 28 Dec 2023 10:28:22 +0100 Cc: Miroslav Lachman <000.fbsd@quip.cz>, Alexander@leidinger.net Content-Transfer-Encoding: quoted-printable Message-Id: <40702ABB-1DD2-44D3-B33E-0EAB60D19B5C@ellael.org> References: <4A6398FE-5DC1-45A1-85A9-7C5054CF5BF7@ellael.org> To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spamd-Result: default: False [-2.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[ellael.org,quarantine]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:135.125.211.209]; R_DKIM_ALLOW(-0.20)[ellael.org:s=dkim]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; ASN(0.00)[asn:16276, ipnet:135.125.128.0/17, country:FR]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[ellael.org:+]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4T139572Nfz3QWm X-Spamd-Bar: -- Alexander Leidinger wrote > Am 2023-12-26 19:41, schrieb Michael Grimm: >> Miroslav Lachman <000.fbsd@quip.cz> wrote; >>> On 26/12/2023 15:22, Michael Grimm wrote: >> Sorry, if I haven't been clear enough: >> #) I do want to migrate an existing ZFS pool (from one instance to = another (zfs send | zfs receive). >> This I have done numerous times before. >> #) New to me is the preparation of the target disk out of an = Ubuntu/Linux rescue system. >> Namely, how to partition with Linux functionality (gdisk, cfdisk, = =E2=80=A6) lacking gpart? >> Namely, which kind of booting to use (legacy versus EFI)? >>> And the second is: you can prepare small minimalistic FreeBSD image = in Bhyve / VirtualBox etc. make a copy of it with dd and then write it = by dd to your new instance's disk with the help of Linux rescue system. = Then you can reboot to a minimalistic FreeBSD system, enlarge = partition(s), use growfs or zpool / zfs enlargement and then finally = move data from the old instance to this new instance by rsync, or zfs = send, or whatever tool you prefer. >> Thanks for this info, very much appreciated. >=20 > This is more or less what I did for such a case (local provider, not = OVH): I used an existing FreeBSD system, created a file of a few GB, = dd-ed /dev/zero to it completeley (for a compressed transfer), created a = md(4) out of the file, partitioned it, created a root pool, installed = FreeBSD into it, created a suitable rc.conf and such to boot from it, = and wrote it to the linux rescue system on the target host "ssh -C = me@target dd of=3D/dev/sda