vgextend io error

[Manix]

check if disk is bad ..
run the command "dd if=/dev/rdsk/c4t2d7 of=/dev/null bs=1024 count=1000"

keep the count high if the command passes.

Hope you are adding the disks running pvcreate.

[Torsten.]

Forget "dd" here, it is an array!

[Torsten.]

First I would check the array health.
If commandview sdm is installed, run

# armdsp -a

and check if it is "ready", without errors and warnings.

[Chad Brindley]

Hi Torsten,

I checked the array with the armdsp command and it reports back as ready and the enclosures + disks report back as Good.

I have ran the vgextend for one of the alternate paths and it seems to be doing the same again with the IO timeout.

The vgextend command works but it times out with an io error once again when trying to run the vgcfgbackup (as below).

vgcfgbackup: IO error on Physical Volume device /dev/rdsk/c4t2d7: I/O error

I can run the pvdisplay and diskinfo to the disk with the command.

pvdisplay -v /dev/dsk/c4t2d7
diskinfo /dev/rdsk/c4t2d7

c4t2d7 looks like the primary path on the other LUN which is presented to this Server and extended to this same Volume group.

And there are no array issues as confirmed above. Strange.

I am not sure on the LVM patch levels but as this worked on a previous vgextend it would be strange if it was that.

Would a reboot of the Server help? Maybe something is locking that file, nothing in syslog.

What is the syntax to run a vgcfgbackup manually?

Regards,

Chad

[Torsten.]

Secure Manager in use?

Try to get the table like this

armsecure â r â f lun_security.txt -p AUTORAID array_alias

where AUTORAID is the password. Adjust password and alias.

[Chad Brindley]

Torsten,

Secure Manager is in use.

I have attached the file, not sure what I am looking at but I assume its LUN number and device world wide name?

Chad

p.s. Learning alot here, really appreciate your time and help on this.

[Torsten.]

Let's pick a line:

NODEWWN 50060b00002fed42 21 WC

This means the server HBA with WWN 50060b00002fed42 is allowed to do WRITE and CONFIGURE on LUN 21.

You need such entry for each server WWN and LUN.





All the DEFAULT lines mean no access for anyone.






So this sets "NO ACCESS by default for all the LUNs", then "overwrites" with "WWN abc is allowed to write to LUN 21", clear enough?

[Chad Brindley]

After looking at the table this looks fine.

I ran an ioscan to find out the HBA device and then an fcmsutil and the LUNS+security is assigned correctly.

[Torsten.]

Well, I can't check this, I don't know your WWN.

IIRC the armtopology command will also help you on this.


The output of "armdsp -a would be nice ...

[Chad Brindley]

Hi Torsten,

Been away for a few days so just coming back to this.

I have attached the armdsp output for you to look through, it looks okay to me but maybe it will help you understand what I have here.

Chad