Error file config/storage/info.db failed: database is locked

hello I can’t find the error info.db I put here the command "docker logs storagenode
"

2025-01-29T00:02:28Z	ERROR	failure during run	{"Process": "storagenode", "error": "Error migrating tables for database on storagenode: migrate: database: info opening file \"config/storage/info.db\" failed: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).openDatabaseWithStat:390\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:367\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).Migration.func1:715\n\tstorj.io/storj/private/migrate.(*Migration).Run:168\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:415\n\tmain.cmdRun:100\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272", "errorVerbose": "Error migrating tables for database on storagenode: migrate: database: info opening file \"config/storage/info.db\" failed: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).openDatabaseWithStat:390\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:367\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).Migration.func1:715\n\tstorj.io/storj/private/migrate.(*Migration).Run:168\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:415\n\tmain.cmdRun:100\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272\n\tmain.cmdRun:102\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272"}
Error: Error migrating tables for database on storagenode: migrate: database: info opening file "config/storage/info.db" failed: database is locked
	storj.io/storj/storagenode/storagenodedb.(*DB).openDatabaseWithStat:390
	storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:367
	storj.io/storj/storagenode/storagenodedb.(*DB).Migration.func1:715
	storj.io/storj/private/migrate.(*Migration).Run:168
	storj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:415
	main.cmdRun:100
	main.newRunCmd.func1:33
	storj.io/common/process.cleanup.func1.4:392
	storj.io/common/process.cleanup.func1:410
	github.com/spf13/cobra.(*Command).execute:983
	github.com/spf13/cobra.(*Command).ExecuteC:1115
	github.com/spf13/cobra.(*Command).Execute:1039
	storj.io/common/process.ExecWithCustomOptions:112
	main.main:34
	runtime.main:272
2025-01-29 00:02:28,979 WARN exited: storagenode (exit status 1; not expected)
2025-01-29 00:02:29,981 INFO spawned: 'storagenode' with pid 116
2025-01-29 00:02:29,981 WARN received SIGQUIT indicating exit request
2025-01-29 00:02:29,982 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2025-01-29T00:02:29Z	INFO	Got a signal from the OS: "terminated"	{"Process": "storagenode-updater"}
2025-01-29 00:02:29,984 INFO stopped: storagenode-updater (exit status 0)
2025-01-29 00:02:29,984 WARN stopped: storagenode (terminated by SIGTERM)
2025-01-29 00:02:29,984 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2025-01-29 00:02:42,413 INFO Set uid to user 0 succeeded
2025-01-29 00:02:42,415 INFO RPC interface 'supervisor' initialized
2025-01-29 00:02:42,415 INFO supervisord started with pid 1
2025-01-29 00:02:43,416 INFO spawned: 'processes-exit-eventlistener' with pid 64
2025-01-29 00:02:43,418 INFO spawned: 'storagenode' with pid 65
2025-01-29 00:02:43,419 INFO spawned: 'storagenode-updater' with pid 66
2025-01-29T00:02:43Z	INFO	Configuration loaded	{"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "healthcheck.details"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "console.address"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "contact.external-address"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "operator.email"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "server.private-address"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "server.address"}
2025-01-29T00:02:43Z	INFO	Invalid configuration file key	{"Process": "storagenode-updater", "Key": "operator.wallet"}
2025-01-29T00:02:43Z	INFO	Anonymized tracing enabled	{"Process": "storagenode-updater"}
2025-01-29T00:02:43Z	INFO	Running on version	{"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.120.4"}
2025-01-29T00:02:43Z	INFO	Downloading versions.	{"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2025-01-29T00:02:43Z	INFO	Configuration loaded	{"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-01-29T00:02:43Z	INFO	Anonymized tracing enabled	{"Process": "storagenode"}
2025-01-29T00:02:43Z	INFO	Operator email	{"Process": "storagenode", "Address": "billidon12345@gmail.com"}
2025-01-29T00:02:43Z	INFO	Operator wallet	{"Process": "storagenode", "Address": "0x099f2eD3D35A4974eAd15483700ad69A5FBabB34"}
2025-01-29T00:02:43Z	INFO	Current binary version	{"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.120.4"}
2025-01-29T00:02:43Z	INFO	Version is up to date	{"Process": "storagenode-updater", "Service": "storagenode"}
2025-01-29T00:02:43Z	INFO	Current binary version	{"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.120.4"}
2025-01-29T00:02:43Z	INFO	Version is up to date	{"Process": "storagenode-updater", "Service": "storagenode-updater"}
2025-01-29 00:02:44,601 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-29 00:02:44,601 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-29 00:02:44,601 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

I use a terramaster and I’m on ubuntu

Hello @ti-marc,
Welcome to the forum!

How your drive is connected?

Please note - none of network filesystems (NFS, SMB, CIFS, etc.) are supported. If you are unable to run a node directly on your fileserver, then only iSCSI is working.

I use NFS shares so alexey can roll his eyes at me.

You can move the databases to local storage:
How to move DB’s to SSD on Docker - Node Operators / FAQ - Storj Community Forum (official)

Also, with the new version 120 you may get errors about a hashstore file flock. That can be worked around similarly:
Hashstore: bad file descriptor - Node Operators / troubleshooting - Storj Community Forum (official)