​Unrecoverable media errors when resetting SnapRaid after Upgrade

    • OMV 1.0
    • ​Unrecoverable media errors when resetting SnapRaid after Upgrade

      Hi,

      I'm still in the process of finalizing my update to OMV 1.0.23. Now, I'm trying to set up Snapraid again. Problem is that I don't remember what name I gave the parity drive in snapraid. So I just called it "parity". I am now running an snapraid check and am getting "unrecoverable media" errors. It will take another 2 hours to complete. Should I stop it and if so how? And then, how to I correct my mistake?

      Thanks in advance for your help.
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)
    • I hope you got a backup of your snapraid.conf :|
      Did you have a HDD-Crash or are all HDDs well working?
      Crash:
      you have to re-add the drives and the parity-HDD with the right names

      No Crash:
      Just setup SnapRAID, add a Parity and yor Data-Drives and run snapraid sync. This will take a long time (again), but then your data is save.
      "Glowing days. Don't cry because they are over. Smile because they happened." - Confucius

      Server: 1x 32GB SSD (system) - 5x 2TB Data - 1x 2TB Snapraid-Parity - latest OMV 1.x
      No Support through PM
      Tutorials --- Howto install OMV-Extras --- Upgrade/Update-Problems --- If autoshutdown doesn' -work
    • Actually my drive should be fine. So I am going with your *no crash* procedure. But I get this:

      Source Code

      1. WARNING! Ignoring mount point '/media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/raumzeitfalte' because it appears to be in a different device
      2. DANGER! The Parity file /media/19c5b4f6-fe28-4b36-806a-eb44d0c02035/snapraid.parity is smaller than the expected 1162986127360.
      3. If this happens because you are using an old content file,
      4. you can 'sync' anyway using 'snapraid --force-full sync'
      5. to force a full rebuild of the parity.
      6. Self test...
      7. Loading state from /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/snapraid.content...
      8. Scanning disk dv_wdrbetty...
      9. Scanning disk dv_wdratlan...
      10. Using 379 MiB of memory.
      11. Saving state to /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/snapraid.content...
      12. Saving state to /media/df804a1e-2981-4e19-936a-c05aa41a6336/snapraid.content...
      13. Initializing...
      Display All


      So should I run the snapraid --force-full sync command from CLI? Do I have to enter just that or anything before that?

      Does it matter that my two data drives are pooled using aufs? Raumzeifalte is a pool made out of the two drivers wdrbetty and wdratlan.
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)
    • You can run the command, if you had added the drives before in snapraid.
      I get the same warning about the mount point. I'm using pooling too.

      BTW: my drives are Alma, Berta, Celin, ...
      "Glowing days. Don't cry because they are over. Smile because they happened." - Confucius

      Server: 1x 32GB SSD (system) - 5x 2TB Data - 1x 2TB Snapraid-Parity - latest OMV 1.x
      No Support through PM
      Tutorials --- Howto install OMV-Extras --- Upgrade/Update-Problems --- If autoshutdown doesn' -work
    • I'm only reasonably sure about which drive was the parity drive. It there anyway to find out for sure?

      EDIT: I briefly looked at the the output of "status" in Snapraid and got this:

      Source Code

      1. Self test...
      2. Loading state from /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/snapraid.content...
      3. Using 361 MiB of memory.
      4. Files: 36125
      5. Fragmented files: 134
      6. Excess fragments: 222
      7. Files size: 2058 GiB
      8. Parity size: 1083 GiB
      9. 70% *
      10. *
      11. *
      12. *
      13. *
      14. *
      15. *
      16. 35% *
      17. *
      18. *
      19. *
      20. *
      21. *
      22. * * *
      23. 0% *____*__________________________________*____________________________*
      24. 106 days ago of the last scrub 11
      25. The oldest block was scrubbed 106 days ago, the median 106, the newest 11.
      26. WARNING! The array is NOT fully synced.
      27. [u][b]You have a sync in progress at 94%.[/b][/u]
      28. No rehash is in progress or needed.
      29. No silent error detected.
      Display All


      Aparently some sync job is running, although i didn't start the forced one from CLI. What is this about?

      EDIT2: I just started the snyc through CLI as suggested. Everything seems to be running fine.
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)

      The post was edited 2 times, last by TiredHornet ().