Raid 5 Questions

[Jay_167]

Hello Everyone,

I've recently been tasked to configure a DS20 as a raid 5. I'm very new to tru64 but pretty experienced in Solaris and Liunx so bare with me.
Can someone point me in the right direction on accomplishing this. Listed below is my setup.

DS20 running Tru64 V5.1A with internal 1 18.gb drive(OS installed on)

Storageworks 4254R(DS-SSL14-Rm) with 6 36.4GB drives (What I want to raid 5 for /data)

DS-KZPCC-XE LVD Raid Controller.

when I view the diskarray in sysman it shows the entire disk being 138929.500MB Should it show 218GB 36.4 x 6 =218GB

Like I said above basically need helpfull information to get me started.

Thanks

[Johan Brusche]

In a raidset you always lose the equivalent of 1 drive for storing parity data, so
that should give you 5x 36,4=182GB.
The 139 GB you see is less than 4 drives, unless maybe a spare drive for auto-replacement is defined.

Didn't you get a StorageWorks Array SWCCAgent kit with the KZPCC ?

Did you run the config utility from console mode ?
>>> run bios pza0

Rgds,
__ Johan.

[Jay_167]

Hey Johan,

Thanks for the reply. This system has been laying around the lab for about 2-3 years now, I'm not the original admin for this box so the person who initially set the system up threw all the media around the building so I guess I have to track down the SWCCAgent. Is there a way to see if the agent is installed??

When you say console mode do u mean the boot prom?? If so i haven't run that command
As far as finding out why I only see 139GB will this utility help me track this down?? Any other info would be great

Thanks
Jay

[Matthew Pearce]

to see if agent is installed you could try
# setld -i | grep -i swc
then
# setld -i
to view the file locations.

But you need to install additional software installed on a Win platform that can talk to the tru64 server, to be able to use it while online.

To configure it offline you need to #shutdown -h now
Then run the SMOR utility from the >>> boot prompt.

This link might help:
http://h18006.www1.hp.com/alphaserver/products/storage/kzpcc_ac.html

Q6: Is there a command line interface for KZPCC (like the RCU for KZPAC)?
A6: No. We have Alpha SMOR (via the console) for an off-line configuration utility and the SWCC for an on-line configuration utility.

Was a while ago, so that's about all I remember.

[Jay_167]

Ok I found the storageworks media, managed to get everything installed on the server and the remote pc. But for some reason I can't connect to the server. Here is the output of user.log:

KZPCCAgent has shutdown
KZPCCAgent V2.3.0.042 is starting
Attempting to start the process that sends Tc

Searching for supported controllers.
Subsystem i2o0_cp : Supported controller foun

Found 1 supported controller(s).
KZPCCAgent Applet Manager Responder has Start


From the client end. Trying to connect via KZPCC client:

Unable to connect, call to gethostbyaddr failed: vaild name, no data record or requested type.


The KZPCC client failed to connect to system .WSAECONNREFUSED: connection refused


Then I get progam memory errors. On the client I'm using a diff verion of SW to connect to client. Does somebody have the most recent version too see if that make a difference.

Thanks

[Jay_167]

I manged to configure the raid 5 via smor untility and mounted a advfs on it. Now I'm trying to play with the DLT-Tape(DS-BA356-RC) system thats also connected to the DS-KZPCC. I don't think I see it in hwgmgr but i'm not sure. What should I be looking for?? Any help please.

Thanks,

Jay

[Matthew Pearce]

Try shutting down the system again and ensure you can see the tape drive by doing >>> show dev
If it doesn't show there, it won't show in your OS hwmgr database and you may need to verify that this device is supported on the KZPCC.

[Johan Brusche]

J.

Only 9.1 to 72 GB DISK drives
(Ultra2 speed 10k rpm) are supported, no tapedrives in the table.

__ Johan.

[Jay_167]

I think i'm seeing the tape drive?? But don't know what to do now. Any Ideas??


