error while Save_config

[Azaru]

Hi All,

I have configured the ignite server and added the client. Now trying to create network recovery archive from server. But while doing it the recovery fails. The roor is as follows.


IGNITE_SERVER> /var/opt/ignite/clients/misapp3/recovery/2008-07-04,11:18>cat recovery.log


======= 07/04/08 11:18:21 IST Started /opt/ignite/bin/make_net_recovery. (Fri
Jul 04 11:18:21 IST 2008)
@(#)Ignite-UX Revision C.7.6.100
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA0806/ignite/src@73644 Last Modified: 2008-04-15
17:21:10 -0600 (Tue, 15 Apr 2008)


* User interface starting.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x0016353EF3E2/recovery/defaults.

* User interface completed successfully.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x0016353EF3E2/recovery/defaults.

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/0/1/1/0.1.0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
016353EF3E2/recovery/2008-07-04,11:18/system_cfg vg00
save_config: Error - The command "lvlnboot -v vg00" returned 1. If needed, the command "vgscan -v " can be used to recreate the "/etc/lvmtab" file. The lvlnboot error output is: lvlnboot: Couldn't query physical volume "/dev/dsk/c3t0d0s2": The specified path does not correspond to physical volume attached to this volume group
ERROR: /opt/ignite/bin/save_config failed


======= 07/04/08 11:18:42 IST make_net_recovery completed unsuccessfully


Anybody faced this issue before and recovered?

Thanks

[Ivan Krastev]

Have you changed disk on this machine ?
Check your boot configuration with lvlnboot.
Try to recreate /etc/lvmtab as well.

regards,
ivan

[OFC_EDM]

/dev/dsk/c3t0d0s2

Either that disk doesn't physically exist and is incorrectly stated in your lvmtab.

Or you have an issue with your disk and the system can't see it.

You have to remedy that first.

If the physical disk exists it may be down or bad. So you have to get it up and running again and ensure it can be seen (and CLAIMED) in an ioscan.

If it doesn't physically exist then you have to clean up your lvmtab.

[Azaru]

Hi,

It is in claimed state only.

See the ioscan result for disk.




disk 3 1/0/1/1/1.0.0 sdisk CLAIMED DEVICE COMPAQ BD14689BB9
/dev/dsk/c3t0d0 /dev/dsk/c3t0d0s2 /dev/rdsk/c3t0d0 /dev/rdsk/c3t0d0s2
/dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s3 /dev/rdsk/c3t0d0s1 /dev/rdsk/c3t0d0s3
/dev/dsk/c3t1d0 /dev/rdsk/c3t1d0

[Fabio Ettore]

Hi Azaru,

ok about ioscan but please post also

lvlnboot -v
strings /etc/lvmtab

That should clear the reason save_config is failing.

Best regards,
Fabio

[Azaru]

Hi,

Please find the results of

lvlnboot -v and
strings /etc/lvmtab


misapp3:root-/>lvlnboot -v
lvlnboot: Couldn't query physical volume "/dev/dsk/c3t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
misapp3:root-/>


misapp3:root-/>strings /etc/lvmtab
/dev/vg00
/dev/dsk/c0t1d0s2
/dev/dsk/c3t0d0s2
misapp3:root-/>

thanks

[Fabio Ettore · Accepted solution]

Hi,

so lvlnboot -v is the reason why save_config is failing.
I would troubleshoot the problem in the following way:

- try to recreate lvmtab as suggested by the message itself:
mv /etc/lvmtab /etc/lvmtab.OLD
vgscan -v

- if that doesn't help then try
lvlnboot -R
to recover links for lvols on BDRA;

- if that doesn't help troubleshoot the health of the disk, check by diskinfo, try dd, check syslog.log for errors.

Also does vgdisplay -v vg00 shows /dev/dsk/c3t0d0s2 or is it just a message from lvlnboot? Is /dev/dsk/c0t1d0s2 a mirror disk?

HTH.

Best regards,
Fabio

[Rasheed Tamton]

The second disk seems to be a mirrored one. Did you replace the disk recently. Can you do like this:

mv /etc/lvmtab /etc/lvmtab.old
vgscan -v (to recreate the /etc/lvmtab)
strings /etc/lvmtab

rgds.

[Jeeshan]

execute the command

#vgdisplay -v vg00

[Azaru]

Hi,

I have tried every steps that u have given here. Nothing is resolved my problem.
And the health of the disk is

misapp3:root-/>diskinfo /dev/rdsk/c3t1d0
SCSI describe of /dev/rdsk/c3t1d0:
vendor: COMPAQ
product id: BD14689BB9
type: direct access
size: 143374744 Kbytes
bytes per sector: 512
misapp3:root-/>

And



misapp3:root-/>mv /etc/lvmtab /etc/lvmtab.old
misapp3:root-/>vgscan -v
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg00".
Physical Volume "/dev/dsk/c0t0d0" contains no LVM information
Physical Volume "/dev/dsk/c3t1d0" contains no LVM information

vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg00 failed.

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c3t0d0s2

Scan of Physical Volumes Complete.
*** LVMTAB has been created successfully.
*** Do the following to resync the information on the disk.
*** #1. vgchange -a y
*** #2. lvlnboot -R
misapp3:root-/>vgchange -a y
misapp3:root-/>lvlnboot -R
misapp3:root-/>lvlnboot -v
misapp3:root-/>lvlnboot -v vg00
lvlnboot: Volume group "/dev/vg00" does not exist in the "/etc/lvmtab" file.
misapp3:root-/>strings /etc/lvmtab
misapp3:root-/>

here the vgscan -v command is not creating the fresh lvmtab.

What do we can do? Please provide me a good conclusion.

Thanks

[Fabio Ettore]

Hi,

I think there is confusion.

- First of all the boot device from save_config message doesn't correspond to HW path of ioscan that you posted:

From save_config:
* Boot device is: 0/0/1/1/0.1.0

From ioscan posted:
disk 3 1/0/1/1/1.0.0 sdisk CLAIMED DEVICE COMPAQ BD14689BB9
/dev/dsk/c3t0d0 /dev/dsk/c3t0d0s2 /dev/rdsk/c3t0d0 /dev/rdsk/c3t0d0s2
/dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s3 /dev/rdsk/c3t0d0s1 /dev/rdsk/c3t0d0s3
/dev/dsk/c3t1d0 /dev/rdsk/c3t1d0

- then who is /dev/dsk/c3t1d0? I wonder it is showed on ioscan output, I'd expect it is on another HW path. More about c3t1d0 from info posted so far:

from vgscan -v:
Physical Volume "/dev/dsk/c3t1d0" contains no LVM information

It sounds like no pvcreate was never issued on it, so why did you launch diskinfo on it?

I think you should first clear which disk you expect to be the boot disk, I would suppose /dev/dsk/c3t0d0s2 (on Itanium platform s2 is always the EFI partition/boot of vg00).
So when I suggest doing checks on boot disks I suggest doing diskinfo and

dd if=/dev/rdsk/c3t0d0s2 of=/dev/null

And after a while stop by CTRL+C, do you get an I/O error?

Also you didn't response about vgdisplay -v vg00 and messages in syslog.log about disk problems. However after moving lvmtab it doesn't make sense doing vgdisplay, if no disk was found no disk will be showed.

vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg00".

This is a clear message that you should check the disks.

We would like to give you a good conclusion, but here it needs more troubleshooting.
It sounds like you could not reboot your system until the problem is not solved.

Best regards,
Fabio

[Azaru]

Hi Issue has been resolved

The disk was misplaced actually. So i have replaced it to original place and tried the following

misapp3:root-/>mv /etc/lvmtab /etc/lvmtab.old
misapp3:root-/>vgscan -v
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg00".
Physical Volume "/dev/dsk/c0t0d0" contains no LVM information
Physical Volume "/dev/dsk/c3t1d0" contains no LVM information


/dev/vg00
/dev/dsk/c0t1d0s2
/dev/dsk/c3t0d0s2


Scan of Physical Volumes Complete.
*** LVMTAB has been created successfully.
*** Do the following to resync the information on the disk.
*** #1. vgchange -a y
*** #2. lvlnboot -R
misapp3:root-/>strings /etc/lvmtab
/dev/vg00
/dev/dsk/c0t1d0s2
/dev/dsk/c3t0d0s2
misapp3:root-/>

misapp3:root-/>vgchange -a y
Volume group "/dev/vg00" has been successfully changed.
misapp3:root-/>lvlnboot -R
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
misapp3:root-/>vgdislay -v vg00
sh: vgdislay: not found.
misapp3:root-/>vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4356
VGDA 4
PE Size (Mbytes) 32
Total PE 8692
Alloc PE 5216
Free PE 3476
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 64
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/stale
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol3
LV Status available/stale
LV Size (Mbytes) 3072
Current LE 96
Allocated PE 192
Used PV 2

LV Name /dev/vg00/lvol4
LV Status available/stale
LV Size (Mbytes) 2048
Current LE 64
Allocated PE 128
Used PV 2

LV Name /dev/vg00/lvol5
LV Status available/stale
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol6
LV Status available/stale
LV Size (Mbytes) 5120
Current LE 160
Allocated PE 320
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/stale
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol8
LV Status available/stale
LV Size (Mbytes) 6656
Current LE 208
Allocated PE 416
Used PV 2

LV Name /dev/vg00/lvol9
LV Status available/stale
LV Size (Mbytes) 40960
Current LE 1280
Allocated PE 2560
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c0t1d0s2
PV Status available
Total PE 4346
Free PE 1738
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c3t0d0s2
PV Status available
Total PE 4346
Free PE 1738
Autoswitch On
Proactive Polling On
misapp3:root-/>



Now its fine. Thanks for everybodys support in resolving the issue.

Azaru

[Azaru]

thanks
azaru