Adding new disk

[Betty Hardin]

We recently had an outside consultant come in and install two new 18GB drives into our HP9000 (HPUX 11.0). This is what he did:

1. Inserted the drives into an empty slot in the FC60 Array
2. insf -e
3. ioscan -fnC dsk

He told me that the new drives are c5t0d5 & c5t0d6 and that I 'simply' need to add them to a volume group and then mirror the drives.

This is what I had intended to do:
pvcreate /dev/rdsk/c5t0d5
vgextend /dev/vg01 /dev/dsk/c5t0d5
strings /etc/lvmtab
vgdisplay -v /dev/vg01

(Not sure this is the correct procedure; I have previously worked with AIX - Not HPUX)

The problem:
pvcreate tells me these drives are already a part of an existing volume group (vg06 & vg07). Looking at lvmconf contents before/after the drive installation does not show any changes (file sizes and mapfiles are the same)

SAM does not show these 'new' drives

ioscan shows all drives in the system are claimed.

What am I missing? How can I see these drives? Do I have the procedure right? I have read/re-read the manual on "how to add a drive to an existing volume group'.

Can I physically pull those drives, reissue the IOSCAN command and get an accurate listing of drives in the system? And then - reinsert those drives, rerun the IOSCAN and see what's there?

Is there a command that needs to be issued to 'remove' those drives - assuming they are really there?

TIA
Betty Hardin
Trendway Corporation

[Naveej.K.A]

hi,

What i feel is that consultant has given you the wrong disk address.

u need to compare the output of /etc/lvmtab and the ioscan output to come to a conclusion that which hard disk had been added and what is the address of the hard disk which has been added.

with best wishes
Naveej

[Victor Fridyev]

Hi,

First of all, the order of commands is wrong, it should be like this:
0. ioscan -kfnCdisk |tee /tmp/oldstuff
1. Insert the drives into an empty slot in the FC60 Array
2. ioscan -fnC disk
3. insf -e -C disk
4. ioscan -kfnCdisk >/tmp/newstuff

Compare the outputs. If you see new entries, the disk might be added to existing volume groups.
If new entries don't exist, look at the
strings /etc/lvmtab output abd find which disks are not included into volume groups, extract the new disks, repeat
ioscan -fnCdisk and look for NO_HW devices. The entries should be the same as in lvmtab test. Insert the disks, repeat ioscan and include the disks into volume group.
PS. If you don't see new entries, extract and insert new disks and repeat the procedure.
HTH

[shan_7]

Hi,

see if you are add those harddisks and adding into new vgxx. follow this commands.

after connecting the HDDs
#ioscan -fnC disk

then

#pvcreate -f /dev/rdsk/cxtxdx

cerate dirs under root
#mkdir /dev/vgxx

create group file for that
#mknod /dev/vgxx/group c 64 0xXX0000

XX- vgno

then
#vgcreate /dev/vgxx /dev/dsk/cxtxdx
#lvcreate -L xxxx /dev/vgxx
#newfs -F vxfs /dev/vgxx/rlovlx

before mounting
#mkdir mountdir
#mount /dev/vgxx/lvolx /mountdir

this will help you

with cheers
Shankar

[Mohanasundaram_1 · Accepted solution]

Hi,

Do not perform a pvcreate -f, as suggested by shankar, until you know for sure that the device file is not used for other VG.

You can perform a diskinfo -v on the device file to ascertain the size of the LUN and compare it with what the consultant had given you.

If the disks you added newly were used in some other system, then too you might get this message. In that case, you can go ahead and do pvcreate -f. But you better be 200% sure on this.

My approach would be,

1)check strings /etc/lvmtab and ensure your device files are not already in there.

2) Import the disks into a new volume group, if you did not find these devices in lvmtab.

3) Try mounting the filesystems and check if you have any data relevant to your application.

By this way you are sure that you are not trampling on your existing data.

Another way is, Just pullout the 2 newly added disks and check through diskinfo and ioscan. If the ioscan shows NO_HW and diskinfo gives error then you know that the device file belongs to the disks you added or not.

