Summary
A vStor pool may not reappear after a reboot of the vStor. This article suggests techniques for getting it back.
Symptoms
After a reboot a vStor pool is missing. In the GUI is that can seen when attempting to expand the associated storage controller and no volumes being seen.
On the vStor itself, the output of "vstor pool show" will be empty and "zpool status" will report:
no pools available
However, the disks are still present and identified as belonging to a pool:
UUID | TYPE | VENDOR | MODEL | SIZE | USED AS | NAME
------------------------------------------------------------------------------------------------------
36a4badb011c33a0020d2854a055a697d | SCSI | DELL | PERC 6/i | 136.12GB | xfs | /dev/sda
200e49150cf611abaae000000 | SCSI | Amazon | Storage Gateway | 1.00TB | vstor_pool | /dev/sdb
200e48b129e3315f6da000000 | SCSI | Amazon | Storage Gateway | 1.00TB | vstor_pool | /dev/sdc
Resolution
First, if the system reboot time is likely to be short, reboot again see if that is sufficient to rediscover the pool.
If not, run the command "zpool import":
pool: vpool3
id: 7330122766718425589
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
vpool3 ONLINE
scsi-200e48b129e3315f6da000000 ONLINE
scsi-200e49150cf611abaae000000 ONLINE
If the "action" text is the same as the example above, the pool can be imported with:
zpool import -R /vstor "pool name"
In the example above, the pool name is vpool3.
When this completes, regenerate the cache file:
zpool set cachefile=/etc/vstor/zpool.cache/"pool ID" "pool name"
In the example above the pool name is vpool3 and its ID is 3.
Use "zpool status" and "vstor pool show" to check the status. If there are additional problems, please contact Catalogic Technical Support. Please have a vStor log suite available.
This can be collected with: "vstor system logcollect"