I’m new to the Unraid scene, after putting off doing something other than Windows-based serving and sharing for about… oh, about 14 years. By “new to the scene”, I mean: “Trial expires in 28 days 22 hours 6 minutes” :-)

Anywho, I ran into an issue with a disabled drive. The solution was to rebuild it. I solved it thanks to a post by u/Medical_Shame4079, on Reddit.

That made me think about the whole “losing stuff on Reddit” maybe problem of the future. While this post isn’t much, maybe it will be helpful to someone else, sometime else.

The issue? A drive ha a status of disabled, and it has a message of “device is disabled contents emulated unraid.”

The fix:

Stop the array, unassign the disk, start the array in maintenance mode, stop it again, reassign the drive to the same slot. The idea is to start the array temporarily with the drive “missing” so it changes from “disabled” to “emulated” status, then to stop it and “replace” the drive to get it back to “active” status.

Looking forward to more time with Unraid. It’s been easy to pick up so far.

  • Nogami@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    You shouldn’t be getting a disabled drive unless there’s some sort of hardware issue, or the drive is starting to fail. Double check cabling to ensure connections are solid. Check drive smart attributes and maybe run a manual long smart check.

    • whynotzoidberg@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Cheers! Great advice.

      The drive in question has had some SMART failures. I’m looking forward to putting some data on the array so I can watch it fail and experience a rebuild on inconsequential data.

      Ain’t no party like a nonprod party!

      • Nogami@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Fortunately that sort of rebuild is entirely non-exciting. Just put new drive in and start the rebuild and ignore it. Fortunately only needed to do a couple of times. Never any drama or data loss.