New Unraid Build and in the process of fine tuning and learning.  I have two issues.

The first is that several times now when I go to view my shared on my Mac I receive the following error:



If I restart my Mac, it still won't let me log in.  However, if I reboot Unraid, it does. I'm the only user. It worked fine before. I'm not sure why I'm receiving this error. 

So this morning, it happened again for the second time and I rebooted Unraid. But this time, I received the error
 

Event: Parity Check Tuning
Subject: [FILESERVER] Unclean shutdown detected
Importance: alert

And now it's doing a parity check. 

I've attached the diagnostics.

fileserver-diagnostics-20240517-0726.zip

8 minutes ago, csimpson said:

Event: Parity Check Tuning
Subject: [FILESERVER] Unclean shutdown detected
Importance: alert

That is just the plugin notifying you that this has happened.   it was also reported at the base Unraid level in the syslog.  When you get an unclean shutdown an automatic parity check is started.

May 17 07:18:30 fileserver emhttpd: unclean shutdown detected

Did you have to force a shutdown so you could reboot?

 

If you continue to get unexpected unclean shutdowns then you may find this section useful in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. 

All I did was click "reboot."

 

I'm looking through the documentation. Nothing seemed to be running abnormally. UPS was fine, no power drop. I tried rebooting so I could connect to the share again because of the "won't allow additional users to login" error from my Mac.
 

Is there a process that I should follow? Two of the drives were spun down (disk settings: set to spin down after an hour) at the time including the parity drive. Do I need to make sure drives are spun up to do a reboot or does Unraid make sure that when a reboot is done, everything is where it should be?

 

Do I need to stop the array before doing a reboot or does Unraid do then when rebooting?

Edited May 17, 20242 yr by csimpson

6 hours ago, csimpson said:

Do I need to stop the array before doing a reboot or does Unraid do then when rebooting?

Unraid will do this, but you need to make sure your system can successfully stop the array before the timeout kicks in.   The documentation mentions doing this.

2 hours ago, itimpi said:

Unraid will do this, but you need to make sure your system can successfully stop the array before the timeout kicks in.   The documentation mentions doing this.

Yes, I switched it to 420 seconds rather than the default 90 it was at.  I don't know why it would have taken so long as my setup isn't very complex.  But hopefully, that solves it.