Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jan 2017 12:55:41 -0600
From:      Brandon J. Wandersee <brandon.wandersee@gmail.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:  <86bmupg0gi.fsf@WorkBox.homestead.org>
In-Reply-To: <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com>
References:  <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

David Christensen writes:

> What is the proper way to clone a FreeBSD system image from one drive to 
> another?

In my personal opinion, the "proper" way is to back up your data, create
a fresh partition table and filesystems on the new disk, and restore the
backup. Using `dd` to clone an entire disk byte-for-byte works, but it's
the painfully slow, tedious, and potentially dangerous way of doing
this. The native backup utilities---dump(8) and restore(8) for UFS, `zfs
send` and `zfs receive` for ZFS---will copy the data from an existing
filesystem and write to a new filesystem at speeds exponentially greater
than anything you'll get from `dd`.

However, I'm not sure that addresses the actual problem in this
particular case. I can't say exactly what the error message you're
getting means, but while it might stem from how you copied the system it
might also imply a problem with the disk itself. Unrecoverable read
errors, maybe.

-- 
::  Brandon J. Wandersee
::  brandon.wandersee@gmail.com
::  --------------------------------------------------
::  'The best design is as little design as possible.'
::  --- Dieter Rams ----------------------------------



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?86bmupg0gi.fsf>