Beiträge von wolf8auer

So your setup would look like this:

A -> SATA II -> B

B -> CAT6 -> D

C -> CAT6 -> D

Is this correct?

You ran iperf on C connected to B?

maybe this scheme helps to refer to the specific components

Did you have problems with installing resetperms or did you use it and it didn't solve your permissions issue?

Is the Disk where you wanted to create your shared folder mounted?
Have you sucessfully created shared folder(s) on this disk with omv before?

Have a look at my Screenshot about ACL.

Did you try the omv plugin resetperms?
It has always been a lifesaver when I had permission issues.

Now I usually fix permission issues in omv's ACL tab.
Have a look at the image.
On the left the group of this shared folder has changed to root and Read/Execute. (This happened after the SnapRAID plugin recovered some files in this folder.)
On the right are the settings that where on this folder before.

After changing those settings on the left back to the original ones, I clicked "Recursive: Apply permissions to files and subfolders" and Apply.
Permission problem solved.

Zitat von crashtest

SNAPRAID manual. Scroll down to 4.4 "Recovering"

If you prefer to use SnapRAID in the omv user interface have a look at this guide.

Your NAS and PC have GbEthernet.

What about your SBC (single-board computer)?

In case you have a Raspberry Pi 3 here is a brief overview about it’s bottlenecks.

Thank you!
Good suggestion, I've posted an updated version in the guide section.

_{Snapraid in OMV User Guide - Setup, Undelete, replace disk v1.2.pdf}

This detailed Guide on how to replace a disk with snapraid might help. (Although it doesn't include mergerFS.)

On second thought, I am not sure if it is of any help without a parity drive.

Maybe you could create a shared folder Foo on a single disk
temporarily move all files from the mergerFS drive to Foo.
After that,

• replace the temporary HDD
• delete the temporary HDD from your mergerFS pool
• add the new HDD to your mergerFS pool
• relink the disk in snapraid -> you may find that section in the guide
• copy files from shared folder Foo back again to your meregrFS drive
• finally delete good old Foo

Sounds great!
I've downloadad the image and use that for my fresh install.

I think this guide might help:
How to map fresh omv install to existing shares and users

How to map fresh omv install to existing shares and users

I've tried it on a small test system and it worked.
It's a very straight forward process.

1) Record the status quo
First make notes about your omv setup:

existing omv users:
Name | Group
user1 | users

existing omv shared folders:
Name | Device | Path/
share1 | hd1 | hd1/
share2 | hd2 | hd2/

(optional) omv snapraid configuration:
Name | Drive | Content | Data | Parity
data1 | hd1 | yes | yes | no
data2 | hd2 | yes | yes | no
parity| hd3 | no | no | yes

optional: to be on the safe siede make a copy of the etc/openmediavault/config.xml.
The <share> tag lists all your shared folders.
The <users> tag lists all your users.

Attention: The etc/openmediavault/config.xml is for reference only.
It is tempting to copy anything between the <share> and <users> and paste it in the config.xml of the fresh omv install.
Do not do this! Always create shared folders and users via the omv web UI.

As you can see there is a difference between the old config.xml and the new.
This is because omv always creates a new <uuid>, an internal database reference number.
Therefore you should always create the shared folder via omv web UI.

2) Let's do it
after the basic setup of your fresh omv install...
2.1)
mount all your Drives
hd1 | hd2

2.2)
add all your shared folders. Use the same Name and the same Device.
share1 | share2

2.3)
add all your users. Again, use the same Name and Group. (Group defaults to the group 'users').
user1 (set user read/write privileges for the shared folders as you had it before)

2.4)
add your disks to snapraid exactly as you had them on the previous install.

2.5)
add all shared folders to omv samba share service (or Apple Filing) depending on what you had on your previous install.

Done!
Now you should be able to connect to all your shares
More important, you should see all files and subfolders that you had created with your old install.

Addendum: I've finished the same procedure on my live system.
I had a Docker Plex container on my old install.
As suggested in the omv guides, I've created shared folders for Plex, AppData and Media.
AppData was populated with some subdirectories and files by Docker Plex.
Reconnecting those shared folders with the Docker Plex container on the new install worked without any problems.

In OMV 4[/b] you have to make it this way:

You can omit fields with ;; (like I did it here with email and shell)

# <name>;<uid>;<comment>;<email>;<password>;<shell>;<group,group,...>;<disallowusermod>
user1;1001;some comment;;pa$$w0rd;;users;false
user2;1002;some comment;;t0pSecret;;users;false

I've added a notification on their website.
I hope it can be a little help for other users. It's easy to make mistakes in a completely new domain.

Since I'll do a fresh omv install anyway, I am curious to try the Armbian based OMV image.

Would I notice any difference between Armbian and the stretch image?

My bad!
Thanks for the clarification!

I completely ignored the pre-release tag!!!! Oh man, what a blooper

On the other hand I am glad that happened because I did't recognize that I am using a pre-release built at the moment.

This happened because pine64.org had a link to the Release notes on ayufan Linux github and I happened to use the first image on top (which happened to be 0.7.11).

I am using the stretch-openmediavault-rock64-0.7.11-1075-armhf.img.xz with my rock64.
It works!

The latest image stretch-openmediavault-rock64-0.8.0rc10-1125-armhf.img.xz does not work.
ayufan-rock64 linux-builds

I can see the board's IP on my network but I cannot open the OMV WebGUI.

some lines of the HDMI output:

...


[23.217872] Rebooting in 90 seconds..


...


[9.627034] FAT-fs (mmcblk1p6): Volume was not properly unmounted. Some data may be corrupted. Please run fsck.


[11.731829] rk-gmac-dwmac ff540000.ethernet eth0: Link is up -1Gbps/Full - flow control rx/tx


[108.569222] systemd-journald[300]: Failed to send WATCHDOG=1 notification message: Connection refused


[192.784397] systemd-journald[300]: Failed to send WATCHDOG=1 notification message: Transport Endpoint is not connected

I've created a guide for the omv snapraid plugin.

It covers:

• Set Up Disks
• Undelete files
• resolve permission problems
• replace Disk
• reconnect shared folders

unfortunately I don't have a PC with a SATA port to my disposal right now.
Nevertheless the Nanopi is an interesting board anyway.
I'll simply give the the SATA HAT a try.

I have an existing OMV setup running on a rock64 SBC with some disks and shared folders.

Could I change my SBC from rock64 to Nanopi 4m and keep all OMV settings like users and shared folders?

From the FAQ I know that the /etc/openmediavault/config.xml is for referencespurposes only.

I guess it is not ment to be used in to replace the config on the new install with the config from the previous board.

Since I cannot use the image from rock64 on a Nonopi 4m, how would I map the existing shared folders on my harddrives to the new OMV?

I am curious how well the eSATA port on my FANTEC would work with NanoPi's SATA HAT. If it works at all.