UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1027 views

bad_magic_number creating nss volume

Hi all: I have a real problem with a server I just upgraded from OES11 SP1 to SP2. Following the upgrade I lost an nss volume on the server. Since I have good backup I went and removed the pool (no volume was present). I recreated the nss pool but when I try and create a volume from the pool I get this zerr_bad_magic_number(20161).

I have opened an SR with Novell and they are at a loss to fix this issue. I am wondering if anyone else on this forum has seen a similar problem?

Chris.
Labels (2)
0 Likes
6 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

cmosentine;2310455 wrote:
Hi all: I have a real problem with a server I just upgraded from OES11 SP1 to SP2. Following the upgrade I lost an nss volume on the server. Since I have good backup I went and removed the pool (no volume was present). I recreated the nss pool but when I try and create a volume from the pool I get this zerr_bad_magic_number(20161).

I have opened an SR with Novell and they are at a loss to fix this issue. I am wondering if anyone else on this forum has seen a similar problem?


Hi Chris,

How exactly did you do the upgrade from OES11 SP1 to OES11 SP2 (offline/online)?

As a starting point, could you post the output of the following commands:

uname -a

rpm -qa|grep -i "kernel\|nss-"

zypper ca


Cheers,
Willem
0 Likes
Absent Member.
Absent Member.

Thanks for the reply. The answers to your questions are below. One thing I noticed yesterday is that the _admin volume is not showing up (via Windows Explorer) like it does on everyone one of our other servers. The _admin volume is mounted on the server.

Chris.


>>> magic31<magic31@no-mx.forums.novell.com> 3/11/2014 4:46 PM >>>



>How exactly did you do the upgrade from OES11 SP1 to OES11 SP2
>(offline/online)?


The upgrade was via "wagon"


>As a starting point, could you post the output of the following
>commands:


GR13:~ # uname -a
Linux GR13 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux


GR13:~ # rpm -qa|grep -i "kernel\|nss-"
novell-nss-32bit-4.16.4893-0.5.2
novell-plugin-nss-3.7.636-0.6.3
nss-kmp-default-4.15.4362_3.0.13_0.27-2.1
kernel-default-base-3.0.13-0.27.1
linux-kernel-headers-2.6.32-1.13.5
kernel-firmware-20110923-0.48.1
kernel-source-3.0.101-0.15.1
yast2-novell-nss-2.13.10-0.7.28
kernel-default-devel-3.0.101-0.15.1
novell-nss-nlvm-1.1.4893-0.5.1
kernel-default-3.0.13-0.27.1
novell-nss-nlvm-32bit-1.1.4893-0.5.1
mozilla-nss-3.15.4-0.7.1
novell-nss-admin-session-sfcb-provider-1.0.1-0.13.1
novell-nss-ncpid-32bit-1.1.4893-0.5.1
novell-nss-4.16.4893-0.5.2
novell-nss-ncpid-1.1.4893-0.5.1
mozilla-nss-32bit-3.15.4-0.7.1


GR13:~ # zypper ca
# | Alias | Name | Enabled | Refresh
---+----------------------------------------------------+---------------------------------------------------+---------+--------
1 | Novell-Open-Enterprise-Server-11-SP2_11.2.2-1.267 | Novell-Open-Enterprise-Server-11-SP2 11.2.2-1.267 | Yes | Yes
2 | SMT-http_gr11_vrapc_cxm:OES11-SP2-Pool | OES11-SP2-Pool | Yes | Yes
3 | SMT-http_gr11_vrapc_cxm:OES11-SP2-Updates | OES11-SP2-Updates | Yes | Yes
4 | SMT-http_gr11_vrapc_cxm:SLES11-SP1-Pool | SLES11-SP1-Pool | No | Yes
5 | SMT-http_gr11_vrapc_cxm:SLES11-SP1-Updates | SLES11-SP1-Updates | No | Yes
6 | SMT-http_gr11_vrapc_cxm:SLES11-SP2-Core | SLES11-SP2-Core | No | Yes
7 | SMT-http_gr11_vrapc_cxm:SLES11-SP2-Extension-Store | SLES11-SP2-Extension-Store | No | Yes
8 | SMT-http_gr11_vrapc_cxm:SLES11-SP2-Updates | SLES11-SP2-Updates | No | Yes
9 | SMT-http_gr11_vrapc_cxm:SLES11-SP3-Extension-Store | SLES11-SP3-Extension-Store | No | Yes
10 | SMT-http_gr11_vrapc_cxm:SLES11-SP3-Pool | SLES11-SP3-Pool | Yes | Yes
11 | SMT-http_gr11_vrapc_cxm:SLES11-SP3-Updates | SLES11-SP3-Updates | Yes | Yes
12 | SUSE-Linux-Enterprise-Server-11-SP3_11.3.3-1.138 | SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138 | Yes | Yes
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

cmosentine;2310592 wrote:
Thanks for the reply. The answers to your questions are below. One thing I noticed yesterday is that the _admin volume is not showing up (via Windows Explorer) like it does on everyone one of our other servers. The _admin volume is mounted on the server.



Ok, from the output you've posted back the first thing that sticks out for me is that your running kernel (3.0.13-0.27) and installed kernel package doesn't match the recent ones that apply to OES11 SP2.

We can see the kernel-source package has been updated to "kernel-source-3.0.101-0.15.1", but the kernel base is still at "kernel-default-base-3.0.13-0.27.1".

Has your kernel base package maybe been locked that's preventing it from updating? That could well be something that was done long ago, but forgotten or left on that version for some reason.

My first suggestion would be to get those old kernel packages and their dependencies updated, as hopefully that will clear the error with accessing/creating the nss volume.

Curious to know how you go!

-Willem
0 Likes
Absent Member.
Absent Member.

On 3/11/2014 8:07 PM, cmosentine wrote:

Hi cmosentine

> I have opened an SR with Novell and they are at a loss to fix this
> issue. I am wondering if anyone else on this forum has seen a similar
> problem?
> Chris.


Can you please post the SR number ?
I'm very curious as to why we are 'at a loss'.

Thanks
Hans

0 Likes
Absent Member.
Absent Member.

magic31;2310599 wrote:
Ok, from the output you've posted back the first thing that sticks out for me is that your running kernel (3.0.13-0.27) and installed kernel package doesn't match the recent ones that apply to OES11 SP2.

We can see the kernel-source package has been updated to "kernel-source-3.0.101-0.15.1", but the kernel base is still at "kernel-default-base-3.0.13-0.27.1".

Has your kernel base package maybe been locked that's preventing it from updating? That could well be something that was done long ago, but forgotten or left on that version for some reason.

My first suggestion would be to get those old kernel packages and their dependencies updated, as hopefully that will clear the error with accessing/creating the nss volume.

Curious to know how you go!

-Willem


I had nearly the exact same problem when I patched from OES 11.1 (SP1) to OES 11.2 (SP2).

Once I updated my kernel-base to match the newer kernel-source, a reboot, the issue is resolved.

Good call. As it turned out, the kernel was not updated because it conflicted with a Brocade driver which I don't use. I ignored the error and updated the kernel.

Thank You!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

sburmann;2334107 wrote:
...Good call. As it turned out, the kernel was not updated because it conflicted with a Brocade driver which I don't use. I ignored the error and updated the kernel.


Interesting conflict.... (as in curious why that would happen).

Is this a physical or virtual OES server instance? I'm curious to where that Brocade driver came from (SUSE repositories or from some applied vendor pack)...

Good to know this thread at least got you pointed in the right direction! 🙂

Cheers,
Willem
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.