vgcreate is hanging while creating volume group.

[Suresh Patoria]

Hi

check the disk using the mediainit command

Thanx

[Yue Du]

i can pvcreate the disk, and it
seems that mediainit is not
recommended to new disks.

Y.

[Janusz Wojnarowicz]

Hi,

My problem is still not fixed. I've even tried to create vg with two disks and it didn't work as well.
J.

[Cheryl Griffin]

What type of disks are you using?

[KapilRaj]

If you have nothing on these disks , follow the steps ... I am suggesting this as your W2003 would have put some stuff into ur disk ...

I would,

cat /stand/vmunix > /dev/rdsk/c?t?d?

do the same for the next disk .... and then try to pvcreate and then vgcreate !..

Try this please ... It does't kill ur disk anyway but will wipe out any data in those disks ....

Regds,

Kaps

[Janusz Wojnarowicz]

I have 3 disks:
HP 146 GST3146807LC.
Now I'vet tried with mediainit. but I got I/O error:
mediainit: initialization process starting
mediainit: locking SCSI device
mediainit: initializing media
mediainit: initialize media command failed - I/O error

And sam shows one disk with Total MB as 0 !!!

[KapilRaj]

Can u try with just one disk at a time and then extend the others ... ?

Also disconnect the one with 0 MB

Kaps

[Janusz Wojnarowicz]

OK, I'll try it ...

[Janusz Wojnarowicz]

well,
I'm getting on 2nd disk:
cat /stand/vmunix > /dev/rdsk/c3t2d0
Invalid argument
cat: Cannot write to output.

[Joseph Dieckhans_1]

Hi,

I was working on a similar issue and was just told that the problem is with the default physical extent size for the volume group. Use the -s option to set the physical extent size larger than the default 4M.

i.e. vgcreate -s 64 /dev/vg01 /dev/dsk/cXtXdX

- Joey D.


----------------------------------------------------------------------------------------------------
11.23 LVM vgcreate can hang when building a volume group
By: Mr. McMahon, HP-UX Kernel GSE

For a volume group to be built successfully, the volume group reserved area (VGRA) must fit inside a single physical extent. If it does not then an error indicating insufficient space should be returned. Under these conditions, with 11.23, a bug results in vgcreate hanging, and it cannot be killed. The kernel stack for vgcreate will probably show the routine
lv_dev_terminate_daemon(k) calling sleep(k).

Where you can affect the parameters used with vgcreate, increasing the extent size or reducing the maximum number of physical extents per PV or the maximum number of PVs are ways to overcome this problem. lvmcompute

[Janusz Wojnarowicz]

Hi Joe,
the symptoms, you're writnig about seem to confirm in my case. But now I have another problem. I tried to initiate disks with medianinit command. After some time it finished with I/O error and now I can see my disks in sam with Total MB: 0! And vgcreate finishes with:
vgcreate: Couldn't open physical volume "/dev/dsk/c2t0d0":
I/O error.

What can I do know? I hope they are not physically damaged ...

[KapilRaj]

Are there any special drivers for these new disks ?

Kaps

[Janusz Wojnarowicz]

Well, I know of nothing. I didn't install anything new to them. I'm getting also I/O Error using dd.

[Cheryl Griffin]

The disks need to be checked out. This looks like a problem with the disks.

[Janusz Wojnarowicz]

Hi Cheryl,
so what do you propode to do ?

[Janusz Wojnarowicz]

While trying diskinfo on my 2 "bad" disks I'm getting:
/usr/sbin/diskinfo /dev/rdsk/c2t0d0
SCSI describe of /dev/rdsk/c2t0d0:
vendor: HP 146 G
product id: ST3146807LC
type: direct access
size: 0 Kbytes
bytes per sector: 0
hw0099 25: /usr/sbin/diskinfo /dev/rdsk/c3t2d0
SCSI describe of /dev/rdsk/c3t2d0:
vendor: HP 146 G
product id: ST3146807LC
type: direct access
size: 0 Kbytes
bytes per sector: 0

and after have tried VERIFY with mtsm I can see in activity log:

Tue May 11 16:08:27 2004: Open system call failed with errno (16) when
attempting to open file (/dev/rdsk/c3t2d0) with read
and write (O_RDWR) option.

Tue May 11 16:08:27 2004: EBUSY (16) errno returned from an open system call
indicates the device is currently busy.

Possible Causes/Recommended Action:

Wait and Restart the verifier.

Tue May 11 16:08:27 2004: Tool completed with exit_status MOD_INCOMPLETE (5)
indicating the tool was started but could not
properly complete execution.