Date: Wed, 16 Sep 2015 15:12:34 -0700 From: Doug Hardie <bc979@lafn.org> To: Warren Block <wblock@wonkity.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Replacing Drive with SSD Message-ID: <9B43BB2E-779C-4859-B4B5-9BE395F0254B@lafn.org> In-Reply-To: <alpine.BSF.2.20.1509160642580.50308@wonkity.com> References: <CEAD84AD-341A-4FB9-A3A1-D0D5A550AFFD@lafn.org> <alpine.BSF.2.20.1508281235390.74312@wonkity.com> <20150829220311.c7608be1.freebsd@edvax.de> <alpine.BSF.2.20.1508300633160.44682@wonkity.com> <55E45973.2050103@sneakertech.com> <alpine.BSF.2.20.1508311000550.42983@wonkity.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> <alpine.BSF.2.20.1509150753490.99919@wonkity.com> <514A6AC5-9F42-48E2-A37C-5196E6D4DF47@lafn.org> <alpine.BSF.2.20.1509160642580.50308@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 16 September 2015, at 06:38, Warren Block <wblock@wonkity.com> = wrote: >=20 > On Tue, 15 Sep 2015, Doug Hardie wrote: >=20 >>=20 >>> On 15 September 2015, at 07:03, Warren Block <wblock@wonkity.com> = 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. >>=20 >> 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. >=20 > mfsBSD *does* have sshd, and is writable. I thought that could be = done with the installer also, sorry. mfsBSD does work. I am transferring the data now. Looks like it will = take about 7 hours as there are about 300 GB to transfer. Dump is = claiming that time figure. There is an error in the dump command above. = It needs a =91/=91 before the =91|=92. Thanks for all the help from everyone. =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9B43BB2E-779C-4859-B4B5-9BE395F0254B>