![]() gpart list da1 says gpart: no such geom: da1.zpool status says no pools available (broken language? lol.).zpool import -a says no pool available to import.In the terminal, here are some attempted commands and results. Such as creating a new vdev or trying with other disk formats. Warning to other users: If you run into problems with GUI, immediately stop any destructive operations.This is enough info I need before going to terminal. In the GUI Information section shows the disk as da1.I don't think the disk is physically damaged. SMART info about this disk looks all right in GUI.So I cannot import the pool by simply hitting the buttons. However, the GUI ZFS section cannot detect the zpool.In the Web GUI, the disk can be automatically imported and recognized as a zpool (not unformatted or UFS etc.).Might have deleted (destroyed) the pool.Some vague memory about what I did (and did not do): I'm using XigmaNAS (nas4free) and all commands below are issued via terminal. Unfortunately I don't recall what exactly I did (I have been changing some hardware so I messed up don't be like me!), but this worked for me. I somehow screwed up my ZFS configuration. I tried running Jeff Bonwick's labelfix tool (with updates from this post), but it did not seem to solve the problem. There is a discussion of a similar-sounding problem in this old thread. # zpool importĬannot import 'ztmp': no such pool availableĬannot import '16827460747202824739': no such pool available I have run zdb -lu on the partition, and it seems to find the labels just fine. I have tried a number of approaches, but nothing happens. When I try to import the pool, there's no sign that it exists at all. The ZFS data sits in a GPT partition on the disk. I now have only one of the disks from the mirror, and I am trying to recover files from it. I had a ZFS pool - a mirror containing 2 vdevs - running on a FreeBSD server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |