- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Hardware problem?
Operating System - Tru64 Unix
1753365
Members
6308
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2009 06:38 PM
11-30-2009 06:38 PM
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.
Thanks,
Bert
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.
Thanks,
Bert
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2009 09:01 PM
12-08-2009 09:01 PM
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.
WHATEVER YOU DO, NEVER USE THE COMMAND mkfdmn.
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?
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.
WHATEVER YOU DO, NEVER USE THE COMMAND mkfdmn.
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?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP