Jonathan Catt
Cadet
- Joined
- Apr 28, 2016
- Messages
- 3
Hi guys,
I was asked to take a look at a clients FreeNAS implementation and I ran into a few questions that the documentation didn't seem to discuss in detail. First off let me say I recognize 9.10 is quite an old build and yes we are in discussions with the client as to if they want to upgrade to the latest but as of right now this is what I have to work with. I was wondering if one of the experts here would be able to help out.
There are 2 odd/unhappy raid pools, raidz3-7 and raidz3-6.
To start with, raidz3-7 has 13 members instead of 11 (Every RaidZ3 Set was setup with 11 member disks initially)
When disk81p2 or 165p2 are selected, I see the additional option to "Detach" them which is not available to the other multipaths. The rest can only offer "Offline" or "Replace" I'm wondering what means. Are these drives currently not being used in the raid pool but otherwise "good?"
raidz3-6 currently shows up as Degraded with one multipath removed
When I click on replace, I am presented with three options. disk61, disk75 and disk179.
Oddly, disk 61 shows up as member of raidz3-5 but, unlike the others, shows up at just disk61, not disk61p2. I do not know if this is something concerning or not.
disk75 and disk179 do not show up as part of any other raid pools. When I try to replace the "removed" drive in raidz3-6 with either disk75 or disk179, the following box comes up
To consolidate (and add to) my questions
1) In raidz3-7, why do two of the members offer the option to detach, while the others do not. What is the best way to correct this so that it becomes a normal 11 member pool.
2) Why is disk61 presented as an option when replacing disks even though it is part of raidz3-5
3) Are we safe to force the replacement for raidz3-6 using the most recently added disk179?
4) How do I identify and replace the spare-3 that is currently being used in raidz3-7? Also (far less importantly) is there a way to change the naming within raidz3-7 so that spare-3 shows up as a multipath, and the new "spare" takes that name instead.
Thanks
I was asked to take a look at a clients FreeNAS implementation and I ran into a few questions that the documentation didn't seem to discuss in detail. First off let me say I recognize 9.10 is quite an old build and yes we are in discussions with the client as to if they want to upgrade to the latest but as of right now this is what I have to work with. I was wondering if one of the experts here would be able to help out.
There are 2 odd/unhappy raid pools, raidz3-7 and raidz3-6.
To start with, raidz3-7 has 13 members instead of 11 (Every RaidZ3 Set was setup with 11 member disks initially)
When disk81p2 or 165p2 are selected, I see the additional option to "Detach" them which is not available to the other multipaths. The rest can only offer "Offline" or "Replace" I'm wondering what means. Are these drives currently not being used in the raid pool but otherwise "good?"
raidz3-6 currently shows up as Degraded with one multipath removed
When I click on replace, I am presented with three options. disk61, disk75 and disk179.
Oddly, disk 61 shows up as member of raidz3-5 but, unlike the others, shows up at just disk61, not disk61p2. I do not know if this is something concerning or not.
disk75 and disk179 do not show up as part of any other raid pools. When I try to replace the "removed" drive in raidz3-6 with either disk75 or disk179, the following box comes up
To consolidate (and add to) my questions
1) In raidz3-7, why do two of the members offer the option to detach, while the others do not. What is the best way to correct this so that it becomes a normal 11 member pool.
2) Why is disk61 presented as an option when replacing disks even though it is part of raidz3-5
3) Are we safe to force the replacement for raidz3-6 using the most recently added disk179?
4) How do I identify and replace the spare-3 that is currently being used in raidz3-7? Also (far less importantly) is there a way to change the naming within raidz3-7 so that spare-3 shows up as a multipath, and the new "spare" takes that name instead.
Thanks
