Move snapraid and union-filesystem from v4 old maschine to v5 new maschine

Hello,

I have to move my disks from my old machine to a new one.

On the old pc there is a OMV4 running and on the new there is a clean install of OMV5.

Which steps in which order are necessary to transfer snapraid and union-filesystem?

I don't want to loose any data!

Any help appreciated

Solution:

For moving snapraid and union-filesystem from v4 old machine to v5 new machine do do following steps:

If using ACL: write down or copy UserID in old /etc/password

in webgui:

1.

At File-Systems:

Mount all the necessary devices

2.

At Union-Filesystems:

Add the devices (and use the same name as before)

3.

At Snapraid:

Add data and parity drives

4.

If using ACL write the old UserID in new /etc/password - beware it has to be unique!!

Zitat von gderf

Plug in the disks.

There is nothing to "transfer." You will have to setup everything from scratch.

Thanks for fast response!

What about the union-filesystem?

How does the system find the old structure of the files?

For example:

dokuments

pictures

movies

...

Zitat von gderf

UnionFS does not change anything on the data disks. What is sees is determined by configuration within OMV.

OK,

and how does the new system find the old structure of the folders?

What do I have to do to let OVM find the structure of the folders?

Ok,

so the conclusion of your explanation are the following steps in webgui:

1.

At File-Systems:

Mount the devices

2.

At Union-Filesystems:

Add the devices (and use the same name as before)

3.

At Snapraid:

Add data and parity drives

After that the old folderstructure will appear at the new system...

Did I understand this correct?

At point 2:

Union-Filesystems:

Add the devices (and use the same name as before)

I receive following error, after hitting "apply":

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run quota 2>&1' with exit code '1': debian: ---------- ID: quota_check_create_files_0493d2c6-21e8-4545-bf45-5b1f50e7e0c2 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten01 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten01" run Started: 23:36:58.475635 Duration: 9.625 ms Changes: ---------- pid: 2902 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten01 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_f85749a8-889d-4dd9-88a0-97f1dff0c165 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten02 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten02" run Started: 23:36:58.485655 Duration: 8.082 ms Changes: ---------- pid: 2904 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten02 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_3efd358d-aba8-4c1a-b387-771bd6276e1d Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten03 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten03" run Started: 23:36:58.494098 Duration: 7.8 ms Changes: ---------- pid: 2906 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten03 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_769dca7d-f15c-441c-aa82-7cb8b8b4f241 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten04 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten04" run Started: 23:36:58.502296 Duration: 8.242 ms Changes: ---------- pid: 2908 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten04 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_ec115f12-f182-4bff-967c-cadff86681c0 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten05 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten05" run Started: 23:36:58.510866 Duration: 7.953 ms Changes: ---------- pid: 2910 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten05 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_46678b0b-c62b-4e43-9d8b-75c7c524c74d Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten06 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten06" run Started: 23:36:58.519160 Duration: 7.584 ms Changes: ---------- pid: 2912 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten06 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_ef493c8c-1efe-4d9e-a85e-3919f222fa39 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten07 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten07" run Started: 23:36:58.527133 Duration: 8.001 ms Changes: ---------- pid: 2914 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten07 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_43eee1dc-8a38-48cb-9d51-b17f109dd8ee Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten08 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Daten08" run Started: 23:36:58.535501 Duration: 7.621 ms Changes: ---------- pid: 2916 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Daten08 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_a95c13bb-ec78-4ece-aa60-c7e5af1da3e1 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Paritaet1 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Paritaet1" run Started: 23:36:58.543500 Duration: 8.991 ms Changes: ---------- pid: 2919 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Paritaet1 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: quota_check_create_files_fe7e726c-f68c-4999-aeb7-5cf9a87291c2 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Paritaet2 Result: False Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-label/Paritaet2" run Started: 23:36:58.552840 Duration: 7.934 ms Changes: ---------- pid: 2921 retcode: 6 stderr: quotacheck: Quota for users is enabled on mountpoint /srv/dev-disk-by-label-Paritaet2 so quotacheck might damage the file. Please turn quotas off or use -f to force checking. stdout: ---------- ID: disable_quota_service Function: service.disabled Name: quota Result: True Comment: Service quota is already disabled, and is in the desired state Started: 23:36:58.576641 Duration: 39.947 ms Changes: Summary for debian ------------- Succeeded: 1 (changed=10) Failed: 10 ------------- Total states run: 11 Total run time: 121.780 ms

OK,

everything is working again with one exception:

At shared folders the ACLs are changed between most users and groups.

user1 has the rights of user2

user2 has the rights of user3

....

group1 has the rights of group2

.....

What is the fastest way to fix this?

OK,

my solution was:

looking in the old /etc/password for the old UID-Numbers and use them for the username at the new /etc/password.

This worked perfect.

Thanks for all the support!!!

Conclusion:

For moving snapraid and union-filesystem from v4 old machine to v5 new machine do do following steps:

If using ACL: write down or copy UserID in old /etc/password

in webgui:

1.

At File-Systems:

Mount all the necessary devices

2.

At Union-Filesystems:

Add the devices (and use the same name as before)

3.

At Snapraid:

Add data and parity drives

4.

If using ACL write the old UserID in new /etc/password - beware it has to be unique!!