cmgetconf disk error 11.16

[likid0]

Hy,

when i run cmgetconf, to get my latest config, i get this disk error, when i look in cen6 at these disks, they are DISK-SUBSYSTEM, never seen this before, any idea what can I do, to get rid of the errors?

cen6:/dev/rdsk# ioscan -fnkH 1/0/14/0/0.117.90.19.0.1.0
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 111 1/0/14/0/0.117.90.19.0.1.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0


Error: Unable to determine a unique identifier for physical volume /dev/dsk/c1t1 d0 on node cen6. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c26t 0d1 on node cen6. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c8t1 d0 on node cen6. Use pvcreate to give the disk an identifier.

[Steven E. Protter]

Shalom,

Before a disk can be used in HP-UX it must have pvcreate run on it.

Use pvcreate to give the disk an identifier

My G-d! A meaningful Unix error message.

SEP

[likid0]

I have never pvcreated on a HPDISK-SUBSYSTEM, is not even a disk ...

have you ?

but i solved it anyway, it had nothing to do with what the error that.

Using cmcheckonf gave and error on a vg with a cluster mismatch ID, solving that, got rid of the other messages

[skt_skt]

are you sure that is not a disk?

the clusterid mismatch is for th VG( or the disks belong to the that VG)

those CTDs reported do not belong to VG?

[Steven E. Protter · Accepted solution]

Shalom again,

HP DISK-SUBSYSTEM

Its just a label read off the firmware of the disk or disk array. Its not significant.

pvcreate the disk then you can add them to a volume group and use it.

Now sometimes the disk array itself shows up as LUN0. This is not a real disk and can not be used in any way. Assigning a LUN to LUN0 on the disk array avoids this problem.


SEP

[likid0]

I understand what you say steven, but all the disks i have on those boxes are pvcreated and in working vgs.Thats the strange part. I couldn't understand why it was asking to pvcreate and HP DISK-SUBSYSTEM, all the disks that hang from it:

1/0/14/0/0.117.90.19.0.1.1
1/0/14/0/0.117.90.19.0.1.2
1/0/14/0/0.117.90.19.0.1.3
1/0/14/0/0.117.90.19.0.1.4

are in vgs.And not in the same VG with the cluster mismatch.

But anyway the problem has gone.

Thnx for your time and help

[likid0]

w0rking