From owner-freebsd-questions@freebsd.org Mon Jan 30 05:34:22 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BBEBCC7FFF for ; Mon, 30 Jan 2017 05:34:22 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D24AFE30 for ; Mon, 30 Jan 2017 05:34:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id v0U5YKjM032703 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 29 Jan 2017 22:34:20 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id v0U5YKJ7032700; Sun, 29 Jan 2017 22:34:20 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 29 Jan 2017 22:34:20 -0700 (MST) From: Warren Block To: David Christensen cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 11.0-RELEASE-p7 i386 system drive imaging and migration In-Reply-To: <2973d1ea-202f-60fa-2930-eec05b626cfb@holgerdanske.com> Message-ID: References: <86bmupg0gi.fsf@WorkBox.homestead.org> <2973d1ea-202f-60fa-2930-eec05b626cfb@holgerdanske.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (wonkity.com [127.0.0.1]); Sun, 29 Jan 2017 22:34:20 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 05:34:22 -0000 On Sun, 29 Jan 2017, David Christensen wrote: > As I understand it, taking an image involves: > > 1. Back up the MBR (dd?). gpart backup ada0 > 2. Back up the slice 1 partition table (?). gpart backup ada0s1 > 3. Back up bootpool file system ('zfs send'). > > 4. Back up the swap partition encryption container header (?). geli. Easier to just initialize the receiving disk with geli and enter the same key. > 5. Back up the zroot partition encryption container header (?). As above. > 6. Back up zroot file system ('zfs send'). > > > Restoring an image involves: > > 1. Restore MBR ('dd'). gpart restore ada0 > 2. Restore slice 1 partition table (?). gpart restore ada0s1 Create encryption, if truly desired, with geli(8). > 3. Create bootpool ZFS pool and file system (?). zpool create > 4. Restore bootpool file system ('zfs receive'). > 10. Create zroot ZFS pool and file system (?). zpool create > 12. Restore zroot file system ('zfs receive'). > > These processes are complex enough to warrant automation. Can Clonezilla > handle FreeBSD 11.0 with MBR and encrypted ZFS root? Clonezilla can handle UFS, last I checked. ZFS, no, and encryption just appears as binary data to anything that lacks geli(8). > 1. Putting the original system drive into another computer broke Xfce > applications. Something to do with missing semi-important filesystems, maybe. Or the age of a Pentium D, although that still ought to be supported. Maybe options were selected to optimize for that CPU that are not good in a newer one. > 2. Everything works as before when the original system drive is put back > into original computer (I am typing this message on that system). > > 3. The cloned drive works and has passed Intel SSD Toolbox checks. > > 4. Putting the cloned drive into the original computer broke Xfce > applications in exactly the same way. > > > I doubt it's an SSD hardware problem. Writing SSDs with dd is not good, limiting their wear leveling.