summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorPjotr Prins2021-09-29 15:44:59 +0200
committerPjotr Prins2021-09-29 15:44:59 +0200
commitf5bea2cc2b35eef7b7424ab18d43200707a9889c (patch)
tree1340bb8dd60a4fa82fe1eeef118914b6bd761588 /issues
parent6dd9b703769b05a057596c2e919092a14b683758 (diff)
downloadgn-gemtext-f5bea2cc2b35eef7b7424ab18d43200707a9889c.tar.gz
Tux01 crash
Diffstat (limited to 'issues')
-rw-r--r--issues/systems/tux01-hard-disk-crash.gmi16
1 files changed, 16 insertions, 0 deletions
diff --git a/issues/systems/tux01-hard-disk-crash.gmi b/issues/systems/tux01-hard-disk-crash.gmi
new file mode 100644
index 0000000..ea95a56
--- /dev/null
+++ b/issues/systems/tux01-hard-disk-crash.gmi
@@ -0,0 +1,16 @@
+# Tux01 hard disk crash
+
+One spinning disk crashed on Sept. 26th. It was used for Arthur's HOME and backups.
+
+# Tags
+
+* assigned: pjotrp
+* priority: medium
+
+# Info
+
+The system is still up, so it is not too urgent. First step is to recover the backup system. The rsync backups are in an inconsistent state, fortunately we have a BORG_BORG backup (a backup of the backup):
+
+```
+epysode:/export/backup$ borg extract --progress borg-borg::BORG_BORG_TUX01-Saturday-20210925-07:12:04
+```