J_Strong

God, I can’t actually definitively say… I added the disk around 5 months ago and didn’t check the server uptime prior to updating last night! Before anything else then I’ll attempt to run that command you suggested, reboot and advise results when I’m back home later today. Thanks for the suggestion!

Nope, disk had been in the array for array for month, about 40% and had valid party. Browisng about, it seems people have had success by creating a New Config, then starting to array so the problem drive rebuilds from Partiy. The data is replaceable so think I will attempt that and report back on progress….

All working fine on v6.12.6 and pulled the trigger on updating to v6.12.8. OS has booted up fine but array was not started with the below error: Not changed any hardware and clearly as per the screenshot, that is the correct disk for that slot as the expected vs actual S/N's match. Downgraded and no joy. I've therefore upgraded back to v6.12.8 and again, no joy. Diagnostics attached. Any suggestions on how I can resolve this? unraid-server-diagnostics-20240217-2136.zip

It's happened a few times now so decided to try and look into it but my Plex stream cut out, all Homebridge devices went offline and when trying to open the Unraid web ui, I just get a timeout but server does still respond to pings. Checking my syslog, at the time when the system froze I can see: Feb 4 16:40:04 UNRAID-SERVER unraid-api[8425]: ⚠️ Caught exception: Something went wrong. cron reached maximum iterations.#012#011#011#011#011#011#011Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string#012#011#011#011#011#011#011Time Zone: "" - Cron String: 0 * * * * * - UTC offset: +00:00 - current Date: Sun Feb 04 2024 16:39:53 GMT+0000 Feb 4 16:40:33 UNRAID-SERVER unraid-api[8425]: ⚠️ UNRAID API crashed with exit code 1 Feb 4 16:45:34 UNRAID-SERVER unraid-api[13227]: ✔️ UNRAID API started successfully! The system became responsive again 5 minutes late, at the time when the syslog logged the unraid-api successfully restarted. Currently I'm about to just bin off the Unraid Connect as it's have a negative impact on system reliability. My Diagnostics is attached but it sound like the issue needs to be raised on Cron's Github? Is anyone else having the same issue or anything I could try to stop this from happening? unraid-server-diagnostics-20240204-1711.zip

Ah yes, my bad. Updated the Unraid Connect plugin and post reboot, things look good again. Thanks!

Hey... Other forums posts state to post Diagnostics, if you ever see a syslog is getting full message, which I am seeing: Jan 14 14:52:16 UNRAID-SERVER root: Fix Common Problems: Warning: /var/log is getting full (currently 63 % used) Quickly checking the syslog in my Diagnostics .zip, I'm seeing a lot of: Jan 5 19:54:42 UNRAID-SERVER nginx: 2024/01/05 19:54:42 [crit] 7332#7332: ngx_slab_alloc() failed: no memory Jan 5 19:54:42 UNRAID-SERVER nginx: 2024/01/05 19:54:42 [error] 7332#7332: shpool alloc failed Jan 5 19:54:42 UNRAID-SERVER nginx: 2024/01/05 19:54:42 [error] 7332#7332: nchan: Out of shared memory while allocating message of size 14511. Increase nchan_max_reserved_memory. Jan 5 19:54:42 UNRAID-SERVER nginx: 2024/01/05 19:54:42 [error] 7332#7332: *2963538 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jan 5 19:54:42 UNRAID-SERVER nginx: 2024/01/05 19:54:42 [error] 7332#7332: MEMSTORE:00: can't create shared message for channel /disks Literally have no idea what that means other than potentially my system has maxed out on available RAM during that time or something else I should be concerned about? Any help would be appreciated! Thanks. James. unraid-server-diagnostics-20240114-1454.zip