9 hours ago, sirhotness said:

im glad i found this topic.  thank you for posting this.  i am going to try this as i get intermittent unclean shutdowns and then i have to start the array back up which does a parity check.  i am going to attach my syslog, is this helpful?  i am new so i am wondering if i need to do anything else to prevent this from happening in the future.

 

thank you for all your help as it is much appreciated.

Please don't post about the same thing in multiple threads. It makes it impossible to coordinate replies.

 

Since this user already posted about this on another thread and received a reply, please go there if you have anything to add:

 

 

Hello  all! This is quite a convenient thread, though I didn't find the answer to my question so I hope I'm not asking the same thing as somebody else.

 

I experienced an unclean shutdown due to a power outage, and when the power returned and the server came back online, it mounted the disks and began a parity check automatically (as expected).

 

I would like to ask - when starting a parity check manually, the "write corrections to parity" is ticked by default. When the parity check starts automatically, is it starting with this ticked or unticked? How do I found out and control this behaviour?

 

Furthermore, I am under the impression that unless I want to correct the parity data, I should untick this option when doing parity checks. This is so that any corrupt data on the data disks can be fixed using the parity data. As this is likely when there is an unexpected power outage, I believe that it would be proper practice to perform the automatic parity check without writing corrections to parity. Is my assessment correct?

 

Thank you all!

 

24 minutes ago, cybersteel8 said:

Is my assessment correct?

Unclean shutdown parity check is non-correcting

4 hours ago, trurl said:

Unclean shutdown parity check is non-correcting

Ah, so the answer to my first question is that it is running as if it was unticked, which is the behaviour I want. So there's is nothing I need to change! Thank you!

7 hours ago, cybersteel8 said:

Ah, so the answer to my first question is that it is running as if it was unticked, which is the behaviour I want. So there's is nothing I need to change! Thank you!

You should also check that regular scheduled parity checks are set to be non-correcting.

My unraid was off for a few weeks, yesterday I have installed a new HDDs to rebuild (create a new) array and suddenly I started receiving unclean shutdowns. Before it was stable, no issues running for a month or more.  Installed HDDs are a brand Ironwolf NAS 4TB, SMART didn't report any issues.

 

Can you please take a look at my logs and advise what could be the reason of my issues?

unraid-diagnostics-20211116-1308.zip

2 hours ago, ataman said:

unclean shutdowns

Is it crashing, or will it just not shut down cleanly?

Well, difficult to say. My server is running headless thus I don't know exactly what's happening there. But when I'm logging in after such a random  'restart' I see that parity check is in progress. Also in the Fix common problems I see:

 

Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged

 

EDIT:

 

I have connected a GPU to see what's happening with unraid once it's crashed but there's nothing displayed on the screen. Also now the system doesn't reboot itself I need to use power button to turn off and on again.

 

I have configured a syslog however not sure if there's anything interesting here.

syslog

Edited November 17, 20214 yr by ataman

On 11/16/2021 at 10:09 AM, ataman said:

syslog however not sure if there's anything interesting here

Any idea what this is about?

192.168.1.222	Nov 17 12:34:50	unraid	cron	notice	crond[1910]	time disparity of 440 minutes detected

440 minutes = 7 hours 20 minutes

 

Not clear there was any reboot during that syslog. Can you get that syslog server to put dates on the timestamps? Or just send it to somewhere on Unraid, it will look more like the syslogs we are familiar with.

6 hours ago, trurl said:

Or just send it to somewhere on Unraid

 

I've managed to save the logs to the flash drive. I brought the server next to my desk and connected to the screen so I can better troubleshoot it. 

 

Another restart/unclean shutdown happened around 22:13. What is interested that server didn't reboot, it just stopped responding in the WebGui (or ping, shares etc). On the connected screen I was still able to see the boot up lines with flashing unraid login:

 

After 2 or 3 minutes, I was able to login to the WebGui again, and as always I saw the message about unclean shutdown and parity-check in progress..

 

Is it possible that it's more a software issue or maybe flash drive which is failing? 

syslog_flash.txt

9 minutes ago, ataman said:

a software issue or maybe flash drive which is failing? 

I don't think either of those would cause a reboot.

 

Have you done memtest?

 

Also

 

1 minute ago, trurl said:

Have you done memtest?

 

Yes I did just today, passed 2 times.

 

Also checked the Ryzen thread before. What is interesting that unraid was working fine for a couple of months and just after installation of new HDDs and applying "New config" the problem started.

 

btw. is it normall to see below lines in the logs? I've noticed them each time when unraid doesn't respond

 

