make_tape_recovery failure due to failed root PV

[arkie]

Hi All,

We had 2 x 146 GB HDDs comprising the root VG, out of which one disk went bad. Since, the redundancy is lost, we want to keep an ignite backup for safety. But, make_tape_recovery is failing due to the changed PV information.

Need help to override this.

NOTE: The disk gone bad-if we try to use this disk, the system crashes and starts rebooting
---------------------------------------------------------------------------------------------------
P.S. This thread has been moved from system administration to ignite-ux- Forum Moderator

[Bijeesh · Accepted solution]

Hope your root VG is mirrored.Since you are confirm that one disk went bad,ignite ux will give error.Ifyou have a good disk with you, replace the bad disk and use vgcfgrestore,follow the steps to make it bootable and do vgsync.
Otherwise using vgreduce romove the bad disk from the vg.Then go ahead with with the Ignite backup.But this backup contains only single disk configuration.
Can you mention the OS and model (Integrity or PARISC)?

[arkie]

Hi Bijeesh,

Thanks for your response.

Basically, the replacement is yet to arrive, so for safe recovery (in case anything further goes bad) it is very important for us to have an ignite backup(even if it is single disk configuration).

I did the following on each vg00 lvolX
# lvreduce -m 0 -A n -k /dev/vg00/lvolX 1
where '1' is the PV key of the stale PV.

After that when I am trying to vgreduce, the following error says:-
# vgreduce vg00 /dev/dsk/c2t0d0
vgreduce: Couldn't query physical volume "/dev/dsk/c2t0d0":
The specified path does not correspond to physical volume attached to
this volume group

Even, I tried to rebuild lvmtab, but the new lvmtab holds no information about vg00-vg00 entry is simply not there...

The model is PARISC (rp4440) and OS is HP-UX 11iv1

[Bijeesh]

Hi,
can you try
#vgreduce -f /dev/vg00/cxtxdx
#mv /etc/lvmtab /etc/lvmtab.date
#vgscan -av
#strings /etc/lvmtab

[arkie]

Hi Bijeesh,

# vgreduce -f /dev/vg00/c2t0d0
vgreduce: Volume group "/dev/vg00/c2t0d0" does not exist in the "/etc/lvmtab" file.

# vgreduce -f /dev/vg00 /dev/dsk/c2t0d0
Usage: vgreduce
[-A Autobackup]
[-l]
VolumeGroupName PhysicalVolumePath... | [-f] VolumeGroupName
only VolumeGroupName is needed for -f option

Kindly help review the outcome of
# vgreduce -f vg00
Will it remove c2t0d0 and retain c2t1d0, as desired.

# mv /etc/lvmtab /etc/lvmtab.$(date +%d%m%y)
# vgscan -av
Creating "/etc/lvmtab".
Couldn't stat physical volume "/dev/dsk/c0t0d0":
Invalid argument

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.


/dev/vg01
/dev/dsk/c14t0d0


Scan of Physical Volumes Complete.
# strings /etc/lvmtab
/dev/vg01
/dev/dsk/c14t0d0

[arkie]

The following worked:-

vgreduce -f vg00
mv /etc/lvmtab /etc/lvmtab.save
vgscan -v

Now lvmtab entries are as desired:-
/dev/vg00
/dev/dsk/c2t1d0
/dev/vg01
/dev/dsk/c14t0d0

make_tape_recovery is hapenning fine.

Thanks for your support, Bijeesh

[Bijeesh]

arkie,
I typed while thinking something else.It is great you mentioned how the problem get resolved.
Can you check the entries in /stand/bootconf ?
If it still contains the entry of removed disk,delete that line.

[arkie]

Hi Bijeesh,

/stand/bootconf has been the same as before (before removing c2t0d0)

# cat /stand/bootconf
l /dev/dsk/c2t1d0

[Bijeesh]

hi,
Its ok.
But don't forget to add the entry of the mirror disk in this file after you mirroring the root disk.