From 0565df149c20b9ba34c3287b47ff2d0c0b80957e Mon Sep 17 00:00:00 2001 From: kn0wmad <39687477+kn0wmad@users.noreply.github.com> Date: Thu, 23 Feb 2023 16:02:29 +0000 Subject: [PATCH] Maint/misc improvements (#310) * Add warnings about powering external drives to Restore page * Add caveat to physical backups excusing One/Pro users from power reqs * Add warning about ssh key changes to SSH guide * spelling --------- Co-authored-by: BitcoinMechanic --- site/source/user-manual/backups/backup-restore.rst | 4 ++-- .../user-manual/backups/backup-setup/backup-physical.rst | 2 +- site/source/user-manual/ssh.rst | 2 ++ 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/site/source/user-manual/backups/backup-restore.rst b/site/source/user-manual/backups/backup-restore.rst index 7e41be6..6392015 100644 --- a/site/source/user-manual/backups/backup-restore.rst +++ b/site/source/user-manual/backups/backup-restore.rst @@ -11,6 +11,8 @@ There are 3 different ways that you may choose to restore Embassy data, as well #. "Recover" (as in, disaster recovery) all Embassy data in the event that your backup is the **only** thing you have left. #. "Transfer" all data from an existing Embassy. This is a total migration for use when upgrading hardware only. +.. warning:: If you are restoring data from a drive that you are attaching *directly to your Embassy,* (if using a RasPi or other low-powered board) please ensure that it is getting adequate power. This is best accomplished via external power to the drive (such as a powered USB hub). Embassy One (NASPi Geekworm case with built-in power management) and Embassy Pro users can safely ignore this warning. + Select the appropriate tab below to restore your data: .. tabs:: @@ -108,8 +110,6 @@ Select the appropriate tab below to restore your data: .. figure:: /_static/images/restore/recover6.png :width: 60% - - .. group-tab:: Transfer #. During :ref:`Initial Setup`, select "Recover." diff --git a/site/source/user-manual/backups/backup-setup/backup-physical.rst b/site/source/user-manual/backups/backup-setup/backup-physical.rst index 07d95bc..499f452 100644 --- a/site/source/user-manual/backups/backup-setup/backup-physical.rst +++ b/site/source/user-manual/backups/backup-setup/backup-physical.rst @@ -11,7 +11,7 @@ Backup to Physical Drive The recommended method of backup (including with external drives) is to setup a :ref:`Network Folder` via your OS. However, you may use a powered external drive, or external drive via a powered USB 3.0 hub, connected directly to your Embassy if you prefer. -.. warning:: If you still choose to plug into your Embassy, this drive MUST have external power, or be connected via a powered USB hub in order to prevent any data corruption due to power constraints! +.. warning:: If you still choose to plug into your Embassy, this drive MUST have external power, or be connected via a powered USB hub in order to prevent any data corruption due to power constraints! Embassy One (NASPi Geekworm case with built-in power management) and Embassy Pro users can safely ignore this warning. #. Ensure your backup drive is properly formatted. The recommended format at this time is ``exFAT``. **Do not** use ``fat32``. diff --git a/site/source/user-manual/ssh.rst b/site/source/user-manual/ssh.rst index c49e9ec..bd9a35e 100644 --- a/site/source/user-manual/ssh.rst +++ b/site/source/user-manual/ssh.rst @@ -87,6 +87,8 @@ Connecting via CLI (Linux/Mac) Replacing ```` with your Embassy's LAN (``embassy-xxxxxxx.local``) address +.. note:: If you get a scary looking warning that says something like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" - fear not! This is most likely happening because you have recently reflashed or did an update from pre-v0.3.3, which would cause a change in the key for your device's hostname (e.g. `xxxxxxxx.local`) or IP address (e.g. `192.168.1.x`). The solution is to delete the existing entry from your `known_hosts` file, which is typically located at `~/.ssh/known_hosts`. This should be named in the warning, along with a helpful line number (in case your file is lengthy). + Connecting via PuTTY on Windows -------------------------------