[OpenIndiana-discuss] Kernel panic after upgrading to OpenIndiana
cmosetick at gmail.com
Sun Oct 3 07:47:37 UTC 2010
*jack at opensolaris:~$ pfexec zpool import -f rpool
cannot import 'rpool': invalid vdev configuration
* It seems very easy to overlook, but it is my understanding that you always
need to run these steps in a specific order:
first just run import by itself
pfexec zpool import
<output will list pools available for import>
pfexec zpool import -f rpool
In the recent past I have forgot to run "import" by itself, and saw the same
or similar error message and thought WTF, because I know the pool was there
I know that you should do it this way when using OS or OI, as running import
by itself first is inherent to zfs. The expected behavior is the same on
both. I can't say why you are seeing different output on OI vs OS live usb
environments, but at this point I would not over-analyze that.
Just run import by itself first and all should be well.
On Fri, Oct 1, 2010 at 2:23 AM, Thorsten Heit <thorsten.heit at vkb.de> wrote:
> > This appears very similar to another issue with the bootfs
> > specification which is normally transparent:
> > http://opensolaris.org/jive/thread.jspa?messageID=315743
> > Also make sure you have the current version of GRUB installed on
> > *both* disks in your mirror, as it's responsible for specifying the
> > bootfs parameter.
> This was already done after attaching the second disc to rpool.
> I just booted into the live USB image to check whether my system is at all
> capable of booting into OI. Works as expected, but I'm not able to import
> the zpools:
> jack at opensolaris:~$ pfexec zpool import -f rpool
> cannot import 'rpool': invalid vdev configuration
> jack at opensolaris:~$
> Erm, what does this message wants to tell me?
> Why does this happen only when booting the USB image of OI and not the one
> of OSOL b134?
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
More information about the OpenIndiana-discuss