Jump to content
dlandon

Dealing with unclean shutdowns

62 posts in this topic Last Reply

Recommended Posts

47 minutes ago, jonathanm said:

That sounds like something @limetech ought to at least investigate.

 

Thanks. I thought I'd ask because it seems so obvious and repeatable that I thought it might just be a "feature". I'd file a bug report if I could. I'm getting a 404 error at the moment though - already mentioned in the "Welcome to unraid.net" thread.

Share this post


Link to post

Thanks for this guide there was some information that I didn't know for example if you have a terminal window open what causes a unclean shutdown. 

Share this post


Link to post
7 hours ago, MvL said:

terminal window open what causes a unclean shutdown. 

only if it's working directory is /mnt/user/...

 

But you can also install the StopShell app to have it close out any terminal sessions during a shutdown procedure

Share this post


Link to post

I've had to do a couple "power off shutdowns". A problem with the ethernet port of the supermicro mobo, rendered

the server unavailable via the normal admin webpage or SSH/telnet. It's a big Norco array of 20 disks, so at some point

I just had to "flip the switch". A few other attempts to re-establish connectivity similarly failed.

 

I then did a mobo replacement, so now the ethernet config file for the unraid kernel needs to be changed (I'll use nano on a raspberry pi to

do this-reset to default on the USB stick). What should I do or expect when the machine boots? I don't have backups, so if the array comes

up damaged, I don't want to do  more damage. What are the recommendations for recovering raid integrity at this point?

Share this post


Link to post

It should just boot up and recognize your disks assuming your flash drive is OK. You can just delete config/network.cfg and it will create a new default one. You might edit config/disk.cfg to turn autostart off just so you can check the assignments before starting the array.

Share this post


Link to post

Perhaps I am missing a big piece of the issue of an unclean shutdown.

 

A power failure will cause an unclean shutdown. This will create massive parity errors.

 

Does that mean if I lose a data drive in a power failure and parity is now erroneous, I won't be able to reconstruct my damage drive?

Share this post


Link to post
14 minutes ago, tunetyme said:

Perhaps I am missing a big piece of the issue of an unclean shutdown.

 

A power failure will cause an unclean shutdown. This will create massive parity errors.

 

Does that mean if I lose a data drive in a power failure and parity is now erroneous, I won't be able to reconstruct my damage drive?

It depends on the power failure.    Typically it will only be a few and they are likely to refer to any write in progress at the time of failure.

Share this post


Link to post
12 minutes ago, RxLord said:

Please help...I am having issues with my Unraid system and unclean shutdowns.  I am not a computer programmer. Any help or recommendations are greatly appreciated. Thanks in advance.

tower-diagnostics-20190803-0233.zip 180.6 kB · 0 downloads

Please describe in detail exactly what the circumstances are that involved in your unclean shutdowns.  (Server 'crashing', normal attempt to shutdown the server, etc.) 

Share this post


Link to post

Server is rebooting/crashing on it own. if I look at my terminal it says "kernel panic not syncing" then i goes thru the normal reboot process. When it reboot I get the unclean error so I reboot the system and restart the array. If I don't reboot the system, parity check will start and it reboots again without completing the parity check.

Share this post


Link to post
7 hours ago, RxLord said:

Server is rebooting/crashing on it own. if I look at my terminal it says "kernel panic not syncing" then i goes thru the normal reboot process. When it reboot I get the unclean error so I reboot the system and restart the array. If I don't reboot the system, parity check will start and it reboots again without completing the parity check.

You are running 6.7.2 which has a new feature for  use in cases like this called "Syslog Server".  To use it go to   Settings   >>   Syslog Server   and Enable 'Mirror syslog to flash:'.    (The 'Help' feature in the GUI will provide you with more information.)  That file may provide more information to the real Gurus.  Did you do any hardware upgrades just before this all started?  Any other system  configuration or modifications?

Share this post


Link to post

No new hardware upgrades. Only thing new are a couple of dockers. I currently just have my Plex docker started and it has been running with not problems. Going to slowly add my dockers back and see if this is the problem.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.