[OpenIndiana-discuss] Cannot _init zfs module after upgrade
Jonathan Adams
t12nslookup at gmail.com
Tue Jul 17 09:52:33 UTC 2012
you could try installing a specific version of mercurial ...
jadams at jadlaptop:~$ pkg info -r mercurial at 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.johnson at 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 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
More information about the OpenIndiana-discuss
mailing list