Snapraid: Missing 'parity' specification in '/etc/snapraid.conf'

Lacelte · 30. März 2024

Hallo,

ich habe das Problem, das Snapraid über der Konsole nicht funktioniert.

Über das GUI funktioniert es einwandfrei.

Da ich 4 error files nach einem sync habe, wollte ich -e fix laufen lassen?

Code

$ snapraid status
Self test...
Missing 'parity' specification in '/etc/snapraid.conf'

Code

root@NASNEU:/# cat /etc/snapraid.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

autosave 0


exclude *.unrecoverable
exclude lost+found/
exclude aquota.user
exclude aquota.group
exclude /tmp/
exclude .content
exclude *.bak
exclude /snapraid.conf*

Alles anzeigen

Warum ist die Konfiguration leer?

Code

$ sudo omv-showkey snapraid

    <snapraid>
      <blocksize>256</blocksize>
      <hashsize>16</hashsize>
      <autosave>0</autosave>
      <nohidden>0</nohidden>
      <debug>0</debug>
      <sendmail>1</sendmail>
      <runscrub>1</runscrub>
      <scrubfreq>7</scrubfreq>
      <updthreshold>0</updthreshold>
      <delthreshold>0</delthreshold>
      <percentscrub>12</percentscrub>
      <scrubpercent>100</scrubpercent>
      <drives>
        <drive>
          <uuid>c96ae6bb-95f5-48c2-b633-a22540a108b5</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>eb50015d-66c3-4c09-8fa2-b187560cfd46</mntentref>
          <name>Parität18TB</name>
          <label></label>
          <path>/srv/dev-disk-by-uuid-4395b29f-6d3b-4513-93db-96d7e270c005</path                                                                                                                                                             >
          <content>0</content>
          <data>0</data>
          <parity>1</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
        <drive>
          <uuid>17be5d07-adb0-4ad6-a459-9ed56cb799ae</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>390df00c-d364-452e-be74-2e0d4d044811</mntentref>
          <name>Daten2NAS3TB</name>
          <label>Daten2NAS3TB</label>
          <path>/srv/dev-disk-by-uuid-dc50bb6a-604d-4465-af47-1bba914cf789</path                                                                                                                                                             >
          <content>1</content>
          <data>1</data>
          <parity>0</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
        <drive>
          <uuid>b18b8eaf-90cb-4e0a-875d-cb1a02e7067d</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>c19c9832-9672-4c86-a423-e98660dc983b</mntentref>
          <name>Daten5NAS8TB</name>
          <label></label>
          <path>/srv/dev-disk-by-uuid-7e274604-0477-42a3-8245-fa4f37c9f9bf</path                                                                                                                                                             >
          <content>1</content>
          <data>1</data>
          <parity>0</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
        <drive>
          <uuid>687ec699-4fb4-406b-afa9-337b15585a77</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>a705ced3-18d0-40db-8951-a154bd55525c</mntentref>
          <name>Daten1NAS3TB</name>
          <label>Paritaet1</label>
          <path>/srv/dev-disk-by-uuid-e85e4a3c-0437-4f65-ae2a-ebc65a1aa473</path                                                                                                                                                             >
          <content>1</content>
          <data>1</data>
          <parity>0</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
        <drive>
          <uuid>6e90f86e-0227-422a-97fc-526a5b0af9cc</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>3a4ba5e3-cbde-4299-a80c-2f8107ecaf2e</mntentref>
          <name>Daten3NAS3TB</name>
          <label>Daten3NAS3TB</label>
          <path>/srv/dev-disk-by-uuid-e23c7bd3-40b7-4089-a690-285dfdb3fb4b</path                                                                                                                                                             >
          <content>1</content>
          <data>1</data>
          <parity>0</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
        <drive>
          <uuid>73a9f752-5ad2-4843-9f3a-af02c44014ff</uuid>
          <arrayref>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</arrayref>
          <mntentref>1c3c0c73-4e0a-413c-a5b4-bef409351526</mntentref>
          <name>Daten4NAS3TB</name>
          <label>Daten4NAS3TB</label>
          <path>/srv/dev-disk-by-uuid-7758f0e2-7c3a-4193-9482-ba3dc3518dfb</path                                                                                                                                                             >
          <content>1</content>
          <data>1</data>
          <parity>0</parity>
          <paritynum>1</paritynum>
          <paritysplit>0</paritysplit>
        </drive>
      </drives>
      <rules></rules>
      <arrays>
        <array>
          <uuid>4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb</uuid>
          <name>snapraid</name>
        </array>
      </arrays>
    </snapraid>

