Replacing Drive with SSD

Doug Hardie bc979 at lafn.org
Wed Sep 16 22:12:43 UTC 2015


> On 16 September 2015, at 06:38, Warren Block <wblock at wonkity.com> wrote:
> 
> On Tue, 15 Sep 2015, Doug Hardie wrote:
> 
>> 
>>> On 15 September 2015, at 07:03, Warren Block <wblock at wonkity.com> wrote:
>>> 
>>> On Tue, 15 Sep 2015, Doug Hardie wrote:
>>> 
>>>> 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’t see how to easily get dump to dump to a remote system when you can’t get rsh/rcmd to login.
>>> 
>>> The live filesystem from an installer will work, although mfsBSD is nicer.
>>> 
>>> Pipe the output from dump into an ssh session on the remote machine that runs restore.  Leaving out most of the options for clarity:
>>> 
>>> dump -f - | ssh user at remote 'cd /target && restore -rf -'
>>> 
>>> 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_ssh
>>> 
>>> 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’t work either.  The installer’s live filesystem only has one user, root with a null password.  It can’t start sshd because there are no keys on the live filesystem and /etc is not writable.  Likewise I can’t 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.
> 
> 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 ‘/‘ before the ‘|’.

Thanks for all the help from everyone.  



More information about the freebsd-questions mailing list