Hi there, happy to be joining the community.
So I'm just putting this here as a major piece of luck and might save another member hassle with drive failure.
I made 2 mistakes after reading an article recently stating you could expand storage with old drives. Sooooo I bought a 4tb enterprise drive off Fleabay 2nd hand.
That's mistake number 1
I ran the drive in my nas for a week to "run in" and perform smart tests. All good.
Then I made my 2nd mistake. I added it to my pool as a stipe (no mirror). Not a serious boo boo as I do have other copies of my data, I just wanted to centralise everything.
After about a week, the dashboard indicated my pool was unhealthy. Tried zpool scrub and zpool clear but the errors kept coming back. So I turned to the community on FB. Got a couple of answers but I'm not proficient with CLI yet.
I bought a new 4TB ironwolf drive, slapped both that and the offending drive into a "dumb" cloner, left it to do it's thing. Took all day, a very nervous day.
When it finished, I put the new drive in the nas and fired it up. The pool listed as unhealthy because it obviously copied everything from the old drive "bit for bit" and for some reason the share was empty. I uploaded the last system configuration snapshot and it came back online. A new scrub task kicked in and I left it to run overnight. Next morning, entered zpool clear in the CLI and hey presto!! all was well.
So now my nas is back up and running without having to rebuild the shares and data.
So there we go, it seems if the drive is unhealthy but responsive you may be able to copy the stripe and save your system without losing your data.
Hope this helps somebody.
So I'm just putting this here as a major piece of luck and might save another member hassle with drive failure.
I made 2 mistakes after reading an article recently stating you could expand storage with old drives. Sooooo I bought a 4tb enterprise drive off Fleabay 2nd hand.
That's mistake number 1
I ran the drive in my nas for a week to "run in" and perform smart tests. All good.
Then I made my 2nd mistake. I added it to my pool as a stipe (no mirror). Not a serious boo boo as I do have other copies of my data, I just wanted to centralise everything.
After about a week, the dashboard indicated my pool was unhealthy. Tried zpool scrub and zpool clear but the errors kept coming back. So I turned to the community on FB. Got a couple of answers but I'm not proficient with CLI yet.
I bought a new 4TB ironwolf drive, slapped both that and the offending drive into a "dumb" cloner, left it to do it's thing. Took all day, a very nervous day.
When it finished, I put the new drive in the nas and fired it up. The pool listed as unhealthy because it obviously copied everything from the old drive "bit for bit" and for some reason the share was empty. I uploaded the last system configuration snapshot and it came back online. A new scrub task kicked in and I left it to run overnight. Next morning, entered zpool clear in the CLI and hey presto!! all was well.
So now my nas is back up and running without having to rebuild the shares and data.
So there we go, it seems if the drive is unhealthy but responsive you may be able to copy the stripe and save your system without losing your data.
Hope this helps somebody.