Last night I was using my NAS remotely thtrough twingate, everything was working perfectly. today i tried to access it again and it wasn't responding. i come home to the apt where the NAS sits and I see it is simply off. All i know is that it started a monthly parity check last night while i was using it to stream plex content. Any thoughts on why it might've gone down? I powered it back up and it says parity check was completed with 0 errors. When i open the logs, it only shows me logs starting from the time that i booted it up. How can i check logs from before it went down?/

update - i just noticed that despite telling me the parity check went all good (after i booted up the nas), the system has started doing a parity check all over again, currnetly at 3%

Edited June 2, 20251 yr by salvialight

4 hours ago, salvialight said:

How can i check logs from before it went down?/

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

4 hours ago, salvialight said:

i just noticed that despite telling me the parity check went all good (after i booted up the nas), the system has started doing a parity check all over again, currnetly at 3%

This means that an unclean shutdown occurred.

A server powering itself off is nearly always hardware related. The two most obvious culprits that spring to mind are power issues or thermal issue (CPU overheating). Another (surprisingly frequent) one is a pet accidentally pressing the power button to initiate a shutdown.

8 hours ago, itimpi said:

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

This means that an unclean shutdown occurred.

A server powering itself off is nearly always hardware related. The two most obvious culprits that spring to mind are power issues or thermal issue (CPU overheating). Another (surprisingly frequent) one is a pet accidentally pressing the power button to initiate a shutdown.

OK i just enabled the syslog server. I attached the settings i used to this post as a screen shot. I decided not to mirror to flash, cuz my appdata folder is on my cache drive and it gets backed up daily to the array. so i guess at this point ther's no way for me to find out what happened before that shut down, since syslog was not running? weird that it's not on by default

With the settings in the screenshot your server is just in "Listen" mode. If you want it to record its own syslog messages then you need to put your server's IP address into the Remote Server field.

1 hour ago, salvialight said:

weird that it's not on by default

That is I suspect because there is no sensible default location to write to as everybody seems to have their Unraid set up slightly differently.

On 6/2/2025 at 1:01 PM, itimpi said:

With the settings in the screenshot your server is just in "Listen" mode. If you want it to record its own syslog messages then you need to put your server's IP address into the Remote Server field.

you're right i noticed it has not actually created any file. so if my server ip is 10.0.0.153 i just put that for ip address and i can leave the port as is?

48 minutes ago, salvialight said:

so if my server ip is 10.0.0.153 i just put that for ip address and i can leave the port as is?

Yes