192.168.1.222	Nov 17 22:14:21	unraid	user	info	emhttpd	shcmd (38): /etc/rc.d/rc.samba restart
192.168.1.222	Nov 17 22:14:21	unraid	daemon	err	nmbd[4207]	[2021/11/17 22:14:21.962095,  0] ../../source3/nmbd/nmbd.c:59(terminate)
192.168.1.222	Nov 17 22:14:21	unraid	daemon	err	nmbd[4207]	  Got SIGTERM: going down...
192.168.1.222	Nov 17 22:14:21	unraid	daemon	err	winbindd[4217]	[2021/11/17 22:14:21.962147,  0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler)
192.168.1.222	Nov 17 22:14:21	unraid	daemon	err	winbindd[4217]	  Got sig[15] terminate (is_parent=1)

 

Have you read this:

 

 https://forums.unraid.net/topic/76832-ram-for-ryzen-7-solved/?tab=comments#comment-709502

 

As I Read your diagnostics, your four chips are running at 2400.

Edited November 17, 20214 yr by Frank1940

16 minutes ago, Frank1940 said:

As I Read your diagnostics, your four chips are running at 2400.

 

I have Ryzen 7 1700 which is 1st gen as I understand. I have 2 chips installed, so they should be running at 2400 or did I understand it wrong?

 

 

50 minutes ago, ataman said:

 

I have Ryzen 7 1700 which is 1st gen as I understand. I have 2 chips installed, so they should be running at 2400 or did I understand it wrong?

 

 

I made a mistake when looking at your diagnostics.   Since you are running a first gen Ryzen chip, might we assume that you have gone through the BIOS settings to ensure stability with Unraid.

What should the Disk Settings be set to if you do not have VM Manager enabled? 

1 hour ago, dchamb said:

What should the Disk Settings be set to if you do not have VM Manager enabled? 

On 8/22/2021 at 1:54 PM, itimpi said:

try hitting the button to Stop the array and time how long it takes.   You need to make sure the Disk Settings -> shutdown timeout setting is longer than that.

  

 

16 hours ago, trurl said:

  

 

Thanks! 

Does anyone know what would cause an unclean shutdown when shutting down with the array stopped?

15 minutes ago, gamerkonks said:

Does anyone know what would cause an unclean shutdown when shutting down with the array stopped?

That sounds like a bug although not at all clear what could trigger it.  Maybe the flash drive had dropped offline so that Unraid could not update the array status on it to say it was successfully stopped?

7 hours ago, itimpi said:

Maybe the flash drive had dropped offline so that Unraid could not update the array status on it to say it was successfully stopped?

This seems likely.

17 hours ago, itimpi said:

That sounds like a bug although not at all clear what could trigger it.  Maybe the flash drive had dropped offline so that Unraid could not update the array status on it to say it was successfully stopped?

That must be it.

I did get an error saying the flash drive was read only last time I booted, but it seems fine now.

Hey guys,

I've been dealing with unclean shutdowns for a while and I'm not sure why. In all honesty, I haven't really had the time to deal with it.

However this last time it caused one of my SSDs xfs to become corrupt and it ended up being my plex sdd, so now I'm making time.

I have attached a diagnostics file (that is where I saw which SSD is corrupted - sdu), but I have yet to find the root of the problem.

 

To be clear, I've fixed the SSD drive and plex is back up and running, fortunately it wasn't the DB that was corrupted, however I REALLY want to avoid this again.

 

Thank you.

 

Any help is greatly appreciated.

tower-diagnostics-20220120-0514.zip

When you get a clean shutdown, the array stops first, then Unraid updates the flash drive to indicate the array had stopped, before shutting down. If for some reason that doesn't happen, you get an unclean shutdown.

 

If you do a hard powerdown, or if the shutdown timeout expires before the array stops, then the flash drive doesn't get updated.

 

Or a problem with flash prevents it from being updated, such as readonly or disconnected.

4 hours ago, trurl said:

When you get a clean shutdown, the array stops first, then Unraid updates the flash drive to indicate the array had stopped, before shutting down. If for some reason that doesn't happen, you get an unclean shutdown.

 

If you do a hard powerdown, or if the shutdown timeout expires before the array stops, then the flash drive doesn't get updated.

 

Or a problem with flash prevents it from being updated, such as readonly or disconnected.

 

By looking at my diagnostics, is there any way to see what exactly caused the error?

I'm almost certain it's not a problem with the flash drive being read only and definitely not disconnected (at least physically).