after reboot (clean shut down ) the VM manager was automatically set to No and the VM engine was disabled, I had to restart it manually. Reboor does not fix it. Please help. diagnostics attached.

Thank you

tower-diagnostics-20211203-1026.zip

1 minute ago, zavanilli said:

after reboot (clean shut down )

 

Dec  3 10:22:20 Tower emhttpd: unclean shutdown detected

 

thanks for propmpt response

I initiated the reboot from the GUI, do you see anything that may indicate why the system considered it unclean?

the other question, is it an expected behavior that after an unclean shutdown the VM engine will be disabled on reboot?

Thank you for your time

Unclean shutdown doesn't change any of your settings.

 

Unclean shutdown ultimately is caused by the array stopped/started status not being written to the flash drive. This can happen if the array doesn't stop before shutdown because something prevents it, or loss of power. It can also happen if the flash drive can't be written due to corruption or disconnect. Since the setting you made didn't seem to stick after reboot that suggests flash couldn't be written for some reason.

 

Are you booting from USB2 port (recommended)?

 

 

8 minutes ago, zavanilli said:

is it an expected behavior that after an unclean shutdown the VM engine will be disabled on reboot?

IIRC it's a known issue.

 

Shutdown from the GUI can be unclean if one of the timeouts is reached, first one for VMs then the general timeout, when there's one the diags will be saved in the flash drive, logs folder, those can show what the problem is.

1 minute ago, JorgeB said:

IIRC it's a known issue.

Yep:

 

5 minutes ago, JorgeB said:

IIRC it's a known issue.

 

Shutdown from the GUI can be unclean if one of the timeouts is reached, first one for VMs then the general timeout, when there's one the diags will be saved in the flash drive, logs folder, those can show what the problem is.

should I increase the timeour before shutdown in the VM settings?

9 minutes ago, trurl said:

Unclean shutdown doesn't change any of your settings.

 

Unclean shutdown ultimately is caused by the array stopped/started status not being written to the flash drive. This can happen if the array doesn't stop before shutdown because something prevents it, or loss of power. It can also happen if the flash drive can't be written due to corruption or disconnect. Since the setting you made didn't seem to stick after reboot that suggests flash couldn't be written for some reason.

 

Are you booting from USB2 port (recommended)?

 

 

Yes USB 2.0 port

how do I figure out if the flash couldnt be written?

2 minutes ago, zavanilli said:

Yes USB 2.0 port

how do I figure out if the flash couldnt be written?

ErrorWarningSystemArray

Dec 3 10:20:56 Tower kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB)
Dec 3 10:20:56 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec 3 10:20:56 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Dec 3 10:20:56 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 3 10:20:56 Tower kernel: sda: sda1
Dec 3 10:20:56 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Dec 3 10:20:56 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 3 10:22:22 Tower emhttpd: Samsung_Flash_Drive_FIT_0375420070005119-0:0 (sda) 512 62656641
Dec 3 10:22:22 Tower emhttpd: import flash device: sda
Dec 3 10:22:22 Tower emhttpd: read SMART /dev/sda

DONE

2 minutes ago, zavanilli said:

how do I figure out if the flash couldnt be written?

That can often be seen in syslog, but current syslog is in RAM just like the rest of the OS and doesn't survive reboot. You would have to setup syslog server to get them saved somewhere you can get them later.

1 minute ago, zavanilli said:

Dec 3 10:20:56 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

That could just be a symptom of unclean shutdown and not necessarily the cause.

 

Sometimes Unraid itself will run fsck on flash when it boots but you can also put it in your PC and let it checkdisk. And make a backup if you don't have one. You should always have a current backup of flash.

 

13 hours ago, zavanilli said:

should I increase the timeour before shutdown in the VM settings?

Instead of shutdown/reboot press stop with all the VMs/dockers running and time how long it takes for the array to stop, or like mentioned posting the saved diags might also show what the problem was.

In case someone will have a similar issue

this turned out to be a BAD USB flash

I noticed after every reboot that non of the settings I changed are stored to the USB.

I shutdown the server

I then ran CHKDSK in windows on the USB, of course found errors that could not be fixed.

As the group here suggested, I already had a backup zip downloaded.

Brand new USB, the LimeTech tool and created anew Flash USB

plugged it in, boot

then you will find array stopped, you have to sign in to the UNRAID.net 

then replace KEY

they will either email it or install automatically depending on which license you have

then DONE
thank you all for your help