Replacing Drive with SSD

Warren Block wblock at wonkity.com
Wed Sep 16 23:09:34 UTC 2015


On Wed, 16 Sep 2015, Doug Hardie wrote:

>
>> 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 -'

>There is an error in the dump command above.  It needs a ‘/‘ before the 
>‘|’.

Note the "Leaving out most of the options for clarity" part.  See
http://www.wonkity.com/~wblock/docs/html/backup.html#_code_dump_code_via_ssh

Options like -b64 can greatly increase speed.


More information about the freebsd-questions mailing list