Beiträge von Lacelte

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

What did i do wrong?

$ 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.

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!!

Zitat von gderf

What is the output of this command?

$ 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

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?

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

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

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%

Quick question perhaps.

Is -e fix the correct approach here?

Thank you very much!!

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!!

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?

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

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*

Warum ist die Konfiguration leer?

$ 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>

In der GUI wird sie mir angezeigt:

# 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*

Danke für die Hilfe!

Sorry...

mein Fehler..
Ich habe gestern Abend mehre Stunden alles ausprobiert gehabt, ohne Erfolg.
Jetzt gerade eben kam mir der Gedanke, dass ich die ACLs direkt auf der Platte, also am Anfang der Dateistrucktur anwenden sollte.

Denn ich habe auf jeder Platte einen gleichnamigen Ordner, auf den ich verweise und mein "Startpunkt" ist.
Nun habe ich die Freigaben direkt auf "/" verwiesen und die ACLs zurück gesetzt und siehe da, es funktioniert.

Huhu,

hab hier ein Problem mit den Berechtigungen der freigegebene Ordner in OMV7.

Eins vor ab, da ich glaube das es was damit zu tun haben könnte; die Platten haben schon mehrere Umzüge mitgemacht, auf immer wieder neue OMV Installationen.

Jetzt ist es so, dass die 3 Benutzer die ich schon immer angelegt habe, einwandfrei funktionieren.

Gestern dann habe ich versucht, einen neuen zu erstellen. "Backup"

Leider hat dieser keine Schreib-Rechte. Ebenso haben alle Benutzer die ich Anlege dieses Verhalten.

Was auch seltsam ist, das er laut Diagnose in der Gruppe "backup" sei - obwohl nie Gruppen angelegt worden sind.

Auch das tool zum zurücksetzen der ACLs habe ich auf der Freigabe ausgeführt.

Ohne Erfolg.

Ich denke, Bilder sagen mehr als Worte, hier sind ein paar:

Vielleicht habt ihr eine Idee und könnt mir bitte helfen

Vielen Dank!

Thank you very much!

It works perfectly!

Zitat von ryecoaaron

The host would not be able to access the usb device(s) on that controller. Depends on what those devices were to tell you what happens. If it was a keyboard, you could type anything on the host.

I just want to pass various USB hard drives and USB sticks to the VM.

Zitat von ryecoaaron

BUT you maybe not want to do that since the host may be using a usb port on that controller.

Thanks for your answer!

What would happen if it were?
Can I prevent this?

Hallo,

wie ist es möglich, einen USB-Controller durchzureichen?
Habe eine USB Karte installiert:

Fresco Logic FL1100 

lspci | grep USB

Code:

01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee
08:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 01)
0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host

Dieser erscheint aber nicht in der Auswahl?

Zitat

lsusb

Code:

Code

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse
Bus 001 Device 007: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet
Bus 001 Device 006: ID 046b:ff31 American Megatrends, Inc. Virtual HardDisk Device
Bus 001 Device 005: ID 046b:ff20 American Megatrends, Inc. Virtual Cdrom Device
Bus 001 Device 004: ID 046b:ff01 American Megatrends, Inc. Virtual Hub
Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
Bus 001 Device 002: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Alles anzeigen

Spoiler anzeigen

Code

 lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B                                                            ]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B                                                            ]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43eb
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43e9
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04)
04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)
05:00.0 Non-Volatile memory controller: Device 1dbe:5216 (rev 01)
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
08:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 01)
09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy                                                             Function
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SP                                                            P
0a:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor                                                             PSPCPP
0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0a:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

Alles anzeigen

Was kann ich tun um den Controller an der VM weiterzureichen?

Vielen Dank!

Me again

I can use the following to get on the boot loader:

Shell> fs0:EFI\debian\grubx64.efi

How can I proceed now so that the system starts automatically without having to enter the command every time?

I'm glad that the system starts again

Falls wer Deutsch spricht, gerne

Shell> fs0:EFI\debian\grubx64.efi

Hello,

I tried to find options in the BIOS with which I can pass the USB ports to a VM.
Unfortunately, I must have adjusted something in the BIOS that OMV is no longer booting.

Was very stupid and ignorant of me ..

BIOS settings are again as before.

How can I fix the error again?
Is there a possibility?

Translated with Google

Thank you very much!

Zitat von gderf

Selecting the data disks in the same order as was done originally will be important.

Puhh.. kann ich nicht Garantieren.
Die Platten sind wie folgt benannt: Daten1, Daten2, Daten3
Dann hoffe ich, dass ich sie auch nach der Reihenfolge in Snapraid eingebunden habe

Was kann passieren, wenn ich sie in einer falschen Reihenfolge einbinde?

Sorry, mein Englisch ist nicht gut.
Müsste es auch mit Google übersetzen

Hallo,

und zwar habe ich meiner NAS neue Hardware gegönnt.

Im gleichem Atemzug habe ich OMV neu aufgesetzt.

Zuvor war ein Snapraid konfiguriert bestehend aus 3 Daten und 1 Parität.

Leider habe ich bei dem Umzug vergessen, die Snapraid Konfiguration zu sichern?

Meine Frage ist, kann ich die Daten-Platten sowie die Parität-Platte einfach wieder neu einbinden oder muss die Parität komplett neu aufgebaut werden?
Muss ich auf irgendwas achten?

Vielen Dank!

Nach der Deinstallation von dem Root-Plugin ging gar nichts mehr -> System jetzt neu installiert, funktioniert alles wieder.