1856381 Members
17084 Online
104112 Solutions
New Discussion

Re: AS/U-9000

 
SOLVED
Go to solution
P.W.C. Visser
Occasional Advisor

AS/U-9000

Had a system crash. After auto-recovering from my tape, AS/U won't start anymore.
nbutil -N start gives: Error opening /dev/netbiosdg, errno 19.
Can anyone tell me what's wrong?
Thanks in advance, Peter Visser Dutch Royal Navy
12 REPLIES 12
Steven E. Protter
Exalted Contributor

Re: AS/U-9000

If its in /dev sometimes insf -e after an ioscan helps.

Looks like the tape was incomplete or the recovery didn't finish.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Cheryl Griffin
Honored Contributor
Solution

Re: AS/U-9000

check that the drivers are in the kernel:
# lsdev |egrep -e "lmx|net"
Character Block Driver Class
237 -1 netbios unknown
238 -1 netbiosdg unknown
239 -1 lmxloop pseudo

Then compare these devices:
# ll /dev/netbios* /dev/lmxloop
crw-rw-rw- 1 root sys 72 0x0000ed Feb 18 07:20 netbios
crw-rw-rw- 1 root sys 72 0x0000ee Feb 18 07:20 netbiosdg
crw-rw-rw- 1 root sys 72 0x0000ef Feb 18 07:20 lmxloop

If they do not exist, use mknod to create them.
"Downtime is a Crime."
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Hi Steven and Cheryl,

Thanks for answering so fast.

Steven:
insf -e then:
Don't know to handle driver "netbiosdg", "lmxloop" and "netbios"

Cheryl:
The special files seems to be there. Only all they are "pseud"
I don't know is this has something to with it bet also are listed : netdiag1, netman, 2x inet_cots as "unknown"

Greetings Peter
Cheryl Griffin
Honored Contributor

Re: AS/U-9000

pseudo is good. Unknown (as in my example) would have indicated that the drivers were not in the kernel.

What does the following show?
# lssf /dev/netbios* /dev/lmxloop
"Downtime is a Crime."
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Hi Cheryl again,
I guess something is wrong with the number 145. shouldn't that be 168?
If so, how could that happen and how can i fix that. I am not a guru!
Greetings from Holland, Peter

145 -1 netbios pseudo
169 -1 netbiosdg pseudo
170 -1 lmxloop pseudo
hpg60:/sbin/init.d#ll /dev/netbios* /dev/lmxloop
crw-rw-rw- 1 root sys 72 0x00004e Dec 10 1999 /dev/lmxloop
crw-rw-rw- 1 root sys 72 0x00004c Aug 22 2003 /dev/netbios
crw-rw-rw- 1 root sys 72 0x00004d Dec 10 1999 /dev/netbiosdg
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Hi Cheryl,

Answer on your question:

hpg60:/sbin/init.d#lssf /dev/netbios* /dev/lmxloop
pseudo driver clone minor 0x00004c /dev/netbios
pseudo driver clone minor 0x00004d /dev/netbiosdg
pseudo driver clone minor 0x00004e /dev/lmxloop

Thanks so far for helping me, Peter
Rainer von Bongartz
Honored Contributor
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Hi Cheryl, Steven and Rainer,

As you can see: I became a link from Rainer, in which the "almost" cause, the problem and the fix exactly is described.
Reading this document tells me that Cheryl and Steven where leading me to the same solution.
I'll try this tomorrow (i'am home now) and you'll all hear from me.
One question about the value of the Character 237,238 and 239: Are those values important? I'm asking this because I saw those values already on a good working system (A k360 with UX11.0).
The problem exists on a G60 with UX10.20.
Have a nice evening and "see" you all tomorrow,
Peter Visser
Cheryl Griffin
Honored Contributor

Re: AS/U-9000

Peter,
The 237, 238, 239 is not required. It really depends on what you have installed on the system.

For instance on another diag system here, I have:
# lsdev |egrep -e "netbi|lmx"
139 -1 netbios pseudo
140 -1 netbiosdg pseudo
141 -1 lmxloop pseudo

# ll /dev/netb* /dev/lmx*
crw-rw-rw- 1 root sys 72 0x00008b Sep 20 2001 /dev/netbios
crw-rw-rw- 1 root sys 72 0x00008c Oct 24 2001 /dev/netbiosdg
crw-rw-rw- 1 root sys 72 0x00008d Jun 12 2001 /dev/lmxloop

You see that 72 is the major number and when you use the mknod to recreate the devices the number specified is from the lsdev output. In my example here I'd use:
# mknod /dev/netbios c 72 139
# mknod /dev/netbiosdg c 72 140
# mknod /dev/lmxloop c 72 141

At this point, I am guessing from the systems I've looked at but the 139 140 141 character devices are on 10.20 and the 237 238 239 is on 11.00 systems.

Your output is even more different.
145 -1 netbios pseudo
169 -1 netbiosdg pseudo
170 -1 lmxloop pseudo
# mknod /dev/netbios c 72 145
# mknod /dev/netbiosdg c 72 169
# mknod /dev/lmxloop c 72 170

I believe the devices are the problem. They don't correspond to the driver.
Your devices are:
0x00004e (lmxloop) --> 4e in hex = 78
0x00004c (netbios) --> 4c in hex = 76
0x00004d (netbiosdg)-> 4d in hex = 77

rmsf your devices and mknod to recreate them.
"Downtime is a Crime."
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Good morning Cheryl, Rainer and Steven,

My problem is solved!

Cheryl, as you stated, the incorrect minor numbers from devicefiles: netbios, netbiosdg and lmxloop where the cause of my problem. I did, as you suggested, a rmsf and a mknod of them and the netdemon starts normal again. Net start server did the rest.... up en running. Thank you very very much for your help!

Rainer, the link to the document was very helpfull too, with that document i would have had the same result. Also thank you!

Steven, also thank you. Your suggestion was a good start.

Greetings to all of you from Holland and thanks again, Peter Visser

Rainer von Bongartz
Honored Contributor

Re: AS/U-9000

Peter,

Here is another link to a whole bunch of AS/U related documents

http://www5.itrc.hp.com/service/iv/node.do?node=prodITRC%2FWW_Start%2FN1%7C22%7C1

Regards
Rainer
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
P.W.C. Visser
Occasional Advisor

Re: AS/U-9000

Hi Rainer,

Thanks again for those links. As already told
is AS/U working fine again although how this could happen is a big question for me. AS/U was online already for 8 years (on G60 UX10.20) and 4 years (on K360 UX11.0) without any problems. Each week I do a the AS/U maintain script on both servers (PDC's), which I got a couple of years ago from German AS/U support. The name of the support-engineer was something like Weichert as far as I can remember.
Thanks again for your support and have a nice weekend.

Regards,
Peter