Alles anzeigen

In der GUI wird sie mir angezeigt:

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

autosave 0



# drives
#####################################################################
# OMV-Name: Parität18TB  Drive Label: 
parity /srv/dev-disk-by-uuid-4395b29f-6d3b-4513-93db-96d7e270c005/snapraid.parity

#####################################################################
# OMV-Name: Daten2NAS3TB  Drive Label: Daten2NAS3TB
content /srv/dev-disk-by-uuid-dc50bb6a-604d-4465-af47-1bba914cf789/snapraid.content
data Daten2NAS3TB /srv/dev-disk-by-uuid-dc50bb6a-604d-4465-af47-1bba914cf789

#####################################################################
# OMV-Name: Daten5NAS8TB  Drive Label: 
content /srv/dev-disk-by-uuid-7e274604-0477-42a3-8245-fa4f37c9f9bf/snapraid.content
data Daten5NAS8TB /srv/dev-disk-by-uuid-7e274604-0477-42a3-8245-fa4f37c9f9bf

#####################################################################
# OMV-Name: Daten1NAS3TB  Drive Label: Paritaet1
content /srv/dev-disk-by-uuid-e85e4a3c-0437-4f65-ae2a-ebc65a1aa473/snapraid.content
data Daten1NAS3TB /srv/dev-disk-by-uuid-e85e4a3c-0437-4f65-ae2a-ebc65a1aa473

#####################################################################
# OMV-Name: Daten3NAS3TB  Drive Label: Daten3NAS3TB
content /srv/dev-disk-by-uuid-e23c7bd3-40b7-4089-a690-285dfdb3fb4b/snapraid.content
data Daten3NAS3TB /srv/dev-disk-by-uuid-e23c7bd3-40b7-4089-a690-285dfdb3fb4b

#####################################################################
# OMV-Name: Daten4NAS3TB  Drive Label: Daten4NAS3TB
content /srv/dev-disk-by-uuid-7758f0e2-7c3a-4193-9482-ba3dc3518dfb/snapraid.content
data Daten4NAS3TB /srv/dev-disk-by-uuid-7758f0e2-7c3a-4193-9482-ba3dc3518dfb



exclude *.unrecoverable
exclude lost+found/
exclude aquota.user
exclude aquota.group
exclude /tmp/
exclude .content
exclude *.bak
exclude /snapraid.conf*

Alles anzeigen

Danke für die Hilfe!

Lacelte · 30. März 2024

I'll have this translated directly into English with the kind help of Google,

maybe there will be someone who can help me

The point is that Snapraid works in the GUI but not in the console.

When I call up the configuration, it is empty.

This is present in the GUI in the plugin.

What can I do so that I can operate Snapraid via the console?

Many thanks for the help!!

gderf · 30. März 2024

Most likely you are running snapraid commands in the shell without specifying a configuration file. This will probably default to using /etc/snapraid.conf which in your case does not specify any hard drives.

You need to look in /etc/snapraid There will most likely find a configuration file with a very long name, for example (but not usable by you):

omv-snapraid-cf17351c-125a-4c4c-8516-710a4b9a40f7.conf

Then when running snapraid commands in the shell you should specify the configuration file along with the command like this.

