- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Tru64 5.1B crash Process_tempid_list
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО10-05-2004 04:02 AM
тАО10-05-2004 04:02 AM
Tru64 5.1B crash Process_tempid_list
Well after deleting some files that I know are more important than clean underwear and restoring them from files created in memory when the CD boots I get the following error message and a crash.
process_tempid_list: New hardware ID is not unique.
This one stumps me, I can boot into single user with a kernel parameter change (hwc_auto_fix), but when I run /sbin/mountroot I get the error message. What I want to know is how does this process know that the HWID is not unique, and how do I get it not to care so that I can mount my boot disk where it's supposed to be and continue on my merry way?
I know that I can rebuild the cluster, that's not a problem, I'm doing this more as an exercise so that if I ever corrupt my production hwmgr database, I might be able to fix it and continue on, rather than rebuild the cluster, as I've had too in the past.
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 03:29 PM
тАО10-05-2004 03:29 PM
Re: Tru64 5.1B crash Process_tempid_list
You checked out 'man ddr_config' and 'man ddr.base' ?
Tru64, since version V5.0 and onwards really tries hard to have persistent device number over reboot and rebuilds. Once it is seen a given WWID, and handed it an HWID it want to keep it just so... for cluster support.
Yes, it will look around at 'other disks' while installing to pick up old names/numbers. So you really need to install on a clean disk, amongst clean (or disconnected) disks to renumber from 1.
Now, I'm pretty anal myself, and always wanted my disks to have 'nice' numbers, even though that does not really make a difference. (dsk1 is not much fast then dsk27 :-).
For that, I use dsfmgr -e and -m.
In doing so I would for example have dsk10..19 be Oracle Redo and Archive.
dsk20..29 Oracle data
dsk90..99 Online backups
We never went so low as to bother with emx numbering :-).
Cheers,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 09:18 PM
тАО10-05-2004 09:18 PM
Re: Tru64 5.1B crash Process_tempid_list
Why moving disks to other cluster members if you can simple add/remove cluster members on the fly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 11:42 PM
тАО10-05-2004 11:42 PM
Re: Tru64 5.1B crash Process_tempid_list
Then I thought that since I've had my hwmgr database creamed twice that it might be a nice execise to try to restore it, or replace it. Restoring it is no problem, but recreating seems to be an issue.
Since I knew from the start that this was not really the way HP wanted to see it's software installed I felt that opening a case with support was the wrong way to go about finding help, but I thought that this forum might be able to help, maybe someone had run into this before and could share that experience. I understand that for this cluster to be supported it will have to have been installed from scratch. But I also have supported clusters that I have had to reinstall from scratch because of hwmgr database corruptions. It's my biggest fear and I wanted to know if there is a way around it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 12:53 AM
тАО10-06-2004 12:53 AM
Re: Tru64 5.1B crash Process_tempid_list
There are enough best practise cookbooks out to protect your cluster, so why not read and use it?
Why not using the method to connect/create a new member and remove the old one prior to move the disks around?
Btw. if a support engineer will detect unsupported ways/methods on your machine it will reject support or change to "best effort". This is critical for a production system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2004 08:17 PM
тАО10-07-2004 08:17 PM
Re: Tru64 5.1B crash Process_tempid_list
hwmgr -remove name -entry mchan1
hwmgr -add name -component_name mchan \
-component_num 0 -component_typ CONTROLLER \
-parent_name pci -parent_num 1 -slot 2
hwmgr -show name
.
.
.
n/a: mchan0 stocli3 CONTROLLER pci1 slot 2
.
.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2004 09:32 PM
тАО10-07-2004 09:32 PM
Re: Tru64 5.1B crash Process_tempid_list
but booting a system not generated for the hardware is absolutly not supported and doesn't make sense because it is easier to create a new cluster than fixing problems due to the unsupported way...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2004 08:05 PM
тАО10-11-2004 08:05 PM
Re: Tru64 5.1B crash Process_tempid_list
Where does it state that? I agree that doing this is not a best practice.
However I was trying to point out that there are supported commands that can be used to fixed the adapter naming. There are valid reasons for wanting to do that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2004 06:27 PM
тАО10-12-2004 06:27 PM
Re: Tru64 5.1B crash Process_tempid_list
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2004 06:46 PM
тАО10-12-2004 06:46 PM
Re: Tru64 5.1B crash Process_tempid_list
You can not state it that way. "Totally different system" is not an absolute definition.
The original author of this topic replaced an ES40 with another ES40. This definitely falls outside the scope of "totally different system".