I have (or had, really) a pool consisting of 4 SSDs in RAID-Z mode.
One of them was faulty. I shut down the truenas box, so that I can pull the all out to check which serial number matches the faulty reported one.
The faulty one got replaced.
Server is booted up.
And the pool is now completely gone.
This is ridiculous. Sorry but it really is. Am I not supposed to replace a faulty disk, and than just simply select which new disk to add to the existing array? What else am I supposed to do?
I cannot import the pool either.
Luckily no imported data is on it... YET.
But if this were to happen with important data on it, I would be thoroughly, let's say, "discouraged". I guess this is a perfectly failed test of a fault scenario.
So now what? Let's say, just for the sake of argument, that I have to retain the data that is supposed to be stored safely on the remaining 3 SSDs. What should I do to restore the array?
And also, what *should* I have done to replace the faulty SSD, other than what I already described? I had no way of knowing which one it means by the serial number, nevermind its internal devicename like `/dev/sdg` or something. I *have* to pull them all out to check which exact one is reported faulty. And you'd *think* that be safer to do while the system is not powered on, wouldn't you?
Lastly, I want to say that even as a novice in the world of TrueNAS, I would consider this a critical bug. Top priority and all that. After all, there is no way to assign it a new drive and make it rebuild the raidness & redundancy.
Please advice.
One of them was faulty. I shut down the truenas box, so that I can pull the all out to check which serial number matches the faulty reported one.
The faulty one got replaced.
Server is booted up.
And the pool is now completely gone.
This is ridiculous. Sorry but it really is. Am I not supposed to replace a faulty disk, and than just simply select which new disk to add to the existing array? What else am I supposed to do?
I cannot import the pool either.
Luckily no imported data is on it... YET.
But if this were to happen with important data on it, I would be thoroughly, let's say, "discouraged". I guess this is a perfectly failed test of a fault scenario.
So now what? Let's say, just for the sake of argument, that I have to retain the data that is supposed to be stored safely on the remaining 3 SSDs. What should I do to restore the array?
And also, what *should* I have done to replace the faulty SSD, other than what I already described? I had no way of knowing which one it means by the serial number, nevermind its internal devicename like `/dev/sdg` or something. I *have* to pull them all out to check which exact one is reported faulty. And you'd *think* that be safer to do while the system is not powered on, wouldn't you?
Lastly, I want to say that even as a novice in the world of TrueNAS, I would consider this a critical bug. Top priority and all that. After all, there is no way to assign it a new drive and make it rebuild the raidness & redundancy.
Please advice.