Same here, nothing about the database in the log.
2020-01-23T19:41:05.627Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2020-01-23T19:41:06.610Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
I guess this means the db is OK?
Hello @LarsOS,
Welcome to the forum!
You shouldn’t force the update. We do not want to push offline the whole network when we release a new version.
Just wait until it updates itself.
Here is example of positive messages:
2020-01-23T20:26:30.180775047Z 2020-01-23T20:26:30.180Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2020-01-23T20:26:31.113173554Z 2020-01-23T20:26:31.112Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
@littleskunk I enabled preflight.database-check: true on all storage nodes that already updated, and see no issues with this option (no addition bugs and it true positive news 
)
So far it is looking positive. Do we have nobody with a clock offset? Please shoot a short message if your clock was out of sync and how you fixed it. That would help us as well.
Once my nodes update Ill let you know my Windows node came up fine.
No problem:
Precision clock is my standard by default on every server, it extremely important for Virtual Machines, and other non-bare metal systems.
How to check status on Debian (Ubuntu):
timedatectl status
NTP service: should be active
If status is not active, check configuration file /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048
And enable it with:
timedatectl set-ntp true
How can i add this check on linux docker?
preflight.database-check: true
Check your data dir that mounted to destination=/app/config in your docker run string. You can find
config.yaml here, just add preflight.database-check: true to the end of this file.
so if preflight.database-check: is not present in the ymal is not present just add it
Should be there if you updated to 30.5
And don’t forget to restart the container using docker restart -t 300 storagenode for the settings to take effect.
Yes, just add it to the config file if not present and restart.
thanks add it no messages in the log after restart so I will take that as a positive thing
You should see
2020-01-23T14:57:06.987-0500 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-01-23T14:57:07.869-0500 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
yes I see those two messages but nothing about preflight for the db
I think these are the only messages you get.
well I’m going take the lack of no malformed db as positive and move on thanks
The update appears to have removed my operator wallet, and reset my allocated bandwidth, and allocated disk space. It left some of my commented out lines and did not add preflight check. Although the node appears to be running fine somehow. I suspect on next restart it will break itself.
Edit. NVM:. That’s in my docker run command. So wallet and space are ok, however it did not add preflight check to yaml, but it did do a preflight check 
I still have entries in my ymal referencing kademlia and grpc
here the post looks like node not start at all after update