Good suggestion, however, it still failed with the same error. Again, once I turned off the drive on the esata channel, it then imported fine again.
On Wed, 18 Jun 2014 15:58:56 -0400 Ray Arachelian <[email protected]> wrote: > What worked for me in these cases is to rm /etc/zfs/zpool.cache and > then reboot. > You'll need to import any pools (other than rpool) as this is where > the information about the pools is kept, including your ghost. > > > > On 06/18/2014 02:40 PM, Reginald Beardsley via openindiana-discuss > wrote: > > I'm not sure if it's related, but I had for a long time a phantom > > pool that would get listed by "zfs import". i eventually figured > > out that there was an old ZFS vdev label left over from a > > previous disk layout. " dd if=/dev/zero" at the start and end of > > the unused slices cured that once I realized what was going on. > > You might want to read the ZFS on disk format description. > > > > https://maczfs.googlecode.com/files/ZFSOnDiskFormat.pdf > > > > In my case I had been trying various slice alignments to resolve > > messages about the pool alignment with a 4k sector disk. > > > > Reg > > > > -------------------------------------------- > > On Wed, 6/18/14, Michelle Knight <[email protected]> wrote: > > > > Subject: [OpenIndiana-discuss] Persistant ZFS set ID > > To: "John Doe via openindiana-discuss" > > <[email protected]> Date: Wednesday, June 18, > > 2014, 1:14 PM > > Hi Folks, > > > > I changed a drive set and was using an old one as a backup, > > so I put > > the 1.5tb drive in and created a single ZFS drive called > > "backup". > > > > It wouldn't import, even after reboot, update, etc... > > > > mich@jaguar:~# zpool > > import backup > > Assertion failed: rn->rn_nozpool == B_FALSE, > > file ../common/libzfs_import.c, line 1080, function > > zpool_open_func > > Abort (core dumped) > > > > > > So I removed the drive, put it in a Linux machine, destroyed > > everything > > I could find, wrote out a new partition table, put it back > > in the > > server and asked for a ZFS import... > > > > mich@jaguar:~# zpool > > import > > pool: tank > > id: 13988636425947326543 > > state: ONLINE > > status: The pool is formatted using a legacy on-disk > > version. > > action: The pool can be imported using its name or numeric > > identifier, > > though some features will not be available without an > > explicit 'zpool > > upgrade'. config: > > > > tank > > ONLINE > > c3t4d0p0 ONLINE > > > > So I shut the server down, removed the legitimate "tank" and > > tried to > > then bring the server back up in order to mount this old > > tank and > > destroy it ... > > > > mich@jaguar:~# zpool > > import > > Assertion failed: rn->rn_nozpool == B_FALSE, > > file ../common/libzfs_import.c, line 1080, function > > zpool_open_func > > Abort (core dumped) mich@jaguar:~# zpool > > import > > pool: tank > > id: 13988636425947326543 > > state: ONLINE > > status: The pool is formatted using a legacy on-disk > > version. > > action: The pool can be imported using its name or numeric > > identifier, > > though some features will not be available without an > > explicit 'zpool > > upgrade'. config: > > > > tank > > ONLINE > > c3t4d0p0 ONLINE > > mich@jaguar:~# zfs > > destroy tank > > cannot open 'tank': dataset does not exist > > mich@jaguar:~# zpool > > import tank > > Assertion failed: rn->rn_nozpool == B_FALSE, > > file ../common/libzfs_import.c, > > line 1080, function > > zpool_open_func Abort (core > > dumped) mich@jaguar:~# init 6 > > > > > > .... > > > > Eventually, I got rid of tank and recreated the drive as > > "backup", > > changing the mount point to /mnt/backup, then exporting it, > > and then > > when I try to import it again ... > > > > Assertion failed: rn->rn_nozpool == B_FALSE, > > file ../common/libzfs_import.c, line 1080, function > > zpool_open_func > > Abort (core dumped) > > > > ...and there was a "backup" directory left under /mnt/ > > > > I'm getting this assertion failed all over again, and I just > > can't > > import backup. I just don't get it. I wonder if the > > change of mount > > point caused the problem? > > > > > > > > _______________________________________________ > > openindiana-discuss mailing list > > [email protected] > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > > _______________________________________________ > > openindiana-discuss mailing list > > [email protected] > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > > > > _______________________________________________ > openindiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ openindiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
