Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - Tru64 Unix
Showing results for 
Search instead for 
Did you mean: 

Hardware problem?

Bertram Fukuda
Regular Advisor

Hardware problem?

I have a ES-45 that I somewhat manage that hasn't recovered from a power outage over the weekend. When booting from >>> prompt, we get the following:

Problem cause was previous failure of command :"dsfmgr -R hwid 6"
NOTE: ADD inconsistent datum for registered device: unknown0 HWID-BNID was 6-1, is 29-6
Problem cause was previous failure of command :"dsfmgr -R hwid 6"
NOTE: Device naming failed boot configure or verify

Now the hard part, this system is located many miles from me and I don't have console access. So I'm depending on some helpful folks to be my eyes and hands.

I appreciate any help I can get.

Nick Bishop (Kiwi)
Frequent Advisor

Re: Hardware problem?

This could be painful, without a good way of getting screen output. But several things to try.

How long ago was the previous reboot?

What version of Tru64 are you running?

At the console prompt, give the output of these commands.
>>> show device

>>> show config
(just write down the disk units)

>>> show boot*
(this shows some console variables)

You can also try booting single-user mode
>>> boot -flags s
If it gets into single user mode, it will give a root shell, continue with the following, send us the output for commands that produce output.

# mount

# mount -u /
# mount

# (view the /etc/fstab, and for each local filesystem named within, mount it readonly)
# mount -r /usr
# mount -r /usr/users

# hwmgr -view device

# hwmgr -show scsi

# hwmgr -show scsi -full
(just write down the disk units, and anything to do with hwid 6)

The other thing is, if you've got output from those commands PRIOR to the failure, it would be useful, or if you've got sys_check output prior to the failure.

If it won't boot single user, then try booting from a cd ... get the Tru64 install CD and ...
>>> show device
(locate CD)
>>> boot dqa0 (or whatever your CD is)
(Get a shell window)
Type out the various hwmgr commands above and send their output.


Instead, if you want to boot the CD and mount the root disk to have a look (example if the root disk is dsk99 using the "a" partition), ...

# mkdir /etc/fdmns/temp_dmn
# ln -s /dev/disk/dsk99a /etc/fdmns/temp_dmn/dsk99a
# showfsets temp_dmn
(shows the name of the fileset within, assume "root")
# mount -r temp_dmn#root /mnt

That'll do for now. Anyone got other ideas?