HP 9000 and HP e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Physical Memory added to the system but not detected on boot

Sousaman
Occasional Advisor

Physical Memory added to the system but not detected on boot

Good day,

Please can any one help me. I have increased the RAM size of my system (two node cluster) from 8GB to 12GB by installing 4x1GB physical memories each. On one Node it was automatically detected after boot but did not happended on the second node. although when I run ioscan I can see 8 modules on memories but when I look to the physical memory it still showing 8GB. I also run insf but no change was shown. I did a reboot but the result is the same. Now what are way to refresh?

thanks in adv.
8 REPLIES
Torsten.
Acclaimed Contributor

Re: Physical Memory added to the system but not detected on boot

Please post the result of

# model
# uname -a
# echo "selclass qualifier memory;info;wait;infolog" | /usr/sbin/cstm

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Dennis Handly
Acclaimed Contributor

Re: Physical Memory added to the system but not detected on boot

It would be helpful if you could provide your OS version and your machine model.
Sousaman
Occasional Advisor

Re: Physical Memory added to the system but not detected on boot

Thanks for reply. bellow are the info you required:
#Model: 9000/800/rp4440
#uname -a HP-UX Node1 B.11.11 U 9000/800 2376839995 unlimited-user license

#cstm>selclass qualifier memory;info;wait;infolog
-------------
Basic Memory Description

Module Type: MEMORY
Total Configured Memory : 8192 MB
Page Size: 4096 Bytes

Memory interleaving is supported on this machine and is ON.

Memory Board Inventory

DIMM Slot Size (MB)
--------- ---------
1A 1024
1B 1024
1C 1024
1D 1024
2A 1024
2B 1024
2C 1024
2D 1024
--------- ---------
System Total (MB): 8192

Memory Error Log Summary

The memory error log is empty.

Page Deallocation Table (PDT)

PDT Entries Used: 0
PDT Entries Free: 3000
PDT Total Size: 3000
-- Information Tool Log for MEMORY on path 8 --
View - To View the file.
Print - To Print the file.
SaveAs - To Save the file.
Enter Done, Help, Print, SaveAs, or View: [Done] #.

sousaman
Torsten.
Acclaimed Contributor

Re: Physical Memory added to the system but not detected on boot

Dimms in slots 0... are missing - check them.

Also check if your diagnostics software is current, your version may be too old.

I would expect an output like this:

...

Hardware path: 8


Basic Memory Description

Module Type: MEMORY
Total Configured Memory : 16384 MB
Page Size: 4096 Bytes

Memory interleaving is supported on this machine and is ON.

Memory Board Inventory

DIMM Slot Size (MB)
--------- ---------
0A 2048
0B 2048
0C 2048
0D 2048
1A 2048
1B 2048
1C 2048
1D 2048
2A 0
2B 0
2C 0
2D 0
3A 0
3B 0
3C 0
3D 0
--------- ---------
System Total (MB): 16384

Memory Error Log Summary

The memory error log is empty.

Page Deallocation Table (PDT)

PDT Entries Used: 0
PDT Entries Free: 3000
PDT Total Size: 3000
...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Sousaman
Occasional Advisor

Re: Physical Memory added to the system but not detected on boot

Yes!
But how to check and refresh it, because phisical the memories are installed, and actually these missing DIMMs slots were already installed in before the increase.
what I actually added was on the:
2A 1024
2B 1024
2C 1024
2D 1024
The output on the second node is what was expected.

#------
Basic Memory Description

Module Type: MEMORY
Total Configured Memory : 12288 MB
Page Size: 4096 Bytes

Memory interleaving is supported on this machine and is ON.

Memory Board Inventory

DIMM Slot Size (MB)
--------- ---------
0A 1024
0B 1024
0C 1024
0D 1024
1A 1024
1B 1024
1C 1024
1D 1024
2A 1024
2B 1024
2C 1024
2D 1024
--------- ---------
System Total (MB): 12288

Memory Error Log Summary

Error
Board Error Address Error Type Page Count
------------- ----------------- ---------- --------- -----
2b 0x00000000dd327d80 Single-Bit 0x00dd327 1

System start: Wed Dec 31 22:52:07 2008.
Last error check: Fri Jan 2 12:55:09 2009.
Logging interval: 3600 seconds.
1 address(es) with errors logged by memory logging daemon.

The Logtool Utility provides full details about the memory error log.

Page Deallocation Table (PDT)

PDT Entries Used: 0
PDT Entries Free: 3000
PDT Total Size: 3000



regards
Torsten.
Acclaimed Contributor

Re: Physical Memory added to the system but not detected on boot

Install the latest diags first and you will probably get a better information:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Sousaman
Occasional Advisor

Re: Physical Memory added to the system but not detected on boot

Hi
Thanks for the first tip.
I have installed the updated Online Diagnostic and actually the output gives me is as bellow. As I said. on the DIMM slots 0x got placed the memories but it shows 0 as you can see. the only one I added are on the slots 2x. Its stop seing the slots 0x after installing the memories on stots 2x.
what can I do to refresh the slots 0x.
the output now is:

-- Information Tool Log for MEMORY on path 8 --

Log creation time: Fri Jan 2 17:07:28 2009

Hardware path: 8


Basic Memory Description

Module Type: MEMORY
Total Configured Memory : 8192 MB
Page Size: 4096 Bytes

Memory interleaving is supported on this machine and is ON.

Memory Board Inventory

DIMM Slot Size (MB)
--------- ---------
0A 0
0B 0
0C 0
0D 0
1A 1024
1B 1024
1C 1024
1D 1024
2A 1024
2B 1024
2C 1024
2D 1024
3A 0
3B 0
3C 0
3D 0
--------- ---------
System Total (MB): 8192

Memory Error Log Summary

The memory error log is empty.

Page Deallocation Table (PDT)

PDT Entries Used: 0
PDT Entries Free: 3000
PDT Total Size: 3000


regards
TwoProc
Honored Contributor

Re: Physical Memory added to the system but not detected on boot

I've got a feeling that the ram in Bank 0 is the "new ram", and I've got the feeling that this new ram isn't HP brand ram. If not, you're system won't boot, even if the ram is "seen". Or, at least, if the ram is "HP" it isn't the correct "named type" that goes with that machine. If this is the case, even if this ram "works" in this machine - it won't work in Bank 0.

Go back and make sure that the ram in Bank 0 is the actual HP ram type explicitly made for that box.

The reason is, if the machine doesn't "see" the correct type of ram in Bank 0 - it won't boot the machine.

I've seen this in two cases:
a) the ram isn't HP but is Kingston, etc. That ram works, but not in Bank 0- to bring the meachine up you MUST have some HP branded ram that is specifically designated for that machine.

b) the *is HP branded* but isn't the "named type by identifier" designated for that machine. I've seen this when I've used ram for one type of machine and put it in another. Even though the ram is the "same" it's identifier says it's different, so it won't boot the machine with that ram in Bank 0. However, since the "type" of of the ram is correct, but the internal "named type" of the ram is wrong - it works fine in the machine - but not in bank 0.

Of course, if this is a machine that has HP support on it, you don't want to be doing any of these two moves, as it isn't supported, and if you have machine failure(s) you'll be out on your own. But on machines that aren't production, or under support, you can try some riskier things, if you're prepared to deal with the issues that may come up yourself. Naturally, I wouldn't recommend this on Mission critical equipment.
We are the people our parents warned us about --Jimmy Buffett