From owner-freebsd-questions@freebsd.org Wed Sep 16 05:44:21 2015 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 EEC899CDB60 for ; Wed, 16 Sep 2015 05:44:21 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id ABDF21DEE for ; Wed, 16 Sep 2015 05:44:21 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.12] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.9) with ESMTP id t8G5iIpC084183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Sep 2015 22:44:19 -0700 (PDT) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Replacing Drive with SSD From: Doug Hardie In-Reply-To: Date: Tue, 15 Sep 2015 22:44:18 -0700 Cc: FreeBSD Questions Content-Transfer-Encoding: quoted-printable Message-Id: <514A6AC5-9F42-48E2-A37C-5196E6D4DF47@lafn.org> References: <20150829220311.c7608be1.freebsd@edvax.de> <55E45973.2050103@sneakertech.com> <55E4865B.1000104@sneakertech.com> <20150831181135.7682a810@gumby.homeunix.com> <867fnywc8i.fsf@WorkBox.Home> <08306F31-955B-4710-B20B-4F2ABE0CBA56@kraus-haus.org> <997E40C8-6C07-4621-B5D8-E0672DC4517B@lafn.org> To: Warren Block X-Mailer: Apple Mail (2.2104) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 05:44:22 -0000 > On 15 September 2015, at 07:03, Warren Block = wrote: >=20 > On Tue, 15 Sep 2015, Doug Hardie wrote: >=20 >> After spending a lot of time reading through the various responses, I = decided to use a larger SSD and use dump/restore to move the data. = However, I encountered an interesting problem which I do not have a = solution for at this time. The system will only boot a memstick image. = That works fine. I formatted the new SSD and got it all setup. = However, none of the current systems have enough space to do a dump on. = I needed to dump from the existing machine over to the new one with the = SSD. The only thing running on the SSD machine is the live file system. = Dump uses rsh/rcmd which need some files set in /root. Unfortunately = that is mounted as read only as its a memstick image. I can=92t see how = to easily get dump to dump to a remote system when you can=92t get = rsh/rcmd to login. >=20 > The live filesystem from an installer will work, although mfsBSD is = nicer. >=20 > Pipe the output from dump into an ssh session on the remote machine = that runs restore. Leaving out most of the options for clarity: >=20 > dump -f - | ssh user@remote 'cd /target && restore -rf -' >=20 > If a dump file is desired, it can be created on the SSD filesystem: > = http://www.wonkity.com/~wblock/docs/html/backup.html#_code_dump_code_via_s= sh >=20 > That file can be restored directly on that system. Since the SSD has = essentially zero access time, it does not hurt like restoring a dumpfile = on the same drive. Unfortunately, these approaches don=92t work either. The installer=92s = live filesystem only has one user, root with a null password. It can=92t = start sshd because there are no keys on the live filesystem and /etc is = not writable. Likewise I can=92t run nfs on the machine because the = exports file cannot be created. I am downloading mfsBSD to see if that = can be made to work. It does not appear to support ssh, but claims to = include nfs.