Data Recovery P.1.5

Read Data Recovery P.1 for more context!

Not much has happened to warrant a part 2 so let’s go

I took a break from the recovery for about a month as it was affecting my mental health and taking up unworldly amounts of time. So where am I now? To be frank still at stage one, but with a different plan.

To recap the last thing I was getting was

root@tillamook[~]# zpool import            
   pool: Share
     id: 6380960973060959609
  state: FAULTED
status: The pool metadata is corrupted.
 action: The pool cannot be imported due to damaged devices or data.
        The pool may be active on another system, but can be imported using
        the '-f' flag.

        Share                                     FAULTED  corrupted data
          raidz1-0                                ONLINE
            a6be7230-1f75-11ed-bf89-448a5b26cb0a  ONLINE
            a688c0a5-1f75-11ed-bf89-448a5b26cb0a  ONLINE
            a6caa8f8-1f75-11ed-bf89-448a5b26cb0a  ONLINE
          raidz1-1                                ONLINE
            b9728524-57d0-438c-ae2b-e4d84be16086  ONLINE
            21c3e212-683f-4f06-be73-8779d6a2ed09  ONLINE
            4a2194e7-1c81-4a6f-b632-b1d2cc789626  ONLINE

After much consideration of the $400 option I decided to look into other options, and that is when I had a eureka moment. All of my problems are from a dead metadata drive, What if instead of trying to recover the raid vDevs, What if I tried to recover the data on the metadata drive instead, As in theory if all of the metadata is on that drive, if I’m able to clone the drive to a new one, I should be able to reimport it back into the pool. Right? We will have to see. Until next time.

I am the creator of the worst. Gal on the brink of a mental breakdown trying to hold it together. Join me as I riot!

Leave a Reply

All comments are manually reviewed and moderated.
Required fields are marked *

By commenting, you consent to our Privacy Policy
Back To Top
Skip to content