Daedalus is using wrong drive to store temporary chain!

(related to - Daedalus custom path to BC - possible? (linux))

I did change the CHAIN folder location (by symlink like in article - https://iohk.zendesk.com/hc/en-us/articles/900004340586-How-to-symlink-Daedalus-chain-folder), BUT now Daedalus syncing from the start…

It want to download the block chain AGAIN and it use my ROOT (/) SSD to store this temporary block chain witch is wrong (there is simply no space for that).

I want it to see the newmove block chain, update it (on the drive it is stored - cause only there there is space for that) and sync.

As you can see on the picture, Block chain is stored on proper drive, but daedalus sync it with using “/” SSD and not proper “mnt/xxx(the oher SSD drive)/adachain/chain/immutable”.

Can somebody say how to fix this? I guess Daedalus should not work that way.

Muahahhaha it’s working now!

After finding (strange I did not find it before) those topics:

I did manage to fix the problem - solution:
At start I create a simlink:
ln -s /mnt/strange-numbers-of-your-drive-here/adachain/chain /home/pro/.local/share/Daedalus/mainnet

then in file:
/home/YOU_USER_NAME/.local/bin/daedalus-mainnet
you must add:
-m /mnt:/mnt
at two places (in IF and ELSE)

then in file:
/home/YOU_USER_NAME/.local/share/Daedalus/mainnet/namespaceHelper
you must add:
-m /mnt:/mnt
at two places (in IF and ELSE)

I’m using linux MINT (and love it), and honestly I don’t know what is going on here (why those 2 files must be edited), but it works! Synchronization start where it was left, on a new chain location.