diff options
author | mail_redacted_for_web | 2022-03-24 17:37:10 +0100 |
---|---|---|
committer | mail_redacted_for_web | 2022-03-24 17:37:10 +0100 |
commit | c58a64be77d4fe0640616851af294300d60233c4 (patch) | |
tree | ca6b38f3dae6a1a599076ae966f4bbb0a4f0fe3c /erase-broken-modules/README.md | |
download | mikrotik-fixes-c58a64be77d4fe0640616851af294300d60233c4.tar.bz2 |
InComm, +wiper
Diffstat (limited to 'erase-broken-modules/README.md')
-rw-r--r-- | erase-broken-modules/README.md | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/erase-broken-modules/README.md b/erase-broken-modules/README.md new file mode 100644 index 0000000..32a993d --- /dev/null +++ b/erase-broken-modules/README.md @@ -0,0 +1,18 @@ +# Scenario + +For whatever reason, you end up with a MikroTīk device with broken modules. Whatever you do, they +will not disappear. Also, in my scenario – the user module was broken – one of two devices never applied +any update, and the other even did not remember most changes. + +The solution is to: + +1. Uninstall all packages that can be uninstalled (except for system) +1. Disable all packages that cannot be uninstalled (mostly because they are bundled) +1. Place an update to the device's root +1. Reboot + +You will then end up with an updated device, no other modules installed, and in 2/2 cases for me +all setting were still present. Of course a backup prior to this is still highly recommended. + +This folder contains an example rsc file managing the actions on the device and an example script +copying the update and firing the rsc. |