- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: True 64 V5.1a NHD5 Orange Cameroun
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
тАО05-13-2004 05:16 AM
тАО05-13-2004 05:16 AM
Re: True 64 V5.1a NHD5 Orange Cameroun
>>>set heap_expand 4MB (biggest value)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 09:41 PM
тАО05-13-2004 09:41 PM
Re: True 64 V5.1a NHD5 Orange Cameroun
As written in the installation documentation you must set the srm variables correctly incl. clearing the bootdev.
The hardware must match the supported options (check cards, config issues and restrictions for an installation) and must be supported by 5.1A
Firmware must be uptodate to the one necessary for 5.1A.
On an EISA machine you must run ECU for Unix and disable not installed hardware (verify this).
All components must be identified by SRM.
(unknown leads to problem)
After that there is no reason why 5.1A will not run on such an old machine. So if it will not run doublecheck...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2004 02:29 PM
тАО05-19-2004 02:29 PM
Re: True 64 V5.1a NHD5 Orange Cameroun
Status update
1. Tried many thinks: removed all the boards; changed the CPUs to 300MHz; changed the memory to sync; installed only 1 CPU - same errors when booting from CD-ROM
2. After runing the ECU utility (but not doing any changes) and NOT saving the configuation - same errors when booting from CD-ROM
3. After runing the ECU utility (but not doing any changes) AND SAVING the configuration - no errors when booting from the CD-ROM.
4. Installed back all the boards (including the unknow board), the two 600MHz CPUs, the 1GiB EDO memory - no errors when booting from the CD-ROM.
WHY WHY WHY?????
Now I am instaling the Tru64 5.1A into a new disk to create a new kernel. After that I will copy this kernel to the old disk and will try to boot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2004 09:48 AM
тАО05-20-2004 09:48 AM
Re: True 64 V5.1a NHD5 Orange Cameroun
The ECU stores the config informations to the NVRAM, this information will be changed during update leading to "phantom" devices/hardware leading to crashes during boot.
PS: Using the "new kernel" on a totally different type of machine may not work. If creating an individual kernel hardware may vary, using genvmunix is a starter.... and as written before using a system disk from a totally different machine will not work due to the dynamic device databases. You never give up, right? ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2004 10:11 AM
тАО05-20-2004 10:11 AM
Re: True 64 V5.1a NHD5 Orange Cameroun
Yes, never.
1st, this servers was a production system running Windows NT (Alpha) for years in a local telephonic compnay w/o problems.
I bought it very cheap AFTER testing it (including a lot of disks).
My first try was moving the disks from my AS100A to this new server were the problems appear.
After testing back with Windows NT, Tru64 4.0F, Debian Linux (all runing very well) I suppose that the problem is only with Tru64 5.x.
So, I can not give up.
Now the AS4000 has all the boards back and the Tru64 5.1A is installed and running.
Now my next step is moving the new kernel to my old boot disk (with all my configurations). If this works I have a solutions to this infamous problem.
Wait for my next chapter ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2004 10:19 AM
тАО05-20-2004 10:19 AM
Re: True 64 V5.1a NHD5 Orange Cameroun
If this is consisten problem, this problem must rise with all versions of Tru64 and all operating systems and not only with Tru64 5.x.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-21-2004 06:21 AM
тАО05-21-2004 06:21 AM
Re: True 64 V5.1a NHD5 Orange Cameroun
Invalid ECU configuration is a well known problem after update - why not study documentation preventing such an issue? Due to the dynamic configuration it will always lead to a problem on V5.x. In V3.x and V4.x it always crashed with invalid NVRAM information if ECU was not running after srm upgrade, btw. WinNT uses ARC and not SRM so NVRAM information differ (ECU for ARC and ECU for SRM differences!).
And the problem of moving a disk to a totally different machine starting at V5.x is also well known and is documented as "not supported". Copying a kernel from another machine may not work - also well known due to technical facts.
So why ignoring technical facts and not learning some of the machine type (ECU/SRM/ARC) and Tru64 basics?
- « Previous
- Next »