create new vg00 with other manufactory disk

[lb_z]

"ioerror on physical volume device /dev/rdsk/c0t1d0:ioerror" when i do "vgcreate vg02 dev/dsk/c0t1d0 ",what's the problem ,how can i do?

THANS

[Stefan Farrelly]

pvcreate -f it first;

pvcreate -f /dev/rdsk/c0t1d0

[V. V. Ravi Kumar_1]

hi,

have u run pvcreate
pvcreate -f

regds

[lb_z]

yes ,i have done it and sucessfully firstly,but the same error appear when doing "vgcfgbackup /dev/vg02"
is it the disk itself?

[Sanjay_6]

Hi,

First do a pvcreate and then run vgcreate,

pvcreate -f /dev/rdsk/c0t1d0

If this is a new VG, first create the vg control file,

mkdir /dev/vg02
mknod /dev/vg02/group c 64 0x020000
vgcreate /dev/vg02 /dev/dsk/c0t1d0

If this is an existing vg, do a vgextend,

vgextend /dev/vg02 /dev/dsk/c0t1d0

Hope this helps.

Regds

[Stefan Farrelly]

It certainly sounds like something may be wrong with this disk. Pvcreate and vgcreate only access the first few blocks so may not detect any errors until you try other commands.

Lets do a read test on the entire disk to test its readable;

dd if=/dev/rdsk/c0t1d0 of=/dev/null bs=1024k

Let that run, and either it will return with xxx blocks in+out or it will return an I/O error indicating there is a problem with the disk.

[Stefan Farrelly]

Are you sure the group file you created for this vg is unique ?

cd /dev
ll v*/group

And check that all group files shown are unique.

[James R. Ferguson]

Hi:

In addition to using 'dd' as suggested, it would be useful to see what (if anything) 'diskinfo' returns:

# diskinfo -v /dev/rdsk/c0t1d0

Can 'diskinfo' access the disk? Do you get a non-zero size returned? Does the command take more than a couple of seconds to respond, or does it hang?

Regards!

...JRF...

[lb_z]

the problem have been solved ,it is the hardware error,now i repalce it with new on,anything is ok!
thanks anyone

[Stefan Farrelly]

Dont forget to assign points to those who took the time to help you.