Re: No ZFS when loading modules from loeader prompt
--sm4nu43k4a2Rpi4c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Feb 20, 2013 at 7:05 AM, O. Hartmann <ohartman@zedat.fu-berlin.de> =
wrote:
> At the loader prompt, I need to unload the buggy kernel and load the old
> working one via
>
> load /boot/kernel.old/kernel
>
> Then I load also the ZFS related modules
>
> load /boot/kernel.old/opensolaris.ko
> load /boot/kernel.old/zfs.ko
>
> Issuing boot at the end of that stage boots the kernel - the old one
> -successfully - but there is no working ZFS and no ZFS volume gets
> mounted although the rc.conf is executed correctly.
>
> What am I doing wrong at that point? Why isn't ZFS run and mount properly?
Last time I ran into this problem, the issue was that "unload" also
unloaded the zpool.cache file and the ZFS code relied on that to find
the kernel. I don't recall what the workaround was.
On 2013-Feb-20 08:17:46 -0800, Freddie Cash <fjwcash@gmail.com> wrote:
>Sounds like a perfect use case for Boot Environments. Create a new BE,
>install the new kernel into it, set it as the default, reboot. If it
>fails, you manually set the previous BE as the default, and reboot. That
>way, your "known-good", working environment is never affected.
How do you change your BE in the loader? Or how do you change your
BE when you can't boot?
--=20
Peter Jeremy
--sm4nu43k4a2Rpi4c
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlEmvgMACgkQ/opHv/APuIf+5gCfW4aeRzU9NZAjduzYq07qqgD3
2oAAoIO16Jgv6cAY/rL/kITdCI7sj2qx
=Z2yS
-----END PGP SIGNATURE-----
--sm4nu43k4a2Rpi4c--
討論串 (同標題文章)
完整討論串 (本文為第 5 之 5 篇)：