# [OmniOS-discuss] Can't import zpool

Günther Alka alka at hfg-gmuend.de
Fri Dec 28 11:59:33 EST 2012

- Previous message: [OmniOS-discuss] Can't import zpool
- Next message: [OmniOS-discuss] puzzlingly slow disk access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    That seems to be the same problem like with Pools, created in FreeBSD:

    *Problem Pools FreeBSD -> Solaris:*
    If the disks were created in FreeBSD with GPT partitions (which FreeBSD
    recognizes but Solaris doesn't),
    you cannot import to Solaris.

    Only pools with disks formatted with GEOM can be exported from
    FreeBSD/FreeNAS/ZFSGuru and reimported into Solaris
    I do not know what options ZOL offers for partitioning.

    Gea

    On 28.12.2012 08:49, Alistair Harding wrote:
    > Apologize in advance for this, I haven't filed a bug report in years,
    > and I'm entirely useless with Solaris.
    >
    > System is a Supermicro SC-847 Chassis, 36 2TB drives, LSI 9265 for the
    > front 24 drives (all exported as JBOD) and a LSI SAS2308 based card as
    > an HBA.
    >
    > zpool was originally created under ZFSOnLinux 0.6.0-rc13, which is
    > filesystem version 5, pool version 28.
    >
    > After installing OmniOS Bloody 20121107,  I attempted to do a zpool
    > import Storage
    >
    > Error:  Assertion failed: rn->rn_nozpool == B_FALSE, file
    > ../common/libzfs_import.c, line 1086, function zpool_open_func from omnios
    >
    > zpool crashed, and dumped an 9mb core.
    >
    > I then booted FreeBSD 9.1-RELEASE (supposedly) and was able to import
    > the pool.
    >
    > # zpool status
    >   pool: Storage
    >  state: ONLINE
    >   scan: scrub in progress since Thu Dec 27 18:08:44 2012
    >         16.4T scanned out of 38.2T at 856M/s, 7h27m to go
    >         0 repaired, 42.76% done
    > config:
    >
    >         NAME  STATE     READ WRITE CKSUM
    >         Storage ONLINE       0     0     0
    >           raidz3-0  ONLINE       0     0     0
    >             mfid0p1 ONLINE       0     0     0
    >             mfid1p1 ONLINE       0     0     0
    >             mfid2p1 ONLINE       0     0     0
    >             mfid3p1 ONLINE       0     0     0
    >             mfid4p1 ONLINE       0     0     0
    >             mfid5p1 ONLINE       0     0     0
    >             mfid6p1 ONLINE       0     0     0
    >             mfid7p1 ONLINE       0     0     0
    >           raidz3-1  ONLINE       0     0     0
    >             mfid8p1 ONLINE       0     0     0
    >             mfid9p1 ONLINE       0     0     0
    >             mfid10p1  ONLINE       0     0     0
    >             mfid11p1  ONLINE       0     0     0
    >             mfid12p1  ONLINE       0     0     0
    >             mfid13p1  ONLINE       0     0     0
    >             mfid14p1  ONLINE       0     0     0
    >             mfid15p1  ONLINE       0     0     0
    >           raidz3-2  ONLINE       0     0     0
    >             mfid16p1  ONLINE       0     0     0
    >             mfid17p1  ONLINE       0     0     0
    >             mfid18p1  ONLINE       0     0     0
    >             mfid19p1  ONLINE       0     0     0
    >             mfid20p1  ONLINE       0     0     0
    >             mfid21p1  ONLINE       0     0     0
    >             mfid22p1  ONLINE       0     0     0
    >             mfid23p1  ONLINE       0     0     0
    >           raidz3-3  ONLINE       0     0     0
    >             da5p1 ONLINE       0     0     0
    >             da9p1 ONLINE       0     0     0
    >             gptid/cf9318bd-c045-3d4b-b685-31498a450171  ONLINE       0
    >     0     0
    >             da4p1 ONLINE       0     0     0
    >             da10p1  ONLINE       0     0     0
    >             da2p1 ONLINE       0     0     0
    >             da6p1 ONLINE       0     0     0
    >             da8p1 ONLINE       0     0     0
    >         spares
    >           da12p1  AVAIL
    >           da11p1  AVAIL
    >           da3p1 AVAIL
    >           da1p1 AVAIL
    >
    > errors: No known data errors
    >
    > The only two issues I can maybe think of, is OmniOS may not like the
    > one drive being GPT?, and the array was in the middle of a scrub
    > before I exported it from linux, However FreeBSD Doesn't seem to have
    > an issue with either of these things.
    >
    > The only thing I did after installing OmniOS, was log in, configure my
    > network, then attempt to zpool import Storage. /dev/dsk looked like
    > http://pastebin.com/huVBqrvH. I tried one mailing list post of mv
    > /dev/dsk /dev/dsk-old and same for rdsk, then restart some service,
    > but the issue persisted.
    >
    >
    > _______________________________________________
    > OmniOS-discuss mailing list
    > OmniOS-discuss at lists.omniti.com
    > http://lists.omniti.com/mailman/listinfo/omnios-discuss

    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121228/a0be2b0c/attachment.html>

- Previous message: [OmniOS-discuss] Can't import zpool
- Next message: [OmniOS-discuss] puzzlingly slow disk access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list