on master help sign in
dist-faq: add workaround for %error-validating failure of OTA

Co-authored-by: Fang <git@fang.io>

commitf75793836411c89cada25399c2b27c9bc1da8e18 authorEdward Amsden <edward@blackriversoft.com> dateThu 30 Sep 2021, 09:23 (5 years ago) parentf2f4f4f
1 file changed+42
content/using/os/dist-faq.md+42
content/using/os/dist-faq.md+42
@@ -87,3 +87,45 @@ See above. Once your peers receive the OTA, you will be able to communicate agai
8787
8888`|ota` will continue to work on ships without the OTA, even if their OTA provider is running the OTA.
8989After the OTA, the `|ota` command is removed and is replaced by the `|install` command.
90+
91+**The OTA failed for me with `%error-validating`.**
92+
93+Tlon is aware of [this issue](https://github.com/urbit/urbit/issues/5271) and is working on a fix.
94+
95+The error will print near the bottom of the output from the failed OTA, and will be similar to:
96+
97+```
98+[ %error-validating
99+ /backup/ship/~littel-wolfur/vim/~2020.12.11..06.50.27..c12d/graph-update
100+]
101+[ %validate-page-fail
102+ /backup/ship/~littel-wolfur/vim/~2020.12.11..06.50.27..c12d/graph-update
103+ %from
104+ %graph-update
105+]
106+```
107+
108+This is caused by some leftover backup files from a previous migration for which Clay no longer has marks.
109+
110+As a workaround: you can remove these files and retry the OTA:
111+
112+dojo:
113+
114+```
115+|unmount %home`
116+|mount /=home=`
117+```
118+
119+bash:
120+
121+```bash
122+rm -r your-ship/home/backup`
123+```
124+
125+dojo:
126+
127+```
128+|commit %home
129+|ota (sein:title our now our) %kids
130+```
131+