...
[SHORT] 13:45:08 WARNING: Database shema: device present in global list but missing as device/fileinfo entry
...
[monitor] 13:45:09 WARNING: 4 restarts in 10.776522s; not retrying further
Probable workaround: Get the 1.4.2 release and run it with the environment variable STRECHECKDBEVERY=1s set. That should fix your db. Then try to upgrade again.
The issue is that db checking happens after schema update (as it works on the latest schema), so any defect present in the db before the upgrade is present when the schema update happens. The schema migrations should take all possible steps to correct errors encountered when upgrading instead of assuming a consistent starting state (which they apparently do now).