some_guy_named_ed
Dabbler
- Joined
- Dec 31, 2013
- Messages
- 13
So here's the back story -
I woke up this morning to find my array in a degraded state. Without thinking too much, I identified the faulty drive and pulled it from the chassis. I replaced it with another drive. When I noticed it didn't re-silver right away, I started poking around. I used the gui option to extend the array with the new disk and added it as a spare.
Immediately it started resilvering and eventually completed. I thought to myself "Yay! I didn't break it" but lo and behold it's still in a degraded state.
I'm sure it's actually fine and needs some sort of metadata cleanup or something because I botched a proper procedure somewhere. All shares are up and speed seems nominal. Can anybody advise me on what to do next to clean things up? I've attached a screengrab at what I'm looking at in the GUI. The offline disk is the one I removed and for some reason, the new one (da15p2) is in two places now.
Thanks for any help on this.
Ed
I woke up this morning to find my array in a degraded state. Without thinking too much, I identified the faulty drive and pulled it from the chassis. I replaced it with another drive. When I noticed it didn't re-silver right away, I started poking around. I used the gui option to extend the array with the new disk and added it as a spare.
Immediately it started resilvering and eventually completed. I thought to myself "Yay! I didn't break it" but lo and behold it's still in a degraded state.
I'm sure it's actually fine and needs some sort of metadata cleanup or something because I botched a proper procedure somewhere. All shares are up and speed seems nominal. Can anybody advise me on what to do next to clean things up? I've attached a screengrab at what I'm looking at in the GUI. The offline disk is the one I removed and for some reason, the new one (da15p2) is in two places now.
Thanks for any help on this.
Ed
Attachments
Last edited: