I applied a patch to the RAID controller on the NAS a few days ago.<\/p>\n
Twelve hours later. part way through a volume sync, the RAID controller got its knickers in a right knot.<\/p>\n
As a result of its panic-fest, the RAID controller gobbled up 100% of the available RAM and then assumed 100% of the CPU.<\/p>\n
These unplanned events effectively locked up everything behind my router\/primary firewall.<\/p>\n
The NAS squeaked out an email to me that it was in trouble.<\/p>\n
I remote-accessed the NAS, intending\u00a0to kill the rogue processes, but although I could authenticate on to it, the device had insufficient processing power\/CPU to allow me to step in and intervene.<\/p>\n
When I got home, I powered off the NAS and booted the device back up, which restored everything once more.<\/p>\n
After another volume sync (I have the NAS set up as a RAIDed device), I performed a controlled shutdown and restart.<\/p>\n
This brought everything back up correctly, after the previous power-off\/start up.<\/p>\n
With hindsight (I have 20\/20 hindsight sometimes), I should have performed a controlled shutdown\/restart after applying the patch to the RAID controller.<\/p>\n
But I didn’t.<\/p>\n
Oh well, I’m learning.<\/p>\n
If you’re interested in the architecture, this is how things currently look:<\/p>\n
Hardware:
\nThe NAS has 2x 1Tb discs.
\nServer #1 has 4x 2Tb discs
\nServer #2 has 4x 2Tb discs<\/p>\n
I applied a patch to the RAID controller on the NAS a few days ago. Twelve hours later. part way through a volume sync, the RAID controller got its knickers in a right knot. As a result of its panic-fest, the RAID controller gobbled up 100% of the available RAM \u2026 Continue reading ![\"Drawing2\"](\"https:\/\/ahorseforonebin.co.uk\/wp-content\/uploads\/2013\/12\/Drawing2.jpg\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"