Re: [OpenIndiana-discuss] Cannot _init zfs module after upgrade
I use qemu-kvm also (but in linux), I start my machine with the below command qemu-kvm -drive file=disk01.img,cache=none,media=disk -m 4G -cdrom oi-dev-151a-x86.iso -serial telnet:127.0.0.1:2323,server -boot c -net nic -net tap,ifname=tap0,script=no,downscript=no on another session, telnet 127.0.0.1 2323. Once you have grub, enable kmdb by adding -kd to the kernel line and change the console to ttya instead of graphics. Your kernel line should look like kernel$ /platform/i86pc/kernel/$ISADIR/unix -kd -B $ZFS-BOOTFS,console=ttya This way, kmdb will be loaded before the kernel and you will end up in its prompt, type :c to continue execution On Sun, Jul 29, 2012 at 3:41 PM, Andreas Stenius andreas.sten...@astekk.sewrote: 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 [0xfb80, 0xfb964f3b] data at 0xfbc0 module /kernel/amd64/genunix: text at [0xfb964f40, 0xfbbec58f] data at 0xfbc95440 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@0,0 PCI-device: isa@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=fbc2f260: Cannot _init zfs module Warning - stack not written to the dump buffer fbc718e0 genunix:rootconf+1a8 () fbc71920 genunix:vfs_mountroot+63 () fbc71950 genunix:main+136 () fbc71960 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.john...@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@dtrace:~$ which hg which: no hg in (/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin) ryan@dtrace:~$ sudo pkg install mercurial Password: Packages to install: 3 Packages to update:53 Create boot environment: Yes DOWNLOAD PKGS FILESXFER (MB) Completed56/56 7567/7567 98.4/98.4 PHASEACTIONS Removal Phase164/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
Re: [OpenIndiana-discuss] Cannot _init zfs module after upgrade
Thanks! I guess kmdb is some sort of kernel mode debugger? I'll have to google that... :) But I'll wait for some support from experienced oi developers before digging into this. I'll use the workarounds presented in the mean time. //Andreas 2012/7/29 Mohamed Khalfella khalfe...@gmail.com: I use qemu-kvm also (but in linux), I start my machine with the below command qemu-kvm -drive file=disk01.img,cache=none,media=disk -m 4G -cdrom oi-dev-151a-x86.iso -serial telnet:127.0.0.1:2323,server -boot c -net nic -net tap,ifname=tap0,script=no,downscript=no on another session, telnet 127.0.0.1 2323. Once you have grub, enable kmdb by adding -kd to the kernel line and change the console to ttya instead of graphics. Your kernel line should look like kernel$ /platform/i86pc/kernel/$ISADIR/unix -kd -B $ZFS-BOOTFS,console=ttya This way, kmdb will be loaded before the kernel and you will end up in its prompt, type :c to continue execution On Sun, Jul 29, 2012 at 3:41 PM, Andreas Stenius andreas.sten...@astekk.sewrote: 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 [0xfb80, 0xfb964f3b] data at 0xfbc0 module /kernel/amd64/genunix: text at [0xfb964f40, 0xfbbec58f] data at 0xfbc95440 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@0,0 PCI-device: isa@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=fbc2f260: Cannot _init zfs module Warning - stack not written to the dump buffer fbc718e0 genunix:rootconf+1a8 () fbc71920 genunix:vfs_mountroot+63 () fbc71950 genunix:main+136 () fbc71960 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.john...@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@dtrace:~$ which hg which: no hg in (/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin) ryan@dtrace:~$ sudo pkg install mercurial Password: Packages to install: 3 Packages to update:53 Create boot environment: Yes DOWNLOAD PKGS FILESXFER (MB) Completed56/56 7567/7567 98.4/98.4 PHASEACTIONS Removal Phase164/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
Re: [OpenIndiana-discuss] Cannot _init zfs module after upgrade
Thanks Lucas. That worked like a charm :)
2012/7/18 Lucas Van Tol catsey...@hotmail.com:
I have been using this as my pkg command on some systems; adding the current
'kernel' package to the list of to-be installed.
currentkern=$(pkg list -v kernel | grep pkg | awk '{print $1}') ; pkg install
--deny-new-be $currentkern *packagetobeinstalled*
Try it with '-nv' first; and verify the packages you expect are getting
installed...
currentkern=$(pkg list -v kernel | grep pkg | awk '{print $1}') ; pkg install
-nv --deny-new-be $currentkern *packagetobeinstalled*
-Lucas Van Tol
Date: Tue, 17 Jul 2012 10:52:33 +0100
From: t12nsloo...@gmail.com
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] Cannot _init zfs module after upgrade
you could try installing a specific version of mercurial ...
jadams@jadlaptop:~$ pkg info -r mercurial@1.3.1-0.151.1.2
Name: developer/versioning/mercurial
Summary: The Mercurial Source Control Management System
Description: A fast, lightweight source control management system designed
for efficient handling of very large distributed projects.
Category: Development/Source Code Management
State: Not installed
Publisher: openindiana.org
Version: 1.3.1
Build Release: 5.11
Branch: 0.151.1.2
Packaging Date: Thu Feb 9 20:02:25 2012
Size: 6.78 MB
FMRI:
pkg://openindiana.org/developer/versioning/mercurial@1.3.1,5.11-0.151.1.2:20120209T200225Z
Jon
On 17 July 2012 01:51, Ryan Johnson ryan.john...@cs.utoronto.ca wrote:
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@dtrace:~$ which hg
which: no hg in (/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin)
ryan@dtrace:~$ sudo pkg install mercurial
Password:
Packages to install: 3
Packages to update:53
Create boot environment: Yes
DOWNLOAD PKGS FILESXFER (MB)
Completed56/56 7567/7567 98.4/98.4
PHASEACTIONS
Removal Phase164/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@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Cannot _init zfs module after upgrade
Nailed it, I asked at #openindiana and got the immediate suggestion that my pkg's may be out sync. And given that I got a new BE (and kernel) from installing a package, not by pkg update, I felt it plausible. Now, I have a working oi151a5! All it took was to update to the latest version to avoid having pkg pull in updates for the kernel, skipping other parts, leaving the system out of sync and order. Big thanks to Richard Yao (ryao) and @Meths on #openindiana! //Andreas 2012/7/29 Andreas Stenius andreas.sten...@astekk.se: 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 [0xfb80, 0xfb964f3b] data at 0xfbc0 module /kernel/amd64/genunix: text at [0xfb964f40, 0xfbbec58f] data at 0xfbc95440 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@0,0 PCI-device: isa@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=fbc2f260: Cannot _init zfs module Warning - stack not written to the dump buffer fbc718e0 genunix:rootconf+1a8 () fbc71920 genunix:vfs_mountroot+63 () fbc71950 genunix:main+136 () fbc71960 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.john...@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@dtrace:~$ which hg which: no hg in (/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin) ryan@dtrace:~$ sudo pkg install mercurial Password: Packages to install: 3 Packages to update:53 Create boot environment: Yes DOWNLOAD PKGS FILESXFER (MB) Completed56/56 7567/7567 98.4/98.4 PHASEACTIONS Removal Phase164/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@openindiana.org
[OpenIndiana-discuss] OpenSolaris on SPARC
Hello all, There are some discussions about whether illumos on SPARC is a dead-end or not (i.e. whether it is stupid to buy HW systems from the one vendor and not buy their software support, or if there is more than one vendor, or if anyone would pick up the open-sourced processor designs for the Niagaras and build some cool appliances or servers). So, just for the anecdotal sake, I wanted to share this weekend's experience about OpenSolaris on SPARC - and how it saved the day. While it may seem unlikely at this moment that new SPARC systems would be rolled out for OI to get installed on them, there are many already-deployed reliable boxes which would run obsolete (or our new) software until they fscking die. I was asked to look at a T2000 with Sol 10u8 which did just that: it died during what could have been fsck - if ZFS had one. Apparently, the system's users did nothing formally invalid, they were just zfs-sending and zfs-receiving some datasets within the pool in order to recompress older data with gzip-9, then they tried to destroy the older dataset tree and rename the compressed copy to take its place. Something went wrong, the pool locked up with no IOs taking place (according to iostat). The zfs commands all hung, however zpool status and friends did not. Filesystem operations also went well, so running zones were properly stopped and the box was ultimately rebooted. It did not come back up. Luckily, there was a Solaris installation server in that network, so it took a few minutes to prepare a LAN installation resource from a stashed SXCE snv_129_sparc image, and boot the T2000 from the network, into single user mode. OpenSolaris found nothing suspicious about the data pool and the rpool, imported and exported them without complaints. While at the rpool, we deleted the /etc/zfs/zpool.cache file to allow the system to boot its Solaris 10. It booted, but also hung at subsequent zpool import -R / pool request - in the same way: no iostat operations to report, and no errors in the logs... Back to the networked boot of OpenSolaris, where we imported the data pool, destroyed the remaining old uncompressed datasets and completed the renaming of compressed datasets to take place of those ones, transparently to the zones and other consumers. This did unclog something, so the Solaris 10 image did afterwards quickly import the pool and happily uses it today. Yesterday the old OpenSolaris SXCE for SPARC did save the day. I can easily imagine hitting some bugs in ZFS that were fixed after the last SXCE release, where a hypothetical OpenIndiana for SPARC image would be able to save us - even if it is not (yet) used as the everyday OS for the box. Hope this story entertains someone and helps others, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
