Showing results for 
Search instead for 
Do you mean 

make_recovery

SOLVED
Go to Solution
Regular Advisor Regular Advisor

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,

1 ACCEPTED SOLUTIONS
Honored Contributor Honored Contributor

Re: make_recovery

Hi,

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

Regards
3 REPLIES
Honored Contributor Honored Contributor

Re: make_recovery

Hi,

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

Regards
Honored Contributor Honored Contributor

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.
Highlighted
Honored Contributor Honored Contributor

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."