Pool won't mount after reboot

[king13p]

Hello everyone,

Very new to FreeNAS and I'm having some issues with a new server build. I have 12 4tb hard drives running with RaidZ3. These drives are all connected to my motherboard which has 12 on board sata ports. Everything was working fine until I wanted to add another volume to an SSD that I connected after I shut the machine down. The SSD was connected to a PCI SATA addon card. Now I noticed when booting that the 12 drive data pool will not mount anymore and the disk order has changed. It used to be the 12 drives would take ada0 - ada11. Now the SSD takes ada4.

If I remove the SSD from the machine and start FreeNAS all over again, the 12 drive data pool remounts just fine. I am using FreeNAS-11.2-U3. My system has 64GBs of RAM. All pools were created in the GUI.

I'm assuming that the SSD is taking up one of the original FreeBSD disk names and the pool doesn't know how to remount itself. Is there anyway to rename that disk to a higher ada number or is there some other way to fix this issue?

Any help would be greatly appreciated. Thanks!

 

[Apollo]

ada numbering scheme is not assigned to a particular disk. It is added incrementally when a device is detected by the kernel when devices get enumerated.

First thing that comes to mind is that maybe, just maybe, you extended your 12 disk pool to include the SSD causing your pool to become stipped Vdev's. Upon removing the SSD it will cause the pool to be degraded at best, and unavailable in most cases.

If that is the case, you have no other choice, I believe, that you will have to recreate the pool from scratch.
This implies replicating you data to a backup pool, destroy, recreate the 12 disk pool excluding the SSD and restore the pool from replicated backup.

Unless something else is at play.
Can you do:
zpool status