VparError:Granule size in NVRAM (0 0) does not match database(128 128)
Hi,
This is a very common error with the granule size sincronization between the vpdb database and the server NVRAM, this afects servers with vpars versions 4.x and 5.x.
PROB:
when booting we get the following error:
Loading System Directory (boot.sys) to MFS
......Launching /stand/vpmon
SIZE: Text:1563K + Data:53305K + BSS:10763K = Total:65633K
Console is on virtual console - via PCDP
Granule size in NVRAM (0 0) does not match database(128 128). Rebooting system.
SOLUTION:
boot to npars
#vparenv -g ILM:128 -g CLM:128
#vaprenv -m vpars
#shutdown -ry 0
INFO:
Granule:
a. Smallest chunk of memory assignable to individual vPars
b. Granule size is defined at database (/stand/vpdb) creation time
Error:Granule size in NVRAM (0 0) does not match database(128 128). Rebooting system.
Run the below command to check the granule info on the server
# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
The ILM and CLM granule size information specified by the system administrator is stored in the vParsdatabase when it is created. For A.04.xx and A.05.xx vPars releases, the default size is 128 MB for both ILM and CLM. On HP Integrity servers, the firmware also divides the memory into memory objects based on the granule size. Hence, to inform firmware, in addition to the vPars database, thegranule size information is also stored in non-volatile RAM (NVRAM). The following provides detailson how to configure granule size in the A.04.xx and A.05.xx vPars releases. As mentioned earlier, this configuration is not required in the A.01.xx, A.02.xx and A.03.xx vPars releases as the granulesize is fixed at 64 MB.
See the manual below for more info:
http://www.docs.hp.com/en/9832/vParsMemMigration.pdf