Migration of data storage location and stops at 6% from today

Insight & Feedback
,
1

Migration of data storage location
and stops at 6% from today even by restarting Zima I can’t return to the web interface
Are there any terminal commands to stop the process?
Application in progress…
ZimaOS-HData
The migration will take approximately 5-10 minutes.
Stop docker

6%

2

I did a migration in the past and it took a very long time, like 2-3 days. Especially going from the SSD to the RAID. You might leave it alone and see if it continues to progress.

3

Is there a way to check if it’s actually working from the terminal?
The phone app works.
I can access the data from the computer, but I can’t access it from the web; it’s always at 6%.
Yesterday, I actually finished uploading the data to two 2TB drives in a RAID.
Maybe the RAID is also rebuilding?

4

I suggest you do not try to stop the migration mid-way. If you interrupt it, you may not be able to simply “run it again” cleanly from the UI, and you can end up in a half-migrated state that needs manual cleanup or a reinstall to recover.

Also, do not stop Docker on ZimaOS. That can take the web UI offline completely.

Check from terminal if it’s still working

1) Check live disk activity (best indicator)

iotop -o

2) If you migrated to RAID, check if RAID is rebuilding

cat /proc/mdstat

If you see resync or recovery, the RAID is still rebuilding and the progress can appear stuck at 6% for a long time.

If you paste the output of:

cat /proc/mdstat

we can tell straight away if it’s rebuilding or genuinely frozen.

5

cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda[0] sdb[1]
1953382464 blocks super 1.2 [2/2] [UU]
[==========>…] resync = 50.7% (991496128/1953382464) finish=16074.2min speed=996K/sec
bitmap: 11/15 pages [44KB], 65536KB chunk

da@ZimaBoard2:~ ➜ $ iotop -o
-bash: iotop: command not found

iotop gives me an error should I install it?

6

No need to install iotop.

ZimaOS is an appliance-style OS (Docker based) and it doesn’t behave like a normal Linux distro where installing packages is supported/reliable.

Also in your case we don’t even need it — your output already confirms what’s happening:

RAID1 is still rebuilding:
resync = 50.7% ... finish=16074 min

That means the system is still doing heavy background work, and the migration UI can easily appear stuck at 6% while RAID is resyncing.

I suggest leaving it alone and just checking progress with:

cat /proc/mdstat

Once resync completes, the migration should continue / recover normally.

“Normally migration only takes minutes, but in your case RAID is still resyncing, so migration can appear frozen and may take hours or longer until RAID completes.”