topic Re: Error on ignite in Operating System - HP-UX

Error on ignite

Paul Thomson_2 — Fri, 04 Oct 2002 11:41:30 GMT

When running an ignite I get the following errors
Started - Fri Oct 4 14:44:36 2002
********
/opt/ignite/bin/make_recovery -v -A -d /dev/rmt/0m
/usr/sbin/vgdisplay -v "vg00"
/usr/sbin/vgdisplay -v "vg00"
/usr/sbin/vgdisplay -v
"/opt/ignite/bin/save_config" -f "/var/opt/ignite/recovery/config.recover" "vg00
" >> "/var/opt/ignite/logs/makrec.log1" 2>&1
lvlnboot: Warning: Can not determine all Physical Volumes on which mirrored cop
ies of
the Logical Volume are located. "/etc/lvmtab" is missing Physical Volumes.
Unable to query the I/O interface: Parameter error.
lvlnboot: Unable to print reliable information.
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk

********
Ended Unsuccessfully - Fri Oct 4 14:45:04 2002
********

Can anyone advise ??

Re: Error on ignite

Pete Randall — Fri, 04 Oct 2002 11:47:48 GMT

Perhaps your lvmtab is out of sync? Try a vgscan?

Pete

Re: Error on ignite

harry d brown jr — Fri, 04 Oct 2002 11:48:22 GMT

Looks like you need to rebuild the /etc/lvmtab file:

mv /etc/lvmtab /etc/lvmtab.orig
vgscan -a

then try the backup again. BUT, before you start, you should UPGRADE ignite to the latest version:

http://www.software.hp.com/products/IUX/download.html

and start using make_tape_recovery.

After doing a make_tape_recovery, it's also advisble to update your patches.

live free or die
harry

Re: Error on ignite

Cheryl Griffin — Fri, 04 Oct 2002 12:03:37 GMT

There may also be a problem with vg00:
# vgdisplay -v /dev/vg00 |more
# lvlnboot -v
# strings /etc/lvmtab

Look for things like the command(s) error, or the Cur PV and Act PV not being equal in vgdisplay or the list of physical disks does not match what /etc/lvmtab shows.

Check /var/adm/syslog/syslog.log and dmesg for disk related errors.

Cheryl

Re: Error on ignite

steven Burgess_2 — Fri, 04 Oct 2002 12:08:22 GMT

Tommo

Have a look at this doc

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062921960

HTH

Steve

Re: Error on ignite

Clemens van Everdingen — Fri, 04 Oct 2002 12:08:28 GMT

Hi,

lvlnboot -v is giving this error as we can read above.

So follow cheryl's approach to troubleshoot before doing vgscan etc...

Show us the output from vgdisplay and strings lvmtab.

C.

Re: Error on ignite

Paul Thomson_2 — Fri, 04 Oct 2002 14:37:55 GMT

In syslog there are entries such as

Oct 4 14:43:18 gb360_w vmunix: SCSI: Attempt to access partially open device --
dev: bc001000
Oct 4 14:43:18 gb360_w vmunix: SCSI: Attempt to access partially open device --
dev: bc001000
Oct 4 14:59:04 gb360_w vmunix: SCSI: Attempt to access partially open device --
dev: bc001000
Oct 4 14:59:04 gb360_w vmunix: SCSI: Attempt to access partially open device --
dev: bc001000

demsg shows

SCSI: Attempt to access partially open device -- dev: bc001000
SCSI: Attempt to access partially open device -- dev: bc001000
SCSI: Attempt to access partially open device -- dev: bc001000
SCSI: Attempt to access partially open device -- dev: bc001000
SCSI: Attempt to access partially open device -- dev: bc001000
SCSI: Attempt to access partially open device -- dev: bc001000

I have attached the output of vgdisplay and lvmtab

Does this help

I have also tried moving lvmtab to .old and vgscan -a.before raising the question.

ioscan shows for disks
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 4 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0

So the disk dmesg moans about is c0t1d0 which is the cd rom ?

Re: Error on ignite

Cheryl Griffin — Fri, 04 Oct 2002 16:21:14 GMT

Here's the problem:
Cur PV 2
Act PV 1

Are there supposed to be 2 disks in this volume group or 1?

Cheryl

Re: Error on ignite

Cheryl Griffin — Fri, 04 Oct 2002 16:23:49 GMT

/etc/lvmtab shows only 1 so if this is true:
/dev/vg00
/dev/dsk/c1t2d0

Verify with:
# lvlnboot -v

# vgreduce -f /dev/vg00
If this succeeds then recreate the /etc/lvmtab by moving this file and recreating it:
# vgscan -v

If vgreduce fails, use ITRC Knowledge Base doc rcfaxlvm008 where you'll boot into LVM maintenance mode and vgexport/vgimport the volume group to correct it.

Cheryl

Re: Error on ignite

Bill McNAMARA_1 — Fri, 04 Oct 2002 16:34:20 GMT

vgscan can be extremely hazardous for system perf.. make sure that you know what you're doing before just rescanning.

The problem will be apparent if you have HA disk arrays /fc loops and are "load balancing" via lvm primary/alternate links.

in anycase - search the forums about the numerical order vgscan recreates the lvmtab in.

You might just be better off doing a vgreduce..

Later,
Bill

Re: Error on ignite

Paul Thomson_2 — Mon, 07 Oct 2002 06:38:11 GMT

Cheryl.

Could you advise. VG00 appears to have been mirrored, but the VG00 only sees one disk.

Should I perhaps do anything else, say, unmirror VG00 before doing anything else.
For instance lvlnboot shows

#lvlnboot -v
lvlnboot: Warning: Can not determine all Physical Volumes on which mirrored cop
ies of
the Logical Volume are located. "/etc/lvmtab" is missing Physical Volumes.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0

So will say vgreduce work in this case ?

Re: Error on ignite

harry d brown jr — Mon, 07 Oct 2002 10:21:22 GMT

Paul,

you have a missing disk - which is probably dead - call HP support and get someone in to replace it!

live free or die
harry

Re: Error on ignite

Mehrens Wilhelm A. — Tue, 08 Oct 2002 10:20:11 GMT

Hi Paul,
i think, you have to recreate your
/etc/lvmtab. It seems to me, that you have some bad disk-entries in lvmtab.
You can check this whith:
strings /etc/lvmtab|more
and compare this with your vg00 configutation:
vgdisplay -v vg00.
If your disk-configuration is diffrent, you can do the following:

- move your lvmtab to lvmtab.old

- run vgscan

- after vgscan you must
vgchange -a y on every VG on your system and execute lvlnboot -R

...but vgscan will instruct you what to do.

Best regards
Will