Also, give me some time to confirm if FC60 supports standalone disks or not.

Cheers,
Mohan.

[Betty Hardin]

The disks in question DO belong to another VG. I prefer to not use the -f option of pvcreate. I was in there this afternoon - ran IOSCAN with drives in place, pulled the drives, ran ioscan again, shutdown, rebooted ... the results of ioscan are the same before and after .. and lvmtab shows 7 vg's with two drives in each. So far, I haven't found anything that says NO_HW. When I pull the drives & reinsert them, the lights flash green and go out - indicating to me that at least the system sees them in the slot.

I have until 9pm on Sunday to work on this; and then the box has to go into production mode for another week.

I appreciate all of your thoughts on this - thanks - and keep them coming please.

B

[Mohanasundaram_1]

Hi Betty,

Looks like your consultant has not done enough to make your disk usable. I checked for RAID 0. It is supported in FC60 but not recommended. Hope you are aware of this.

To identify a disk in FC60, there are few things involved like slot number, channel number, enclosure number. I do have a manual to help you and I can forward to you directly if you want. Let me know your ID in that case.

Primarily, you need to identify the disks with their slot,channel,enclosure numbers and then bind it to a LUN. Once the binding is done, you can access the LUNs. I am afraid just plugging-in the disk will not help.

Another option is - make your consultant do this for you again. The manual may take some time for you to understand and it may not be possible this Sunday.

Cheers,
Mohan.

[Ashwani Kashyap]

The newly inserted disks in the FC60 array should be bound to a lun or a new LUN created on them and bound to one of the FC60 processor before SAM or ioscan can see them .

The only wat to see them now is to use the FC60 array utilities either through SAM or command line utilites , i think amdsp or armdsp . They can be founf in /opt/hparray .

any way your consultant did not do a good job . As said earlier unless the disk are bounf to a lun and attached to a processor on the FC60 , hpuc cannot even create device file for those . So the device iles you are looking at might be wrong .

What you can do is use sam to go into one of the controllers if the FC60 array and it will show you the diagramatical representation of the array . pick the slots where the new disks haveb been installed and create a new lun there . Then do an ioscan and insf -e and you should see the new device files which can be added into a vg .

[Betty Hardin]

Yes, Mohan -

Please send me the manual that you are referring to. Not sure what you mean by my ID. My personal email address is betty@bigbluewater.com.

Thank you
Betty

[Ashwani Kashyap]

Find all FC60 Manual here :
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=12169&prodSeriesId=33734

[Betty Hardin]

Good info. Have identified my drives (all of my drives including those that are missing). Now; how can I match the physical drive to a volume group or device?

For example; I'd like to equate the serial number of each disk to the device (ie. /dev/dsk/c5t0d5 = 3BV186XE) - or something like that.

Is it possible?

TIA
B

[Todd McDaniel_1]

not sure why you would need the serial number... related to the device name?

Easy way to tell when new devices are added ...

do a:

ls -lrt /dev/dsk/*


This will list in reverse order your disks of most recent creation last.

All you need now is to add them since you have found the correct new disks.

[Todd McDaniel_1]

Here is an easy script I have that lists used disks by VG...


you need a control file with all your VG names in it... vgnamesEMC.out


for name in `cat /root/vgnamesEMC.out `
do
echo $name
vgdisplay -v $name |grep "PV Name" |awk '{ print $3 }'
done > /root/disks.by.VG.`date +%m%d%y` 2> /root/vgerr.`date +%m%d%y`
~

[Sridhar Bhaskarla]

Hi,

This simple script should print out a map of VGs and their corresponding disks.

for VG in $(vgdisplay -v |awk '/VG Name/ {print $3}')
do
printf "$VG -"
vgdisplay -v $VG |awk '/PV Name/ {printf "%s ", $3 }'
echo
done

The disks that are not shown in the above output would be unused. But make sure you don't have any VGs that are in deactivated stage as vgdisplay doesn't show information about them. You will have to depend on 'strings /etc/lvmtab' to get that information.

-Sri