Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jan 2017 22:34:20 -0700 (MST)
From:      Warren Block <wblock@wonkity.com>
To:        David Christensen <dpchrist@holgerdanske.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD 11.0-RELEASE-p7 i386 system drive imaging and migration
Message-ID:  <alpine.BSF.2.20.1701292221150.71961@wonkity.com>
In-Reply-To: <2973d1ea-202f-60fa-2930-eec05b626cfb@holgerdanske.com>
References:  <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com> <86bmupg0gi.fsf@WorkBox.homestead.org> <2973d1ea-202f-60fa-2930-eec05b626cfb@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1701292221150.71961>