Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Jan 2010 17:07:55 +0000
From:      krad <kraduk@googlemail.com>
To:        Steve Bertrand <steve@ibctech.ca>
Cc:        "questions@freebsd.org" <questions@freebsd.org>
Subject:   Re: Can't mountroot from ZFS pool
Message-ID:  <d36406631001190907q391671b1l3ae1436df37c32b1@mail.gmail.com>
In-Reply-To: <4B55D3E3.20502@ibctech.ca>
References:  <4B4BBB4F.5020805@ibctech.ca> <d36406631001120316k2457e6f4y77cfaf7835056cb4@mail.gmail.com> <4B55D3E3.20502@ibctech.ca>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
2010/1/19 Steve Bertrand <steve@ibctech.ca>

> krad wrote:
> >
> >
> > 2010/1/11 Steve Bertrand <steve@ibctech.ca <mailto:steve@ibctech.ca>>
> >
> >     All,
> >
> >     I've successfully upgraded the disks in my ZFS backup server, and can
> >     import/mount the pool properly.
> >
> >     However, I designed this box originally so that it mounts / from
> >     zfs:storage after booting from a USB stick.
> >
> >     After the upgrade of the disks, I'm stuck at a mountroot prompt when
> I
> >     attempt to boot the system with the original USB /boot key.
> >
> >     Can someone inform me how to find the / filesystem at the mountroot
> >     prompt? If not, is there *any* way to boot the system normally from
> >     another medium, and then 'reload' the system with the ZFS / after its
> >     been mounted so that the system functions as designed (ie. cron
> >     works etc)?
>
> > did you export the pool at all before rebooting it?
>
> Yes, I did.
>
> I just finally got it resolved :)
>
> It appears as though by importing the zpool onto another system
> obsoleted the cache file on the original USB /boot disk.
>
> I exported, then imported the pool on the secondary system, then copied
> the cache file into the /boot/zfs directory on my original boot medium.
>
> Things are now working again, and I have all of my new storage and
> original data in place!
>
> Thanks for all the help!
>
> Steve
>

Its an easy mistake to make. People think exporting a pool is  the same as
unmounting but it isn't really, and its kind of difficult to explain why
(unless ur an uber guru)

One thing for sure is that the hostid of the system is stored in to the
zpool somewhere as is the state of it. This also has to match the
zpool.cache files details. The reason for this is probably largely to do
with sun clustering, where a pool on a particular lun may be visible to many
nodes in the cluster, but only one having it currently imported and the
subsequent file systems mounted.

Hmm, why does it always sound so clunky when I try to explain it 8/



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?d36406631001190907q391671b1l3ae1436df37c32b1>