Parity check at each array stop or system reboot

[M4st3r]

Hello, I've just rebuilt my system using a Ryzen 3700x and everything went fine until I've changed my USB flash drive (with the old one I've tested multiple times reboot and stop array without any issue): now when I try to stop or reboot my system (through GUI or SSH), my server invoke everytime a parity check upon restart.

What do you need to inspect this issue?

Thanks!

 

unraid-server-diagnostics-20200201-1128.zip

Edited February 1, 2020 by M4st3r

[M4st3r]

I've just set VM-shutdown time to 300sec and disk time shutdown to 420sec, and set under the Tips&Tweaks plugin to kill ssh,bash before array shutdown...but without success.

Could it be the change of the USB flash disk?

[JorgeB]

Parity check on boot is because of this:

 

Feb  1 11:22:35 unRAID-server emhttpd: unclean shutdown detected

 

You need to find out why the array isn't shutting down cleanly, there should be diags saved to flash (logs folder) if a shutdown is forced, and they might provide a clue on the problem.

[M4st3r]

28 minutes ago, johnnie.black said:

Parity check on boot is because of this:

 

Feb  1 11:22:35 unRAID-server emhttpd: unclean shutdown detected

 

You need to find out why the array isn't shutting down cleanly, there should be diags saved to flash (logs folder) if a shutdown is forced, and they might provide a clue on the problem.

How??

In my log folder I found a diagnostic done before the one posted here...

 

Now I'm facing the problem getting a new replacement key for the USB flash drive...so I cannot test a new change (with an indentical one Kingston Datatraveler 2)

syslog.txt

Edited February 1, 2020 by M4st3r

[M4st3r]

Maybe this one ?

 

 11:06:56 unRAID-server root: rmdir: failed to remove '/mnt/user': Device or resource busy
Jan 30 11:06:56 unRAID-server emhttpd: shcmd (3074): exit status: 1
Jan 30 11:06:56 unRAID-server emhttpd: shcmd (3076): /usr/local/sbin/update_cron
Jan 30 11:06:56 unRAID-server emhttpd: Retry unmounting user share(s)...

[JorgeB]

Most likely something was still using the array, you should post the saved diags.

 

You can also try to stop the array, to see if it's stopping and how long it's taking to stop, if the shutdown timeout is less than that it will result in an unclean shutdown.

 

 

[M4st3r]

Ive changed the USB port for the flash drive and....the problem seems to be gone

But...is it normal that when I stop and then restart the array, the VMs still off either it they are set to 'autostart'?

 

I think I'm facing a strange problem

[JorgeB]

19 minutes ago, M4st3r said:

the VMs still off either it they are set to 'autostart'?

I believe currently auto-start only works if the array is also auto-started at boot, and only for that first start, not sure if by design or not.

[M4st3r]

1 hour ago, johnnie.black said:

I believe currently auto-start only works if the array is also auto-started at boot, and only for that first start, not sure if by design or not.

Ok...when I reboot the whole server, the VMs are currently auto starting, but I'm quite sure that when I stop and then restart the array, a few days before, the VMs did the same...