snapraid -c /etc/snapraid/omv-snapraid-cf17351c-125a-4c4c-8516-710a4b9a40f7.conf status

I am doing some guesswork here because I do not use the SnapRAID plugin and my config file is the default which does not need to be specified.

Lacelte · 30. März 2024

Zitat von gderf

You need to look in /etc/snapraid There will most likely find a configuration file with a very long name, for example (but not usable by you):

Thank you for this hint.

That's right, I can find the configuration there.

Is it possible that I shouldn't have deleted the standard array and added my disks there?!

At least it works exactly as you described

Code

root@NASNEU:/# snapraid -c /etc/snapraid/omv-snapraid-4c0198f9-ec0a-4b8f-810c-eb                4b735eb4bb.conf status
Self test...
Loading state from /srv/dev-disk-by-uuid-dc50bb6a-604d-4465-af47-1bba914cf789/sn                apraid.content...
WARNING! For 5 disks, it's recommended to use two parity levels.
Using 1014 MiB of memory for the file-system.
SnapRAID status report:

   Files Fragmented Excess  Wasted  Used    Free  Use Name
            Files  Fragments  GB      GB      GB
  244492       0       0       -    1665    1288  56% Daten2NAS3TB
   18792       0       0       -    5891    2155  73% Daten5NAS8TB
    1152       1       2       -     182    2769   6% Daten1NAS3TB
  459604       0       0       -    1040    1909  37% Daten3NAS3TB
   12104       0       0       -     112    2894   3% Daten4NAS3TB
 --------------------------------------------------------------------------
  736144       1       2     0.0    8891   11017  45%

Alles anzeigen

Quick question perhaps.

Is -e fix the correct approach here?

Thank you very much!!

gderf · 30. März 2024

I am not sure as I do not use the plugin myself as far as why the config file is located where it is. Probably done that way to support multiple arrays which might use different config files?

The SnapRaid manual answers questions about shell commands and options.

https://www.snapraid.it/

ryecoaaron · 30. März 2024

Zitat von gderf

am not sure as I do not use the plugin myself as far as why the config file is located where it is. Probably done that way to support multiple arrays which might use different config files?

Correct. The plugin also creates a symlink to the config file in the /etc/snapraid folder named with the array's name.

Lacelte · 31. März 2024

Why does this fact not appear in any documentation?

Because I think I'm not the only one who likes to use Snapraid via the console.

In OMV6 there was no option to use multiple arrays.

But now that this is possible, the circumstance should at least be documented, right?

And another thought: isn't it possible to simply specify the name of the array that you used in the GUI instead of the long name (omv-snapraid-4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb.conf)?

Sure, now that I know, I'll just save it to a text file - no problem. But it's tricky

I hope Google translates it understandably for you

gderf · 31. März 2024

I can't help you with what is or is not documented.

Zitat von Lacelte

And another thought: isn't it possible to simply specify the name of the array that you used in the GUI instead of the long name (omv-snapraid-4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb.conf)?

Read @ryecoaaron's post above. I believe he said there is a symlink with the array name that points to its conf file. Does this not help?

Lacelte · 31. März 2024

Mh, I don't think I understand that technically

What does that mean for me?

Where can I find this link and how does it work?

Does that possibly have something to do with this?

gderf · 31. März 2024

As I said, I don't use the plugin.

What is the output of this command?

Code

ls -al /etc/snapraid

ryecoaaron · 31. März 2024

Zitat von Lacelte

Why does this fact not appear in any documentation?

The point of OMV is to use the web interface. We don't typically document command line things unless they are required.

Zitat von Lacelte

Because I think I'm not the only one who likes to use Snapraid via the console.

Why?

Zitat von Lacelte

In OMV6 there was no option to use multiple arrays.
But now that this is possible, the circumstance should at least be documented, right?

Actually, multiple arrays were available in 6.2+ versions of the plugin. It was in the testing repo though. Feel free to contribute if the docs you want are missing.

Zitat von Lacelte

