HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to Create NFS mount Archive directory.

 
SOLVED
Go to solution
David Willams
Super Advisor

Failed to Create NFS mount Archive directory.

# make_net_recovery -s 192.168.114.230
* Creating NFS mount directories for configuration files.

======= 09/20/09 02:51:27 EDT Started make_net_recovery. (Sun Sep 20 02:51:27
EDT 2009)
@(#) Ignite-UX Revision C.6.2.241
@(#) net_recovery (opt) $Revision: 10.695 $

* Testing for necessary pax patch.
* Passed pax tests.
* Checking Versions of Recovery Tools
* Creating System Configuration.
WARNING: The volume group /dev/vg00 will be only partially included in the
System Recovery Archive. This means that not all files and
directories on this volume group will be restored when the archive is
installed. This message can be suppressed using the "-P s" option for
make_net_recovery. See make_net_recovery(1M) for more details.

* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
013215B7554/recovery/2009-09-20,02:51/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vghpvm
* /usr/sbin/vgcfgbackup /dev/vghpvm
* Creating Map Files for Volume Group /dev/vghpvm
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vghpvm.mapfile /dev/vghpvm

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_m
nt/0x0013215B7554/recovery/2009-09-20,02:51/archive_cfg -g /var/opt/ig
nite/recovery/client_mnt/0x0013215B7554/recovery/2009-09-20,02:51/flis
t -n 2009-09-20,02:51 -r ipf -b 64 -d Recovery\ Archive -L
/var/opt/ignite/recovery/arch_mnt -l
192.168.114.230:/var/opt/ignite/recovery/archives/rx26-111 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Networking Archive

Permission denied
ERROR: Unable to mount or write
192.168.114.230:/var/opt/ignite/recovery/archives/rx26-111
On 192.168.114.230 you may need to:
mkdir -p /var/opt/ignite/recovery/archives/rx26-111
chown bin:bin /var/opt/ignite/recovery/archives/rx26-111

vi /etc/exports (add or modify an entry). The /etc/exports file on
"192.168.114.230" should contain the entry:
"/var/opt/ignite/recovery/archives/rx26-111 -anon=2,access=rx26-111".
After editing the /etc/exports file, run exportfs -av

If you need to change the owner of the directory,
you will also need to re-export the directory.

See make_net_recovery(1M) for more information.
ERROR: Failed to Create NFS mount Archive directory.


======= 09/20/09 02:51:47 EDT make_net_recovery completed unsuccessfully
[rx26-111]/
#
2 REPLIES
Stephan._1
Trusted Contributor
Solution

Re: Failed to Create NFS mount Archive directory.

Hi,

did you test the suggestion the error give?

On 192.168.114.230 you may need to:
mkdir -p /var/opt/ignite/recovery/archives/rx26-111
chown bin:bin /var/opt/ignite/recovery/archives/rx26-111

vi /etc/exports (add or modify an entry). The /etc/exports file on
"192.168.114.230" should contain the entry:
"/var/opt/ignite/recovery/archives/rx26-111 -anon=2,access=rx26-111".
After editing the /etc/exports file, run exportfs -av

Did it work before? Have there been changes in the enviroment / network?
Share what you know, learn what you don't.
David Willams
Super Advisor

Re: Failed to Create NFS mount Archive directory.

thanks u