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.

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. 

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

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?

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.

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?

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.

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

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.) 

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.

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?

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.

5 hours ago, mc_866 said:

Ryzen 1600

You should post your diagnostics instead of just syslog. Tools - Diagnostics, attach complete ZIP file to your NEXT post.

14 minutes ago, mc_866 said:

Full zip attached.

Have you done memtest? Be sure to check out the link I gave.

it was an unclean shutdown in this case, and most likely due to having a too short timeout set.

i did a normal reboot via the Gui on unraid and i got the warning

 

Parity Check Tuning
Automatic unRaid Non-Correcting Parity Check will be started
1629649753
Unclean shutdown detected
warning

 

i dont have any VM currently running they are off and only 6 dockers online.

55 minutes ago, KoNeko said:

i did a normal reboot via the Gui on unraid and i got the warning

 

Parity Check Tuning
Automatic unRaid Non-Correcting Parity Check will be started
1629649753
Unclean shutdown detected
warning

 

i dont have any VM currently running they are off and only 6 dockers online.

did an automatic check actually start?    The reason I am asking is that in testing I occasionally get the plugin outputting that warning and the automatic check does not actually start.    I have not identified the exact conditions where the plugin thinks it was an unclean shutdown but UnRaid decides it was not.

3 minutes ago, itimpi said:

did an automatic check actually start?    The reason I am asking is that in testing I occasionally get the plugin outputting that warning and the automatic check does not actually start.    I have not identified the exact conditions where the plugin thinks it was an unclean shutdown but UnRaid decides it was not.

yes the partiy check did start automaticly.

1 minute ago, KoNeko said:

yes the partiy check did start automaticly.

Thanks for letting me know.

 

You should only get an unclean shutdown if one of the shutdown timeouts trigger.  I would suggest you 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.

13 minutes ago, itimpi said:

Thanks for letting me know.

 

You should only get an unclean shutdown if one of the shutdown timeouts trigger.  I would suggest you 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.

i did increase the timing somewhat but that is a good idea to time that.

 

Will do that once the check is done in a day or 2 or so

 

1 minute ago, KoNeko said:

i did increase the timing somewhat but that is a good idea to time that.

 

Will do that once the check is done in a day or 2 or so

 

 

My experience is that any errors in such a situation as yours tend to be at the start of the parity check so it is not always necessary to run it to the end.

 

Hello there

 

i have some major problem with my new server setup.

server in GUI mode and successfully setup two win10 vms with gpu passtrough.

3 external USB to NVME drives out of two is on the same controller and passtrough to Win10 vm #1 and one ext drive is showed in unraid as unassigned device with the "pass" option enabled and used as a vitrual drive on the Win10 VM #2.

 

at rebooting first the reboot splash screen appears time counting until localhost is losing the connecting then nothing happends. 

i can still access the terminal window and using command "shutdown -t 5 now" forces the server to action but only until its trying to allocate the unraid usb flash drive and then nothing, forceing me to hard reset the server everytime.

 

can the problem be with the external drive on the controller managed by unraid as rebooting the server with that drive disconnected works?

 

issue also posted for support in the unnassigned devices plugin forum

 

very much apprecietad if someone can have a look at the diagnostic file 

galactica-diagnostics-20210831-1030.zip

Edited August 31, 20214 yr by TIE Fighter

7 minutes ago, TIE Fighter said:

hard reset the server

What have you already tried that was discussed in this thread you have posted in?

On 8/31/2021 at 3:51 PM, trurl said:

What have you already tried that was discussed in this thread you have posted in?

at this moment manually before soft reboot the server

- stopped the two VM:s before rebooting.

- rebooting with external nvme to usb drive attached and unplugged 

- unmount smb shares

- stopped dockers

- increased the timer in  Settings->Disk Settings->Shutdown time-out to: 420s

- increased VM shutdown time-out: 300s

 

at the moment i am doing a Parity-Sync / data rebuild from this morning when i have to replace an old data drive so i am unable to try to reboot at the moment.

Edited September 1, 20214 yr by TIE Fighter

@trurl 

parity rebuild completed manually stopped the vms and dockers.

one docker was not possible to stop and forced the array to not be put offline.

for future knowledge it was a docker that i added from github rep that manage the HBA Card Adaptec 71605.

i only use this to monitor the temp of the card.

hard rebooted and stopped the docker from autostart.

 

now been trying a cuple of shutdown and reboot attempts and everything seems ok.

 

cheers