[OpenIndiana-discuss] Cannot _init zfs module after upgrade

[Andreas Stenius]

Hi,

I got this same issue when upgrading to oi151a4 (and still have it for
a5 as well).

I'm running OI as a KVM guest on a Proxmox system, and after some
fiddling, I was able to capture to boot messages:

module /platform/i86pc/kernel/amd64/unix: text at [0xfffffffffb800000,
0xfffffffffb964f3b] data at 0xfffffffffbc00000
module /kernel/amd64/genunix: text at [0xfffffffffb964f40,
0xfffffffffbbec58f] data at 0xfffffffffbc95440
OpenIndiana Build oi_151a3 64-bit (illumos 022f1af9e21c)
SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
All rights reserved. Use is subject to license terms.
x86_feature: lgpg
x86_feature: tsc
x86_feature: msr
x86_feature: mtrr
x86_feature: pge
x86_feature: de
x86_feature: cmov
x86_feature: mmx
x86_feature: mca
x86_feature: pae
x86_feature: cv8
x86_feature: pat
x86_feature: sse
x86_feature: sse2
x86_feature: asysc
x86_feature: nx
x86_feature: sse3
x86_feature: cx16
x86_feature: cmp
x86_feature: cpuid
x86_feature: ssse3
x86_feature: clfsh
x86_feature: 64
mem = 8388212K (0x1fff9d000)
SMBIOS v2.4 loaded (616 bytes)initialized model-specific module
'cpu_ms.GenuineIntel' on chip 0 core 0 strand 0
root nexus = i86pc
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
Reading Intel IOMMU boot options
pci0 at root: space 0 offset 0
pci0 is /pci at 0,0
PCI-device: isa at 1, isa0
/kernel/fs/amd64/zfs: undefined symbol 'fnvlist_alloc'
/kernel/fs/amd64/zfs: undefined symbol 'fnvlist_add_nvlist'
/kernel/fs/amd64/zfs: undefined symbol 'fnvlist_free'
/kernel/fs/amd64/zfs: undefined symbol 'vmem_qcache_reap'
/kernel/fs/amd64/zfs: undefined symbol 'fnvlist_add_boolean'
WARNING: mod_load: cannot load module 'zfs'

panic[cpu0]/thread=fffffffffbc2f260: Cannot _init zfs module

Warning - stack not written to the dump buffer
fffffffffbc718e0 genunix:rootconf+1a8 ()
fffffffffbc71920 genunix:vfs_mountroot+63 ()
fffffffffbc71950 genunix:main+136 ()
fffffffffbc71960 unix:_locore_start+90 ()

skipping system dump - no dump device configured
rebooting...


Since I'm running this on a qemu-kvm system, there should be good
options for debugging the boot, if needed (although I'm not an
experienced qemu user, nor at debugging boot-ups).

I join Ryan in asking for how to solve this...

//Andreas

2012/7/17 Ryan Johnson <ryan.johnson at cs.utoronto.ca>:
> Hi all,
>
> I'm new to OpenIndiana, and am hitting a problem that doesn't seem to be on
> Google anywhere:
>
> I downloaded the latest oi151a release ISO today and installed it on an
> Intel x86_64 machine under VMWare. The install worked fine, but as soon as I
> tried to install any package, it pulled in an upgrade to 151a3 that includes
> a new boot environment. Unfortunately, the new environment can't boot, and
> loops endlessly between the grub menu and crashing.
>
> The error is "Cannot _init zfs module", after complaints that
> /kernel/fs/amd64/zfs has the following undefined symbols: fnvlist_alloc,
> fnvlist_add_nvlist, fnvlist_free, fnvlist_add_boolean, and vmem_qcache_reap.
>
> The offending command was:
>>
>> ryan at dtrace:~$ which hg
>> which: no hg in (/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin)
>> ryan at dtrace:~$ sudo pkg install mercurial
>> Password:
>>                Packages to install:     3
>>                 Packages to update:    53
>>            Create boot environment:   Yes
>> DOWNLOAD                                  PKGS       FILES    XFER (MB)
>> Completed                                56/56   7567/7567 98.4/98.4
>>
>> PHASE                                        ACTIONS
>> Removal Phase                                164/164
>> Install Phase                              3323/3323
>> Update Phase                               5671/5671
>>
>> PHASE                                          ITEMS
>> Package State Update Phase                   109/109
>> Package Cache Update Phase                     53/53
>> Image State Update Phase                         2/2
>>
>> A clone of openindiana exists and has been updated and activated.
>> On the next boot the Boot Environment openindiana-2 will be mounted on
>> '/'.
>> Reboot when ready to switch to this updated BE.
>
> (the openindiana-2 BE is the second failed attempt)
>
> Any ideas? If I didn't know better I'd say this was a packaging error, but I
> really have no clue what the problem might be...
>
> Thanks,
> Ryan
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss