make_recovery (91 Views)
Reply
Regular Advisor
Manuel Plaza
Posts: 101
Registered: ‎11-30-1998
Message 1 of 4 (91 Views)
Accepted Solution

make_recovery

Hi,
When I run make_recovery in a system with a whole disk the following error appear:
----------------------------------
# make_recovery -A
Option -A specified. Entire Core Volume Group/disk will be backed up.
make_recovery(371): Found /dev/root as the root device file in either /etc/fstab or /etc/mnttab. Try removing the file and running "mount -u".
make_recovery(214): make_recovery(1M) encountered a fatal error.
make_recovery(216): Please fix errors and re-try.
Cleanup
#
------------------------------------------
The -u option is not recognized by mount command.
How can I resolve this ?
Regards,

Honored Contributor
Andreas Voss
Posts: 1,364
Registered: ‎10-14-1997
Message 2 of 4 (91 Views)

Re: make_recovery

Hi,

mount -p does it also, but don't forget to remove /etc/mnttab before useing mount -p.

Regards
Honored Contributor
CHRIS ANORUO
Posts: 1,361
Registered: ‎05-29-1998
Message 3 of 4 (91 Views)

Re: make_recovery

Hi,

Try using make_recovery -ACv -d /dev/rmt/0m.
This will do the entire core volume/disk system backup.
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Honored Contributor
Cheryl Griffin
Posts: 2,701
Registered: ‎05-11-2000
Message 4 of 4 (91 Views)

Re: make_recovery

Specifically, it is the reference to /dev/root that Ignite does not like. By removing the /etc/mnttab file and using the mount (-u, -p, -a, etc) the file is recreated referencing /dev/vg00.

/dev/root occurs when you change init levels.

A quick check to see if make_recovery will fail or not, is to do a bdf. If /dev/root exists, rebuild mnttab. This could easily be scripted so that the recovery process is not delayed unnecessarily.
"Downtime is a Crime."
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.