Logical Disk on SSA 1

[visvid]

I have read through the forum concerning this subject as we have the same problem.

I have tried all the suggestings as per

smitty | chgssadisk


rmdev -dl pdisk19

plus running cfgmgr -vl ssar


this put pdisk19 back in but when i try and add the hdisk19 to it it bomds out with this


0514-519 The following device was not found in the customized
device configuration database:
name = 'hdisk19'


This disk failed and was replaced so it should be a stright forward rmdev / mkdev and extendvg.


I am running out of ideas here


Regards


Simon

 

[bjverzal]

ssaxlate -l pdisk19
rmdev -dl ###### where ###### is the hdisk# the command above tells you.

 

[DebiJo]

By default the Hdisk # and the Pdisk # are typically not the same. The Pdisk #'s only take into account the SSA disks, while the Hdisk #'s begin by numbering the internals. So, be careful what you force your hdisk # to be.

Debi

 

[Guest_imported]

Go to smit, devices, ssa disks. In both SSA logical & Physical disks options, there is a 'logical to physical relationship' option. It show which Hdisk is assigned to which pdisk.

Another command I use displays the external serial number (on the front of the actual drive) of each hdisk drive. I created a batch job to list all the drives.

echo 'HDISK17'
lsattr -El hdisk17 -a connwhere_shad|cut -c20-27

Between both list, it is easier for me to find a problem drive.

 

[bi]

Simon,

You need to use the pdisk in an array or designate the pdisk as a system disk.

Use smit: Devices/SSA RAID Arrays/Change-Show use of an SSA Physical Disk.

If the disk is desginated as an Array Candidate but it isn't part of an array yet, you won't see a corresponding hdisk. You'll need more than one pdisk to create an array. For example, if you have two pdisks and create a RAID1 array, you will get o-n-e hdisk designation.

Or, if you designate the pdisk as a system disk, it will get an hdisk assignment.

 

[visvid]

Many thanks for all the help, looks like changing it from Cabinate Disk to Sys Disk has now giving us the h/p disk assocation.

We then mkdev on h/p disk which was ok, but cannot extendvg as we now get error 0514-047, no pvid

I have chdev -l hdisk$ -a pv=yes

but this has not worked. I will rmdev and reboot to see if this

picks it up, unless i have missed something.

Any advice greatlly appreciated

 

[visvid]

I have done the reboot and run cfgmgr but this has not worked. I have had a look at some other notes on PVID and notice from earlier entries that if the ROS level and ID are different this may be the problem ?

My new disk is id 0070 and the other 7 disks are 0059 , is where my problem lies ? maybe change the disk over again ?


Thanks in advance

 

[visvid]

Finally got this problem resolved yesterday, following the advise from bi, I got the pdisk and hdisk seeing each other , so happy with that, but as mentioned we could not extendvg with this disk.

Had a search around ,and then formatted the new disk , as it had no data... this seems to have done the job,as cfgmgr then saw it gave it a pvid and the rest was then easy.

Once again , thanks for all the help, this is a great web site, I will be using this again


Regards

Simon