I think I've screwed replacing a drive up. Here's what I've done.
I got an email that a disk was degraded (I'm using ZFS2 on my Freenas). I went into the webgui, identified the disk (/dev/ada2) and physically replaced it with a new one. When I boot up the machine, the first time it failed to mount and start Freenas. So I turned it off and on again. Now it goes to the main screen, but I can't connect to the WebGui (which pisses me off to no end). I figure I need to replace the drive manually and then the WebGui will work again.
This is where things get a little tricky. I know I need to run zpool replace, but the zpool status is only giving me some id information, rather than simple things I recall from the gui (like /dev/ada2, I have a total of 6 drives so it goes ada0-5). Since I had restarted the drives, I couldn't get the id information from before, but there is an obviously new one showing up that is just a number with no letters (didn't work to use that as a target for zpool replace). So I then ran glabel status, which listed ada0 through ada4 with some others that I wasn't sure of. I figured that the machine considered the ada2 not there, so then it moved down what was ada3-5 to ada2-4. So then I ran
zpool replace [name of Volume] [some id number that the zpool status is using for the failed drive] /dev/ada5
It is re-silvering now, but I'm really unsure if I did the right thing of using ada5 rather than ada2. So I have two main questions, 1) did I do the right thing, 2) if I did the wrong thing, should I cancel the re-silver (is that possible?), or should I wait for it to finish and do something else. I have sufficient spare drives that after this resilver is done, I could replace another one properly.
I got an email that a disk was degraded (I'm using ZFS2 on my Freenas). I went into the webgui, identified the disk (/dev/ada2) and physically replaced it with a new one. When I boot up the machine, the first time it failed to mount and start Freenas. So I turned it off and on again. Now it goes to the main screen, but I can't connect to the WebGui (which pisses me off to no end). I figure I need to replace the drive manually and then the WebGui will work again.
This is where things get a little tricky. I know I need to run zpool replace, but the zpool status is only giving me some id information, rather than simple things I recall from the gui (like /dev/ada2, I have a total of 6 drives so it goes ada0-5). Since I had restarted the drives, I couldn't get the id information from before, but there is an obviously new one showing up that is just a number with no letters (didn't work to use that as a target for zpool replace). So I then ran glabel status, which listed ada0 through ada4 with some others that I wasn't sure of. I figured that the machine considered the ada2 not there, so then it moved down what was ada3-5 to ada2-4. So then I ran
zpool replace [name of Volume] [some id number that the zpool status is using for the failed drive] /dev/ada5
It is re-silvering now, but I'm really unsure if I did the right thing of using ada5 rather than ada2. So I have two main questions, 1) did I do the right thing, 2) if I did the wrong thing, should I cancel the re-silver (is that possible?), or should I wait for it to finish and do something else. I have sufficient spare drives that after this resilver is done, I could replace another one properly.