topic Re: SAM problems in Operating System - HP-UX

SAM problems

Josee Bourget-Thuma — Mon, 12 Nov 2001 17:58:01 GMT

Hello!

I'm trying to create a new volume group using SAM. I started SAM fine, and kicked off the create volume group.

I looked in /var/sam/log/samlog and found nothing special. Except for one vgimport -P command which exited with code 1.

The disc I'm trying to create volume on is on a NIKE20 disk array.

I installed patch PHCO_23876 on my 11.00 O/S.
Any clues as to what is going on?

Thank!
Josee...

Re: SAM problems

Bill McNAMARA_1 — Mon, 12 Nov 2001 18:03:54 GMT

watch out for your lun 0.

do a diskinfo /dev/dsk/cXtYd0
after you get the device file for the lun 0 of the nike 20.

You will probably see the lun0 twice. once on tX and tY corresponding to the SPA and SPB.

The nike has a curious note about autotrespass.

You could try it from command line also.. to get a more verbose output.
See: here for more on the nike:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x417edfe5920fd5118fef0090279cd0f9,00.html

Later,
Bill

Re: SAM problems

nancy rippey — Mon, 12 Nov 2001 18:04:58 GMT

Have you tried creating it manually
Try
Creating Volume Group and Logical Volumes

pvcreate /dev/rdsk/cXtXd0 - For each disk

mkdir /dev/vgname
mknod /dev/vgname/group c 64 0x0#0000

vgcreate /dev/vgname /dev/dsk/cXtXd0

To create new logical volumes

lvcreate -n lv## /dev/vgname - Create a zero sized logical volume,

lvextend -l <# 4MB extents> /dev/vgname/lv## /dev/dsk/cXtXd0 - Make lv's size you want

To create and mount a new filesystem (make sure to get blksize from DBA)

mkdir /mntpoint

newfs -F vxfs -b /dev/vgname/lvol_

mount /dev/vgname/lvol_ /mntpoint

Add entry to /etc/fstab

/dev/vgname/lvol_ /mntpoint vxfs rw,suid,delaylog,detainlog 0 2

Re: SAM problems

Roger Baptiste — Mon, 12 Nov 2001 18:14:12 GMT

hi,

To identify the problem, go in the manual route.

ioscan -nkCdisk
and note the disks which you want to be in the new VG

If there are any pvlinks (two pv paths to the same disk), make a note of that too.

pvcreate

mkdir /dev/vgname
mknod /dev/vgname/group c 64 0xx0000

vgcreate /dev/vgname

{options can be pv limit, extent size etc. or you can not specify anything).

See how this works. I suspect the problem is more to
with the recognition of disks.

-raj

Re: SAM problems

Sanjay_6 — Mon, 12 Nov 2001 22:59:01 GMT

Hi Josee,

Try to create the vg manually,

Do a ioscan -fnC disk to check whether the disk is sensed properly with the device as claimed.

ioscan -fnC disk

Now proceed to creating a VG,

pvcreate -f /dev/rdsk/cxtydz
mkdir /dev/vg_name
mknod /dev/vg_name/group c 64 0x0n0000
(n=1,2,3,.... and is unique
do a ll /dev/*/group to check the n is unique)
vgcreate /dev/vg_name /dev/dsk/cxtydz
Do a pvcreate and vgextend for any other disk you want to add to this vg. Now do a lvcreate to create a new lv on this disk,

lvcreate -L lv_size_MB -n lv_name /dev/vg_name

Now create a filesystem on this lv,

newfs -F vxfs -o largefiles /dev/dsk/rlv_name

Hope this helps.

Regds

Re: SAM problems

Josee Bourget-Thuma — Mon, 19 Nov 2001 23:24:08 GMT

Thank you all for your input, although all of your suggestions are very valid, turns out that one of my NIKE arrays is causing problems and not allowing for any administrative changes to any disks. I had to turn it off and work on the system that way.

I haven't not yet isolated the issue due to lack of time but am lucky that the array in not critical for me at this time.

Something for me to play with on rainy days.

Thanks again!
Josee...