Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hp-pcd!hpfcso!hpfcdc!rodean
From: rodean@hpfcdc.HP.COM (Bruce Rodean)
Newsgroups: comp.sys.hp
Subject: Re: 400dl won't boot
Message-ID: <5570559@hpfcdc.HP.COM>
Date: 15 Jan 91 23:03:16 GMT
References: <1991Jan15.155520.7406@sat.uucp>
Organization: Hewlett-Packard Co., Ft. Collins, CO.
Lines: 30

In article <1991Jan15.155520.7406@sat.uucp> root@sat.uucp writes:
> I have a HP 9000/400dl discless node that won't boot.  All I get is the
> message:
> Secondary Loader Revision: 64.2
> Booting /hp-ux
> 
> and then a blank screen.
> 
> Any suggestions?

I would check the device files for that node.  From the server execute
'll -H /dev+/<node>' where <node> is the name of the node that won't
boot.  You should see something like:

crw--w--w-   3 myself   users      0 0x000000 <node>   Jan 15 08:23 console
crw-rw-rw-   1 root     other     12 0x000000 <node>   Dec 13 09:24 crt

where once again, <node> should be the name of that node.  If it is some
other name, then your device files are no good as they "belong" to
another node.  See the discussion in the mknod.1m manual entry for
Device Special Files where it talks about the cnode_name option.  It
points you to the mkrnod system call.

Did you use SAM to add the node?

Bruce Rodean
rodean@hpfclg.fc.hp.com

This does not reflect the official position of Hewlett-Packard Co.  No
guarantees of any kind are give or implied.