Adding KZPCC to ES40 with Digital Unix 4.0G

[Ali Diab]

Dear All,

we are in a phase of adding new storage to our server ES40. We installed KZPCC with 2 HDDs 146G, the Two HDD configured as RAID 1, and can be shown on the P00>>show dev as dza516 (BSA).
But when booting the OS, it is not detected by the OS.

Please advice.
Note: attached is the boot log file

[Rob Leadbeater]

Hi,

Take a look through the following page:

http://h18002.www1.hp.com/alphaserver/options/ases40/ases40_ds-kzpcc-ce.html

Looking at your boot log, you need to upgrade your firmware to at least 5.8. You're currently on 5.7. You also need to be on at least patck kit 3.

Hope this helps,

Regards,

Rob

[Pieter 't Hart]

the OS did see the KZPCC :
>>>
Jul 24 13:51:28 es40 vmunix: xcr0 at pci1 slot 5
Jul 24 13:51:28 es40 vmunix: re0 at xcr0 unit 0 (unit status = ONLINE, raid level = 5)
Jul 24 13:51:28 es40 vmunix: (WRITE BACK cache operation SUPPORTED if battery backup enabled)
Jul 24 13:51:28 es40 vmunix: re1 at xcr0 unit 1 (unit status = ONLINE, raid level = 5)
Jul 24 13:51:28 es40 vmunix: (WRITE BACK cache operation SUPPORTED if battery backup enabled)
<<<

did you run MAKEDEV to create the device special files?

[Ali Diab]

Dear Rob

Thanks for you reply, but we have two problems:

1- â ¦v4.0G:
â  Patch Kit: T64V40GAS0003-20010613.tar required. See most up-to-date patch information.

How can we get this patch?

2- For any new hardware added to True 64 Unix, a kernel rebuild must be done to detect the new Hardware and install its drivers, what we know till now that we have to boot to genvmunix and do the kernel rebuild there, but we still need detailed steps how to do that without affecting the existing configuration especially there is an Oracle Database installed on this server.

Please advice

[Ali Diab]

Dear Pieter,

the OS see an existing RAID controller, and not the new one, the new one must shown as:

i2o0 at slot 4 (since we install it on slot 4)

I think the Kernal rebuild will solve our issue, so please help us in that.

Thanks

[Pieter 't Hart · Accepted solution]

Hi Ali,
sorry for the mistake.

procedure would be

boot general unix kernel
>>> boot -fi genvmunix
use sizer to detect hardware and create a new configfile
unix# sizer -v > /tmp/newsystem.conf

- compare this file with the current configfile in /sys/conf
diff /tmp/newsystem.conf /sys/conf/
- some line (probably "config_driver itpsa") will differ
- add this line to the /sys/conf/
and do a "doconfig -c"
- make a backup of your old vmunix "cp /vmunix /vmunix.old"
- and copy the new vmunix to the root of the filesystem "cp /usr/sys//vmunix /vmunix"
- reboot to the new kernel

[Ali Diab]

Thanks Pieter this solve the problem, but with sizer -n (instead of -v) :-)

[Ali Diab]

Solved by Pieter
Thanks again Pieter

[Pieter 't Hart]

sorry for typo.
thanks for feedback and points
Regards,
Pieter