Problem with Snapraid after Upgrade to OMV 1.0

Hi,

now after a few updates in use is 1.029 Kralizec. Today now new updates are visible. Newest snapraid plugin from omvetras.org is in use. I have 4 4 TB Data HDD (d1, d2, d3, d4) and 1 4 TB Parity HDD (d0). Here is my snapraid config:

# this file is automatically generated.
block_size 256
autosave 0

# OMV-Name: d0
parity /media/dd8096f3-885f-4965-9ae1-852162c14daa/snapraid.parity
# OMV-Name: d1
content /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98/snapraid.content
# OMV-Name: d1 Drive Label: d1
disk d1 /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98
# OMV-Name: d2
content /media/48c94372-ea55-495f-9e42-1273a3a7f52d/snapraid.content
# OMV-Name: d2 Drive Label: d2
disk d2 /media/48c94372-ea55-495f-9e42-1273a3a7f52d
# OMV-Name: d3
content /media/dd274731-97f8-4060-ba68-3c0b2eb4986b/snapraid.content
# OMV-Name: d3 Drive Label: d3
disk d3 /media/dd274731-97f8-4060-ba68-3c0b2eb4986b
# OMV-Name: d4
content /media/44fdc808-c477-41ac-b316-a7c4e602a4cc/snapraid.content
# OMV-Name: d4 Drive Label: d4
disk d4 /media/44fdc808-c477-41ac-b316-a7c4e602a4cc

exclude *.bak
exclude *.unrecoverable
exclude /tmp/
exclude lost+found/
exclude .content
exclude aquota.group
exclude aquota.user
exclude /media/dd8096f3-885f-4965-9ae1-852162c14daa/snapraid.conf
exclude /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98/snapraid.conf
exclude /media/48c94372-ea55-495f-9e42-1273a3a7f52d/snapraid.conf
exclude /media/dd274731-97f8-4060-ba68-3c0b2eb4986b/snapraid.conf
exclude /media/44fdc808-c477-41ac-b316-a7c4e602a4cc/snapraid.conf

For Pooling aufs is in use with snapraid. Pooolshare for Samba is on Data HDD d4.

Following outputs i have in console (Putty) and in OMV GUI:

snapraid scrub
Self test...
Loading state from /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98/snapraid.content...
Using 1474 MiB of memory.
Initializing...
The array appears to be empty.

snapraid sync
Self test...
Loading state from /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98/snapraid.content...
Scanning disk d1...
Scanning disk d2...
Scanning disk d3...
Scanning disk d4...
WARNING! Ignoring mount point '/media/44fdc808-c477-41ac-b316-a7c4e602a4cc/poolshare' because it appears to be in a different device

snapraid status
Self test...
Loading state from /media/8acef4a7-8f5d-4fcf-8227-5d7f6100fc98/snapraid.content...
Using 1474 MiB of memory.

Files: 35295
Fragmented files: 0
Excess fragments: 0
Files size: 9087 GiB
Parity size: 2276 GiB

The array is empty.

What is wrong in my configuration and what could i do to change possible faults.?

Regards

Gerald

Hi,

after a few days of research i have done these:

omv logs show "out of memory problem" (my NAS has 2 GB DDR3 RAM). Now the machine has 6 GB DDR3 RAM. Snapraid sync has to be synced from the scratch and now snapraid shows no problems. The CPU Load (AMD X2 250) is changing betwen 40 and 86 %, the memory load is shown around 35%. But before and before all the new OMV Updates the CPU load while syncing was even high but memory load was around 81 % (with 2 and 6 GB RAM).

Any advices from the OMV Defs.

Regards

Gerald