Start9/documentation
2
0
Fork 0
mirror of https://github.com/Start9Labs/documentation.git synced 2026-03-26 02:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Maint/misc improvements (#310)

Browse Source 
* 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 <bitcoinmechanicca@protonmail.com>
This commit is contained in:
kn0wmad
2023-02-23 16:02:29 +00:00
committed by GitHub
parent 318243903e
commit 0565df149c
3 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
site/source/user-manual/backups/backup-restore.rst
View File

@@ -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<initial-setup>`, select "Recover."

2
site/source/user-manual/backups/backup-setup/backup-physical.rst
View File

@@ -11,7 +11,7 @@ Backup to Physical Drive
The recommended method of backup (including with external drives) is to setup a :ref:`Network Folder<backup>` 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``.

2
site/source/user-manual/ssh.rst
View File

@@ -87,6 +87,8 @@ Connecting via CLI (Linux/Mac)
Replacing ``<LAN URL>`` 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
-------------------------------