I want to move the Appdata-Folder to an external USB-Drive. But i have no option to start the migration tool.
It is greyed out, so i can not start it.
What could be the reasen for that?
It sounds like the USB Drive isn’t properly mounted, so ZimaOS can’t see it, therefor can’t migrate to it.
From your screenshots, the reason the “Move AppData-Folder” option is disabled is simple and not related to permissions or a ZimaOS bug.
ZimaOS does not recognise your USB disk as a valid “data drive”.
Right now, the OS sees it only as a normal USB storage device, not as a ZimaOS-managed data disk, which is required for AppData migration.
Your screenshots confirm this:
- In the Files app, the drive shows as
2.“ZimaData (USB)” > this means generic external drive, not part of the ZimaOS storage pool. - In Settings > Storage, the same drive appears only under
4.“External Device”, not under “Data Pool / Main Storage”.
Since AppData is a core system path, ZimaOS will only allow migration to:
- a drive that is fully mounted under /DATA,
- managed by ZimaOS,
- and formatted by ZimaOS as part of its storage subsystem.
Your USB stick is not mounted under /DATA, so the system blocks the operation.
How to fix it
I suggest doing the following:
- Go to Storage in ZimaOS.
- Select the USB drive.
- Choose Format / Initialize for ZimaOS.
This step converts it into a proper ZimaOS storage disk. - Once the drive appears as a Data Drive (inside the ZimaOS pool), the migration button will unlock automatically.
After that, the OS will allow you to move the AppData folder to this disk.
Why ZimaOS requires this
I believe the OS enforces this because AppData contains:
- all container volumes
- all database paths
- all metadata
- all application configs
- all persistent service files
If the drive is not properly mounted under /DATA, the system cannot guarantee stability or data protection.
Making the drive a ZimaOS-managed data disk solves that.
Thank you for the explanation.
But i still have a problem. There is no option for choosing Format / Initialize for ZimaOS
I formatted the drive before i connected it with GPT and ext4 filesystem.
should i delete that and just connect it unformatted?
I think the issue is exactly that the drive was pre-formatted manually.
When a disk already has a GPT table and an ext4 filesystem, ZimaOS assumes it is just a normal external USB drive, so it hides the “Initialize for ZimaOS” option.
ZimaOS will only offer that option when it sees an uninitialized / raw disk.
What I suggest:
- Remove all partitions on the USB drive so it shows up as completely empty.
(No GPT, no ext4, nothing, just unallocated space.) - Reconnect the now-blank drive to ZimaOS.
At that point, ZimaOS should recognise it as a new device and show the Format / Initialize for ZimaOS button. After you initialise it, the drive becomes part of the ZimaOS storage system, which will then unlock the Move AppData-Folder option.
Why this matters
ZimaOS must create its own internal structure under /DATA, and it will only do this on a disk it fully controls. Pre-formatted disks bypass this detection, which is why the option never appeared.
Thanks again for the detailed answer.
I will check that later, when i am at home again, and let you know if that worked.
It seems like the SSD from Crucial is not supported.
I deleted the partitions. ZimaOS shows me a new device, but in Storage it is not visible.
I don’t think the Crucial SSD is unsupported.
If ZimaOS shows it in the “New device detected” pop-up, then the kernel is detecting it correctly and the hardware is fine.
The reason it doesn’t appear in Storage is almost always the same:
The disk is not fully “raw” yet.
ZimaOS only shows a disk in the Storage app when:
- it has no filesystem signatures, and
- no partition table at all (no GPT, no MBR)
Deleting partitions often leaves behind a GPT header or the backup GPT at the end of the disk. When that metadata remains, ZimaOS assumes the disk is already formatted and hides it.
That’s exactly the behaviour you’re seeing.
Important first step
Before wiping anything, you must confirm the Crucial SSD is not the disk where ZimaOS is installed.
Device names can shift depending on boot order, so never assume /dev/sda or /dev/sdb.
You can confirm safely with:
lsblk -o NAME,SIZE,MODEL
How to properly blank the SSD
Once you confirm the correct device name, you can wipe it fully:
sgdisk --zap-all /dev/sdX
wipefs -a /dev/sdX
(Replace /dev/sdX with the actual Crucial SSD device.)
After the disk is completely raw, ZimaOS will immediately list it in Storage and allow you to initialise it.
If you want zero risk, paste your lsblk -o NAME,SIZE,MODEL output here and I’ll point out the exact device to wipe.
And again, thanks for your detailed answer.
I will try that later too. I had the same thing with a brand new, never used SSD.
But i will check that. I guess i need to connect via SSH to do that, correct?
Unfortunately it did not help.
I ordered a 2TB WD Red now, as this is on the compatibility list.
Anyway, thank you very much for your help!
I appreciate that.