You may disable a filewalker on start
storage2.piece-scan-on-startup: false
also move databases to SSD or at least to C:\
And perhaps you need to increase a check timeout again. Please note, in case of readable check timeout you need also increase the readable check interval too, because they both 1m0s by default.
You may also have a writable check timeouts too, so just make sure that you modifying the correct one.
For the migration it’s better to use a simple SMB/CIFS or NFS share from your NAS dataset, because you likely cannot simple migrate from iSCSI virtual disk to a dataset.
You may setup a node using TrueChart on Scale, just need to provide a custom paths to your identity and data before the start of the application. I would also disable a port forwarding in case of mistake to do not disqualify your migrated node. When you will make sure that the app is running and use the provided paths, e.g. without duplicated blobs subfolder in a wrong place, you may enable the port forwarding. Please note, the docker version expects all data in the storage subfolder, but you must provide a parent folder to the docker version (it will append storage automatically to the provided path to see its data), this is the main difference between Windows GUI and docker setups.
See Migrating from Windows GUI installation to Docker CLI - Storj Docs