make_recovery errors

[J V Martinez]

When I attempt to run a make_recovery - i am receiveing the following error:

./make_recovery
/opt/ignite/lbin/list_expander -d -v
/opt/ignite/lbin/list_expander -d
/opt/ignite/lbin/list_expander -d
"/opt/ignite/bin/save_config" -f "/var/opt/ignite/recovery/config.recover" "/dev/vx/dsk/rootdg/usrvol" "/dev/vx/dsk/rootdg/standvol" "/dev/vx/dsk/rootdg/rootvol" >> "/var/opt/ignite/logs/makrec.log1" 2>&1
save_config: error - no disk device at /dev/vx/dsk/rootdg/usrvol

Running HPUX 11.11.

Can anyone assist - I am confused as to why it wont work.

BDF output:

# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vx/dsk/rootdg/rootvol
212992 167181 42969 80% /
/dev/vx/dsk/rootdg/standvol
304584 62861 211264 23% /stand
/dev/vx/dsk/rootdg/varvol
4718592 2384539 2188848 52% /var
/dev/vx/dsk/rootdg/usrvol
2015232 1323076 648957 67% /usr
/dev/vx/dsk/sybadg/ss_sybase
1994752 1284930 665732 66% /usr/sybase
/dev/vx/dsk/sybadg/ss_datatools
1048576 272010 728073 27% /usr/datatools
/dev/vx/dsk/rootdg/tmpvol
425984 254879 160480 61% /tmp
/dev/vx/dsk/rootdg/optvol
2539520 1833957 661518 73% /opt
/dev/vx/dsk/rootdg/homevol
32768 11603 19906 37% /home
/dev/vx/dsk/sybadg/bsd_datashr
234496 1506 218482 1% /home/datashr
/dev/vx/dsk/sybadg/bsd_bsdapps
1048576 280725 720065 28% /home/bsdapps
/dev/vx/dsk/sybadg/bsd_dbs60
5352651 1968299 3178304 38% /home/bsdapps/dbs65
/dev/vx/dsk/sybadg/bsd_bcpdat
2097152 1427709 627625 69% /home/bsdapps/bcpdat
/dev/vx/dsk/SOX_logs
1048576 74881 913100 8% /home/SOX_logs
/dev/vx/dsk/sybadg/ss_backup
25845760 8760928 16017249 35% /backup_ss

[Fabian Briseño]

Hello JV.
If I remeber correctly make_recovery is no longer supported, you should run make_tape_recovery instead.

if your tape hardware address is /dev/rmt/0m

# make_tape_recovery -Av

[Fabian Briseño]

I forgot to ask, what version of ignite are you using. ?

[Todd McDaniel_1]

I suspect your issue is similar to this one...its not an ignite error but an LVM issue.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=7162&admit=-682735245+1184608611056+28353475

[Todd McDaniel_1]

I agree with Fabain...

Please upgrade make_tape_recovery, you will be able to get better support from HP and it works very well.


zero points for this post please.

[Torsten.]

Does not sound like a LVM problem, because there is no LVM in play ...

This is VxVM. Unforunately I'm not familiar with this.

How about your ignite version?

[Eric SAUBIGNAC]

Hi Fabian,

Have you resolved the DP / Ignite issue ? Take a look at http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1135363 : i have posted an answer.

Eric

[John Dvorchak]

Hello. First of all the error messages is telling you the problem. There doesn't appear to be a disk device associated with
/dev/vx/dsk/rootdg/usrvol

save_config: error - no disk device at /dev/vx/dsk/rootdg/usrvol

There must have been a usrvol at one time on this box. To see what you have defined in vxvm do the following:

vxprint -g rootdg

You will probably not see a usrvol defined. If you do make sure that the disk device(s) are "active".

I suspect that there is a directory entry in /dev/vx/dsk/rootdg/ (also /dev/vx/rdsk/rootdg/ for usrvol but the vxprint -g rootdg doesn't show one defined. You sure don't have it mounted in the bdf output that I could find.

If you see the directory entry but vxprint doesn't list it as an active or disabled Plex then I would move or delete the files /dev/vx/dsk/rootdg/usrvol and /dev/vx/rdsk/rootdg/usrvol

Then re-run your make_tape_recovery command.

[J V Martinez]

I attempted to use make_tape_recovery - now I get this error

save_config: error - unknown disk type for /dev/dsk/-, not SCSI or HPFL

I noticed /dev/dsk/- is my mirror disk that is down and disabled.

In? dsk/vg name minor# Associated disks/mountpoints
2 x /dev/vx/dsk/rootdg N/A /dev/dsk/c3t6d0 /dev/dsk/-


I checked and my mirror disk is disabled. Is there a way to make the make recovery just point to the primary disk and not even look at the mirror.

[J V Martinez]

One thing also - usrvol does exist

Mirror plex is down. I think my problem is the mirror disk itself. Is there a work around until I get this mirror disk replaced

v usrvol fsgen ENABLED 2015232 - ACTIVE - -
pl usrvol-01 usrvol ENABLED 2015232 - ACTIVE - -
sd rootdisk01-07 usrvol-01 ENABLED 2015232 0 - - -
pl usrvol-02 usrvol DISABLED 2015232 - NODEVICE - -
sd rootdisk02-07 usrvol-02 DISABLED 2015232 0 NODEVICE - -