And another thought: isn't it possible to simply specify the name of the array that you used in the GUI instead of the long name (omv-snapraid-4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb.conf)?

As I mentioned above and gderf reminded, there is a symlink you can use:

Code

aron@omv7dev:~$ ls -al /etc/snapraid
total 32
drwxr-xr-x   2 root root  4096 Mar  8 10:43 .
drwxr-xr-x 133 root root 12288 Mar 30 15:43 ..
-rw-r--r--   1 root root  1016 Mar  8 10:43 omv-snapraid-193819d0-f5b1-4926-9ccc-d56c877a4335.conf
-rw-r--r--   1 root root  1016 Mar  8 10:43 omv-snapraid-7ebf61f2-7370-4152-bf78-6a2e01249e01.conf
lrwxrwxrwx   1 root root    68 Mar  8 10:43 s1.conf -> /etc/snapraid/omv-snapraid-7ebf61f2-7370-4152-bf78-6a2e01249e01.conf
lrwxrwxrwx   1 root root    68 Mar  8 10:43 s2b.conf -> /etc/snapraid/omv-snapraid-193819d0-f5b1-4926-9ccc-d56c877a4335.conf

snapraid -c /etc/snapraid/s1.conf sync

works just like

snapraid -c /etc/snapraid/omv-snapraid-7ebf61f2-7370-4152-bf78-6a2e01249e01.conf sync

s1 is the array's name in this example.

Lacelte · 31. März 2024

Zitat von gderf

What is the output of this command?

Code

$ ls -al /etc/snapraid
insgesamt 24
drwxr-xr-x    2 root root   4096 30. Mär 02:31 .
drwxr-sr-x+ 108 root users 12288 30. Mär 02:03 ..
-rw-r--r--    1 root root   1922 30. Mär 02:31 omv-snapraid-4c0198f9-ec0a-4b8f-8                                                                                                                                                             10c-eb4b735eb4bb.conf
lrwxrwxrwx    1 root root     68 30. Mär 02:31 snapraid.conf -> /etc/snapraid/om                                                                                                                                                             v-snapraid-4c0198f9-ec0a-4b8f-810c-eb4b735eb4bb.conf
$

Zitat von gderf

As I said, I don't use the plugin.

All good, it's aimed more at the general public

Lacelte · 31. März 2024

Zitat von ryecoaaron

Why?

Because I wanted to use the "Fix" command with the -e filter. So that Snapraid only repairs the corrupted data and doesn't have to go through the entire array?

Zitat von ryecoaaron

. Feel free to contribute if the docs you want are missing.

I can certainly understand and if my English were better, I would like to get involved. But unfortunately the language barrier is there

Zitat von ryecoaaron

As I mentioned above and gderf reminded, there is a symlink you can use:

Ah, okay, now I understand.

It's sometimes not easy to understand as an outsider

Thanks for the help!!

ryecoaaron · 31. März 2024

Zitat von Lacelte

Because I wanted to use the "Fix" command with the -e filter. So that Snapraid only repairs the corrupted data and doesn't have to go through the entire array?

I could add that feature to the plugin but don't have a way to show the output when it is running.

Zitat von Lacelte

I can certainly understand and if my English were better, I would like to get involved. But unfortunately the language barrier is there

Write something in your native language and we can translate and edit. It would be easier to start with something than write it from scratch.

Lacelte · 31. März 2024

What did i do wrong?

Code

$ snapraid -c /etc/snapraid/snapraid.conf status
Self test...
Failed to create the lock file '/srv/dev-disk-by-uuid-dc50bb6a-604d-4465-af47-1bba914cf789/snapraid.content.lock'. Permission denied.

ryecoaaron · 31. März 2024

You didn't use sudo or run the command as root.

Lacelte · 31. März 2024

Sorry, I didn't log in as root...

Snapraid: Missing 'parity' specification in '/etc/snapraid.conf'

Lacelte 30. März 2024

Jetzt mitmachen!