gptid devices, mirrored boot drives

[jal]

Hello all,

First, I imagine this is covered somewhere in the forums, but I found this to be a remarkably difficult set of search terms to work out.

The background: I built a FreeNAS box about a year and a half ago. The motherboard failed, and I took the opportunity to upgrade quite a bit from my first iteration. Same disks (6x6T WD Reds, Z2), but I went with the Supermicro X10SDV-TLN4F motherboard and 64G RAM (yes, ECC)[1].

One of the things that didn't work out on the first build was mirroring the boot drives. Had an issue with an internal USB port multiplier, and ended up dropping it at the time, but took this opportunity to fix it. Which brings me to now.

I followed the instructions in the manual (System -> Boot -> Status). I didn't think about the fact that it presented me the sole option of device name 'da2', and used it. So after the resilver, a `zpool list` shows

Code:

  freenas-boot  ONLINE  0  0  0
	mirror-0  ONLINE  0  0  0
	gptid/364a20c3-905a-11e6-8957-0cc47ac6c6a4  ONLINE  0  0  0
	da2p2  ONLINE  0  0  0

I guess my concern is having the system decide at some point that the usb drive currently known as da2 should be renamed, and this will become something that needs periodic attention upon reboot. Not the worst thing in the world, but, well, seems like something that should be fixed.

So I'm wondering if I just fix this at the command line, if that will annoy, confuse or otherwise torment the GUI. If so, is there a fix through the GUI? Following the instructions in the manual didn't offer any other options.

[1] In case anyone wonders at the rather expensive upgrade with no similar storage increase, that will be happening later, when I get over the sticker shock of this part. Also, I'm considering moving back to full FreeBSD because I want more flexible virtualization, and also I'm just more comfortable with managing this at the command line, But I still want to fix this, because getting around to installing FreeBSD will likely take me another year and a half.

 

[depasseg]

I know it's cliche, but have you rebooted?

because getting around to installing FreeBSD will likely take me another year and a half.

By that time, FreeNAS 10 will be nice and stable which has a vastly improved virtualization environment.

 

[jal]

I know it's cliche, but have you rebooted?

I hadn't previously, but just did; no change (`zpool list` still reports the same as my first post.)

By that time, FreeNAS 10 will be nice and stable which has a vastly improved virtualization environment.

I haven't looked at 10/the roadmap, abut that wold be an interesting direction for the project. Other virtualization projects (VMWare, obviously, but now Ovirt) are focusing on distributed storage. Single machine-focused virtualization with ZFS backing in an appliance is a nice alternative.

In any case, I was using "manage at the command line" as a bit of shorthand to try to avoid extraneous detail. I use Saltstack, which doesn't grok FreeNAS and makes the GUI mostly redundant for my purposes.

 

[Stux]

Scrub the mirror. Offline the drive. Wipe the drive. Replace the offlined drive with the now wiped drive.

Done.