bash-2.05b# hwmgr -show scsi

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
63: 1 marley disk none 2 3 dsk1 [4/0/0]
64: 2 marley cdrom none 0 1 cdrom0 [2/0/0]
65: 0 marley tape none 0 1 (null)
67: 3 marley disk none 0 1 (null)
68: 4 marley disk none 0 1 (null)
69: 5 marley disk none 0 1 (null)
70: 6 marley disk none 0 1 (null)
71: 7 marley disk none 0 1 (null)
72: 8 marley disk none 0 1 (null)
74: 9 marley cdrom none 0 1 (null)

[Johan Brusche]

The tape, you see there, is one that has been removed in the past, it has no valid path nor any special device files associated.

The command "hwmgr sho scsi -full -id 65"
will show you the details.

__ Johan.

[Jay_167]

Here is the output to the command u posted.

bash-2.05b# hwmgr sho scsi -full -id 65

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
65: 0 marley tape none 0 1 (null)

WWID:04100022:"DEC TZ89 (C) DECPXA33S4179"


BUS TARGET LUN PATH STATE
---------------------------------
0 4 0 stale

[Johan Brusche]

As I said, at one time in the past a TZ89 was connected to scsi-bus #0 with target-id #4, but it is not there now. There were also several disks on that bus. So there probably is/was another type of PCI-scsi adapter in this DS20 than the KZPCC.

Can you post a "hwmgr view hierarchy" ?

Johan.

[Jay_167]

Here it is.

bash-2.05b# hwmgr view hierarchy
HWID: hardware hierarchy
-------------------------------------------------------------------------------
1: platform COMPAQ AlphaServer DS20E 617 MHz
2: cpu CPU0
18: bus pci0
19: connection pci0slot5
33: bus isa0
34: connection isa0slot0
35: keyboard keyboard0
36: pointer mouse0
37: connection isa0slot2
38: serial_port tty00
39: connection isa0slot3
40: serial_port tty01
41: connection isa0slot4
42: parallel_port lp0
43: connection isa0slot5
44: fdi_controller fdi0
45: disk fdi0-unit-0 floppy0
46: ide_adapter ata0
47: scsi_bus scsi2
64: disk bus-2-targ-0-lun-0 cdrom0
48: ide_adapter ata1
49: scsi_bus scsi3
50: bus usb0
24: connection pci0slot6
51: scsi_adapter aha_chim0
52: scsi_bus scsi4
63: disk bus-4-targ-0-lun-0 dsk1
53: scsi_adapter aha_chim2
54: scsi_bus scsi5
27: connection pci0slot7
73: network alt1
29: connection pci0slot8
66: graphics_controller per0
31: connection pci0slot9
56: bus pci2
57: connection pci2slot3
58: unconfigured_hardware Unconfigured-device-()-at-pci2slot3
59: connection pci2slot4
61: i2o_controller i2o0
62: disk iop-0-dev-0 dsk0
80: control_port i2o0_cp scp0

[Johan Brusche]

Above data shows the KZPCC as I2O0 controller and the raidset as iop-0-dev-0 dsk0, plus the CD-drive connected to SCSI-bus #2.

On top of that there are 3 additional SCSI buses #3, #4 and #5, probably there are 2 dual channel PCI-SCSI adapters. However we do not see SCSI-bus #0 and #1, but this can be normal if one of these 2 SCSI-cards was formerly located in another PCI-slot. So you have plenty of possibilities to connect the DS-BA356-RC shelf with DLT to one of those 4 SCSI-buses.

__ Johan.

[Jay_167]

The only card i have in the box is a KZPCC.

[Michael Schulte zur Sur]

Jay,

I once accidentily connected a dlt 40/80 to a kzpcc with the result that a couple of disks went to failure status. I wouldn't do that.

greetings,

Michael

[Jay_167]

Thanks for the heads up. I will see if i have a extra scsi card around.

[Johan Brusche]

If you only have the KZPCC with dsk0, where is dsk1 connected to then ??

hwmgr show scsi -id 63 -full

__ Johan.

[Jay_167]

Disk1 is connected to onboard scsi.

[Johan Brusche]

The motherboard has 2 integerated SCSI ports, and hwmgr tells us you have to more.

Are you sure none of these SCSI ports are connected to one of the 5(or6) SCSI knock-out
connector holes in the back-panel of the system ?

__ Johan.

[Sid Shorter_2]

If you don't have to have harward RAID, use LSM and create RAID5 volume that way.