From: Copper, Steve (scopper@westernpower.co.uk)
Date: Thu Dec 09 2004 - 08:53:51 EST
All,
Thanks to Howard Arnold and Eric Mortensen for their replies (listed below).
Unfortunately none of their suggestions worked. In the end I had to recreate
the hardware database files, following a procedure from HP.
Howards' reply:
If you are booting the install CD try and set the bootdef_dev "" and see if
this helps. I have ran into things like this before and it was tied to the
bootdef_dev being set to an old install.
Erics' reply:
I'm not sure if this will solve your problem, but anytime I've ever had
problems with the scsi device database and related files, the following
command has helped to fix the problem:
/sbin/dsfmgr -vVF
Run it a few times to see if it will come back clean.
Then if you're using advfs filesystem you could also run:
/sbin/advfs/verify
On each of the filedomains in /etc/fdmns to double-check that there's no
additional filesystem corruption.
Thanks again,
Steve
-----Original Message-----
All,
We have an ES40 which we were about to upgrade to version 5.1B from 5.1A
pk4. We have got as far as installing the new firmware levels (6.7),
everything seemed to go ok on this part. But since then we have not been
able to boot the server past the single user mode. We can boot into single
user mode, but from there on any commands like "mountroot" or "bcheckrc"
cause the system to crash.
The only message that we can catch in time before it disappears is:-
process_tempid_list: New hardware ID is not unique.
I am thinking that there is a problem with the device driver databases in
/etc, especially the files dec_unid_db, dec_scsi_db and dec_hw_db.
Possibly related to this is that when we perform the "hwmgr show scsi"
command all the device names return as being "null". If I do a "dn_setup
-install_tape" and then show the devices again, all the names are present.
However this does not have any affect on stopping the problem when we try
and boot the system any further.
Would anyone have any ideas as to what has gone on here and more importantly
how to fix it!
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:12 EDT