aex.perez
Very Senior Member
Post Mortem, sort of
Well today things all running as they should after some settings I missed, which were dirving me nuts.
WiFi settings on the Router
Did not disable 802.11b
Had the wrong SSID shared key for the main/smartconnect SSID
didn't notice as I use the SmartConnect SSID as the guest network and the guest networks 2.4Ghz and 5Ghz, as the actual internal SSID's
Syslog
Scribe, node logging, uiscribe now all setup again, working, and updated.
One node was logging correctly, the other was not (wouldn't even log logger) syslogd was failing to run correctly.
Message_loglevel and log_level were set wrong/too verbose on the nodes which I can only assume was part of the issue.
Both nodes had the same settings (for the stuff that matters).
Both filters on the router supporting the nodes were identical (except names, so each has there own log).
USB
Failure, not sure it was actually a failure of the USB as jffs, nvram and the USB were all impacted/corrupted and kept geting corrupted even after a restore (BACKUPMON)
Only after a Hardware reset (WPS reset) on the router, and starting from scratch (did the nodes as well to be safe) did it all start to operationally recover
What I thought was a failed USB, as nothing would load or run, and every script was resporting a locked file and claimed to be already running, is today working perfectly as much as you can say a USB works perfectly and has been for a few weeks now.
Router is on a UPS, fed by a good filtering power strip, nodes just plugged in but nothing else on the same circuits as those devices have had an issue, and really only the router went nuts.
Getting to SSD was a bonus, and has been very stable and the router just a bit more responsive
Having run @JGrana's MTD Checker tool on the router and nodes every few days just to be sure everything is stable in that regard, has shown it's all good across all three devices.
Lessons learned.
Even with backups, have a good retention schedule.
Even with backups have a secondary target, especially on the router. I have a secondary USB (FAT) targert that I can mount on the PC or Laptop and share to recover from there, if the NAS becomes unavailable when the router fails (especially if configured to support 802.3ad)
Document your setup parameters, because if all else fails and you have to start from scratch, you will inevitably forget something to get you back were you were.
And if/when you upgrade you router, and or move to a different code base (like 3004 to 3006) that will be very handy to at least get you started on on solid ground before making additional changes to take advantage of the new HW and or Software/Firmware.
VPNs
Mostly setup. Will likely sunset OpenVPN and stick to IPSEC (native to the Win11 Laptop, ease of use) and WireGuard (speed)
Back to low to very low maintenence mode now that its all done or at least normalcy is achived.
Well today things all running as they should after some settings I missed, which were dirving me nuts.
WiFi settings on the Router
Did not disable 802.11b
Had the wrong SSID shared key for the main/smartconnect SSID

Syslog
Scribe, node logging, uiscribe now all setup again, working, and updated.
One node was logging correctly, the other was not (wouldn't even log logger) syslogd was failing to run correctly.
Message_loglevel and log_level were set wrong/too verbose on the nodes which I can only assume was part of the issue.
Both nodes had the same settings (for the stuff that matters).
Both filters on the router supporting the nodes were identical (except names, so each has there own log).
USB
Failure, not sure it was actually a failure of the USB as jffs, nvram and the USB were all impacted/corrupted and kept geting corrupted even after a restore (BACKUPMON)
Only after a Hardware reset (WPS reset) on the router, and starting from scratch (did the nodes as well to be safe) did it all start to operationally recover
What I thought was a failed USB, as nothing would load or run, and every script was resporting a locked file and claimed to be already running, is today working perfectly as much as you can say a USB works perfectly and has been for a few weeks now.
Router is on a UPS, fed by a good filtering power strip, nodes just plugged in but nothing else on the same circuits as those devices have had an issue, and really only the router went nuts.
Getting to SSD was a bonus, and has been very stable and the router just a bit more responsive
Having run @JGrana's MTD Checker tool on the router and nodes every few days just to be sure everything is stable in that regard, has shown it's all good across all three devices.
Lessons learned.
Even with backups, have a good retention schedule.
Even with backups have a secondary target, especially on the router. I have a secondary USB (FAT) targert that I can mount on the PC or Laptop and share to recover from there, if the NAS becomes unavailable when the router fails (especially if configured to support 802.3ad)
Document your setup parameters, because if all else fails and you have to start from scratch, you will inevitably forget something to get you back were you were.
And if/when you upgrade you router, and or move to a different code base (like 3004 to 3006) that will be very handy to at least get you started on on solid ground before making additional changes to take advantage of the new HW and or Software/Firmware.
VPNs
Mostly setup. Will likely sunset OpenVPN and stick to IPSEC (native to the Win11 Laptop, ease of use) and WireGuard (speed)
Back to low to very low maintenence mode now that its all done or at least normalcy is achived.

Last edited: