Operating System - HP-UX
1748169 Members
4193 Online
108758 Solutions
New Discussion юеВ

Re: Pvcreate > Unable to query the I/O interface: System call error

 
Roger Lavender
Frequent Advisor

Pvcreate > Unable to query the I/O interface: System call error


System: ia64 hp server rp3600
HPUX: B.11.31.1009

Brand New Server

Executed this script to mirror root vg00 (/dev/rdsk/c2t7d0) from SMH:

/usr/sbin/idisk -q -w -f /var/sam/fsweb.idf /dev/rdsk/c2t6d0 &&
/usr/sbin/insf -e -v -H 0/4/1/0.0.0.6.0 &&
/usr/sbin/pvcreate /dev/rdsk/c2t6d0s2 &&
/usr/sbin/vgextend -A y -x y /dev/vg00 /dev/dsk/c2t6d0s2 &&
/usr/sbin/mkboot -e -l /dev/rdsk/c2t6d0 &&
/usr/sbin/mkboot -a "hpux" /dev/rdsk/c2t6d0 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol1 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol2 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol3 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol4 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol5 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol6 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol7 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvextend -s -m 1 /dev/vg00/lvol8 /dev/dsk/c2t6d0s2 &&
/usr/sbin/lvlnboot -R /dev/vg00 &&
boot -a 0/4/1/0.0.0.6.0 &&
/usr/bin/cp -p /stand/bootconf /stand/bootconf.fsweb.old &&
/usr/bin/echo "l /dev/dsk/c2t6d0s2" >> /stand/bootconf

RESULTS:

# pg /var/sam/fsweb:idf
3
EFI 500MB
HPUX 100%
HPSP 400MB

line_1 executes correctly, verified:

diskinfo -b /dev/rdsk/c2t6d0s1 | awk '{print $1 / (1024)}' = 499.969
diskinfo -b /dev/rdsk/c2t6d0s2 | awk '{print $1 / (1024)}' = 139115
diskinfo -b /dev/rdsk/c2t6d0s3 | awk '{print $1 / (1024)}' = 399.375

# cd /dev/dsk
# ll
total 0
brw-r----- 1 bin sys 31 0x020000 Oct 5 06:45 c2t0d0
brw-r----- 1 bin sys 31 0x021000 Oct 5 06:45 c2t1d0
brw-r----- 1 bin sys 31 0x022000 Oct 5 06:45 c2t2d0
brw-r----- 1 bin sys 31 0x023000 Oct 5 06:45 c2t3d0
brw-r----- 1 bin sys 31 0x024000 Oct 5 06:45 c2t4d0
brw-r----- 1 bin sys 31 0x025000 Oct 5 06:45 c2t5d0
brw-r----- 1 bin sys 31 0x026000 Oct 5 06:45 c2t6d0
brw-r----- 1 bin sys 31 0x026001 Dec 2 08:24 c2t6d0s1
brw-r----- 1 bin sys 31 0x026002 Dec 2 08:24 c2t6d0s2
brw-r----- 1 bin sys 31 0x026003 Dec 2 08:24 c2t6d0s3
brw-r----- 1 bin sys 31 0x027000 Oct 5 06:45 c2t7d0
brw-r----- 1 bin sys 31 0x027001 Oct 5 06:45 c2t7d0s1
brw-r----- 1 bin sys 31 0x027002 Oct 5 06:45 c2t7d0s2
brw-r----- 1 bin sys 31 0x027003 Oct 5 06:45 c2t7d0s3
brw-r----- 1 bin sys 31 0x030000 Oct 5 06:45 c3t0d0

# cd /dev/rdsk
# ll
total 0
crw-r----- 1 bin sys 188 0x020000 Oct 5 06:45 c2t0d0
crw-r----- 1 bin sys 188 0x021000 Oct 5 06:45 c2t1d0
crw-r----- 1 bin sys 188 0x022000 Oct 5 06:45 c2t2d0
crw-r----- 1 bin sys 188 0x023000 Oct 5 06:45 c2t3d0
crw-r----- 1 bin sys 188 0x024000 Oct 5 06:45 c2t4d0
crw-r----- 1 bin sys 188 0x025000 Oct 5 06:45 c2t5d0
crw-r----- 1 bin sys 188 0x026000 Dec 2 08:30 c2t6d0
crw-r----- 1 bin sys 188 0x026001 Dec 2 08:30 c2t6d0s1
crw-r----- 1 bin sys 188 0x026002 Dec 2 08:30 c2t6d0s2
crw-r----- 1 bin sys 188 0x026003 Dec 2 08:24 c2t6d0s3
crw-r----- 1 bin sys 188 0x027000 Oct 5 06:45 c2t7d0
crw-r----- 1 bin sys 188 0x027001 Oct 5 06:45 c2t7d0s1
crw-r----- 1 bin sys 188 0x027002 Oct 5 06:45 c2t7d0s2
crw-r----- 1 bin sys 188 0x027003 Oct 5 06:45 c2t7d0s3
crw-r----- 1 bin sys 188 0x030000 Oct 5 06:45 c3t0d0

line_2 executes

line_3 fails execution, error reported:

pvcreate: Unable to query the I/O interface: System call error.

Script aborts.

Execute the same script from command line. Same error.

Execute the pvcreate with -fB - same error.

Looked everywhere (including searching forums) - nada? Any ideas?
9 REPLIES 9
Torsten.
Acclaimed Contributor

Re: Pvcreate > Unable to query the I/O interface: System call error

The message looks a bit strange, but pvcreate needs "-B", otherwise it will not be bootable.

If the disk contains a filesystem, you need to use "-f" too.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Roger Lavender
Frequent Advisor

Re: Pvcreate > Unable to query the I/O interface: System call error

Yep, did that (see OP). Executed:

pvcreate -fB /dev//dev/rdsk/c2t6d0s2

Same error.
Torsten.
Acclaimed Contributor

Re: Pvcreate > Unable to query the I/O interface: System call error

>> pvcreate -fB /dev//dev/rdsk/c2t6d0s2


With this double slash?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Roger Lavender
Frequent Advisor

Re: Pvcreate > Unable to query the I/O interface: System call error

Nope, sorry cut&paste error on my part. Command issued was in-fact "pvcreate -fB /dev/rdsk/c2t6d0s2".

Reissued to verify:

# pvcreate -fB /dev/rdsk/c2t6d0s2
pvcreate: Unable to query the I/O interface: System call error.
#
Torsten.
Acclaimed Contributor

Re: Pvcreate > Unable to query the I/O interface: System call error

Did you wrote this script?


I think there is a line missing:

efi_fsinit -d /dev/rdsk/...s1

You also did not set the AUTO file.

You should also use "setboot" to add the alternate disk to the boot menu.

(adjust this line:
boot -a 0/4/1/0.0.0.6.0 && )





BTW, I prefer to use the hardware mirror (Integrated RAID) on this type of server - this makes your life much easier.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Roger Lavender
Frequent Advisor

Re: Pvcreate > Unable to query the I/O interface: System call error

Well, the original script was generated by SHM, but, I verified it - line by line - before executing it. I also copied the SMH script off to a 'mirror_root.sh' file before executing it so that I could verify the commands as they executed with pause/coninue statements. In both cases, the pvcreate error is issued - even as a single cmd line statemenet as noted above.

The 'boot' command is in the script - 3rd line from bottom.

You are correct, the "efi_fsinst" command is not there, but rightly, shouldn't this command after the mkboot commands? Is this required prior to the pvcreate? As this cmd operates on 's1' and not 's2', I don't see/know how this would have an effect on the pvcreate cmd for the 's2' partition. I will factor this cmd into the next iteration of the script.

Maybe there is an issue between legacy and agile (persistent) addressing that is creating this error? I could have issued the following cmd:

pvcreate -fB /dev/rdisk/disk14_p2

I didn't because the original script began using legacy addressing and uses it throughout. As noted, "...you should mix these to addressing schemes".

I don't know at this point. Lvmtab was not updated prior to the point where the error occurs. I'm thinking I could delete the /dev/rdsk entries at this point and restart the process manually using agile (persistent) addressing - see where that gets me.

Shooting in the dark at this point, as I don't know what the pvcreate "...IO interface. System call error." is, or where to look and find out more info.

Torsten.
Acclaimed Contributor

Re: Pvcreate > Unable to query the I/O interface: System call error

This was what I noticed in your script, but it has no relation to this error.
No idea - but maybe there is a special "hidden" character in this line of the script???




Beside this problem I would still recommend to use the hardware RAID.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Roger Lavender
Frequent Advisor

Re: Pvcreate > Unable to query the I/O interface: System call error

Last night I re-read everything I could find within HPUX 11iV3 concerning MirrorUX and the new Mass Storage Stack in order to find a solution to this pvcreate error. I was sure the problem was related to the differences between legacy and agile (persistent) addressing.

This morning, I came in and undid all the commands from the first two lines of the script (noted above in the OP) and verified everything was clean. I then re-executed the commands using the new agile (persistent) addressing only.

The attached file includes all the steps (both creation and verification) that I used to SUCCESSFULLY create a mirror of the root disk device.

Apparently, under the new ia64 OS (B.11.31.1009), the pvcreate command will only execute correctly on the agile (persistent) disk devices by default. This is the only explaination I have at this point.

Needless to say, at this point, I have a successfully mirrored root disk which I have verified.

Unless someone else has an explaination or adds additional comments, I will close this post on Dec 7, 2010.
Roger Lavender
Frequent Advisor

Re: Pvcreate > Unable to query the I/O interface: System call error

A little reading on the Mass Storage Stack would have resolved this problem. New installations of HPUX 11i V3 place both Legacy and Persistent DSFs on the server. However, Persistent DSFs are used by default - not the Legacy DSFs. When I issued the commands above, the first two lines acted on the Legacy DSFs, and the third line acted on the Persistent DSF - by default. As the frirst two lines did not act on the Persistent DSFs, when the pvcreate ran, it could not perform becase the prepatory commands did not act on the persistent DSFs.

Lesson learned.