My summary - as promised.
Thanks to the only response from Dr. Thomas Blinn for his solution. The
complete text is included at the end.
The short solution is:
1) mount -u /
to make root read-write
2) cd /dev
3) rm kevm*
4) sync
5) cd /
6) reboot
It worked without a hitch, and recreated the kevm* devices on reboot.
Everything appears to be running normally after the reboot.
BTW: We were able to bring the system up to multi-user level manually -
mount -u
mount -a
init 3
seemed to do the trick for a short term (until the next reboot) fix.
Thanks for this great list. It is one of my primary technical resources.
Joyce Johns
Gtech Corp.
joyce.johns_at_gtech.com
Original Post:
> Fellow managers,
>
> I have a DS20E which was recently (last week) upgraded from 4.0F
to 5.0A,
> then 5.1 - all with AdvFs. This is actually one of 20 systems
which are in
> the process of being upgraded, but it is currently the only one
with this
> problem. All has been running well until today, when the
developers
> decided they needed to reboot. I now see the following on every
attempt to
> reboot, even after a power-cycle:
>
> Dev Nodes:
> ERROR: wrong ldev major # (83,0):
/dev/kevm:84
> ERROR: wrong ldev major # (83,2):
/dev/kevm.pterm:84
>
> Total errors = 2
> bcheckrc: Device naming failed boot.....
>
> The system is now in single user mode.
>
> I searched the archives and found the following in the only
matching
> posting, but alas, there was no summary.
>
> it reboots and then hangs in single user mode with the following
error:
> Dev Nodes: Wrong ldev major (#82,00): /dev/kev: 84
> Wrong ldev major (#82,00): /dev/kev: 84 Errors 2 bcheckrc:
> Device naming failed boot configure or verify.
> Please correct problem and continue or reboot.
> Has anyone ever seen this before?
>
> Can't seem to find anything in the documentation either....
Knowing that I
> am not the first or the only one to experience this perplexing
problem
> helps, but some helpful information would be even better.
>
> I will summarize.
>
> TIA,
> Joyce Johns
> joyce.johns_at_gtech.com
I'm sure there is an official way to do this, but
here's what I'd try:
1) mount -u /
to make root read-write
2) cd /dev
3) rm kevm*
4) sync
5) cd /
6) reboot
and see if it makes it further. It seems to be
complaining that you
have a bad kevm device; "kevm" relates to the kernel
event monitor,
if you remove the bad device names, they should get
recreated on the
next boot with the correct major/minor numbers.
If that doesn't fix it, you might need some dsfmgr
incantation, there
is a reference page but it's rather opaque, and I
don't remember all
of the details off hand.
Tom
Dr. Thomas P. Blinn + UNIX Software Group + Compaq
Computer Corporation
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New
Hampshire 03062-2698
Technology Partnership Engineering
Phone: (603) 884-0646
Internet: tpb_at_zk3.dec.com Compaq's
Easynet: alpha::tpb
ACM Member: tpblinn_at_acm.org PC_at_Home:
tom_at_felines.mv.net
Worry kills more people than work because more
people worry than work.
Keep your stick on the ice. -- Steve
Smith ("Red Green")
My favorite palindrome is: Satan, oscillate my
metallic sonatas.
-- Phil Agre,
pagre_at_alpha.oac.ucla.edu
Yesterday it worked / Today it is not working /
UNIX is like that
-- apologies to Margaret
Segall
Opinions expressed herein are my own, and do not
necessarily represent
those of my employer or anyone else, living or
dead, real or imagined.
Received on Wed Feb 14 2001 - 13:27:31 NZDT