OMV Snapraid - trying to run 'FIX' for newly added disk, but get error about a data disk being not present in config

    TLDR: OMV Snapraid says one of my disks is not present in the config file while it clearly is (new install of OMV, trying to recover a disk that failed).


    Hello, I am having an issue trying to recover a data disk that was part of my setup in Snapraid. Background info- something went wrong in my PC, had to re-buy everything (mobo, cpu, ram) and re-install OMV. But after re-installing OMV I discovered that one of the data disks was now faulty.


    After the disk failed I bought a new drive. Unfortunately I was not able to copy any data from it to save it. So now trying to sync the data

    So, added the disks that were working + new one for the disk that errored. Everything seems to be set up correctly. But when I now run 'FIX' on the new empty disk (disk2), I get error that disk3 has been removed from config:


    Code
    Self test...
Loading state from /srv/dev-disk-by-uuid-2ff92b0b-e642-4433-8a15-2e2e103f0079/snapraid.content...
Decoding error in '/srv/dev-disk-by-uuid-2ff92b0b-e642-4433-8a15-2e2e103f0079/snapraid.content' at offset 93
The file CRC is correct!
Disk 'medusa' with uuid '83745eb3-c780-4f62-91e0-8836e5bca8a1' not present in the configuration file!
If you have removed it from the configuration file, please restore it


    When I look at the config then the disk IS present in the config file.



    Any help would be greatly appreciated!


    EDIT:


    >83745eb3-c780-4f62-91e0-8836e5bca8a1


    When I look at the UUID of the drives then it is present on the OS: https://i.imgur.com/dTsxi4w.jpeg



    Code
    lrwxrwxrwx 1 root root  10 Sep 29 07:31 2ff92b0b-e642-4433-8a15-2e2e103f0079 ->                                                                           ../../sdc1
lrwxrwxrwx 1 root root  10 Sep 29 07:31 5fe4899b-84c2-40ca-b764-cc398786a273 ->                                                                           ../../sda1
lrwxrwxrwx 1 root root  10 Sep 29 07:31 83745eb3-c780-4f62-91e0-8836e5bca8a1 ->                                                                           ../../sdd1
lrwxrwxrwx 1 root root  10 Sep 29 07:31 8f8b2ea2-9aa3-43dd-be08-ece7b55899ce ->                                                                           ../../sdb1
lrwxrwxrwx 1 root root  10 Sep 29 07:31 a4fcf42b-33b8-4279-9023-6cbd2ceef1a1 ->                                                                           ../../sda5
lrwxrwxrwx 1 root root  10 Sep 29 07:31 e04be864-c8f5-4c19-aa46-7ed9d7667497 ->                                                                           ../../sde1
lrwxrwxrwx 1 root root  10 Sep 29 07:31 e10cc0d3-9640-4d8c-95ed-96420a1228e1 ->                                                                           ../../sdf1

  • KM0201

    Hat das Thema freigeschaltet.

    I found solution to my issue. When setting up the disks in snapraid I had failed to select 'content' and 'data'. I had all the disks selected just as content. Changing this fixed it.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden