Forum Discussion

shahfar's avatar
shahfar
Level 5
14 years ago
Solved

[Error] V-126-3 'bmrprep' could not complete the requested operation.

Hi Everyone,

Am getting the following error when doing a PTR operation for a HP-UX 11.31 server. Have attached the 'vxlogview -i 126' output to this post. Any help would  be much appreciated.

 

[Error] V-126-3 'bmrprep' could not complete the requested operation.

Please see logs for additional information.

The shared resoruce tree "srtname" could not be shared by the boot Server hosting it. Please verify that the required configuration
in the boot server is correct. The nfs daemons and configuration files needs to be properly working for this operation
to work.

[Info] V-126-43 Cleaning up. Please wait..

 

  • Hi Everyone,

    Believe it or not, this issue was resolved by removing a tiny error in the hosts file (incorrect name).enlightened

  • Hi Mandar,

    Found them. Please find attached the raw log files for bmrd.

  • I still do not see complete debug level 6 log. Its partial.

    Please confirm your nblog.conf on bmr bs. make sure below values are set in it.

    Default.DiagnosticLevel=6
    Default.DebugLevel=6

    thanks.

    mandar

  • Hi Mandar,

    There is one concern. Are you aware where the SRT is copied when BMR creates the NFS share for the SRT?

    The boot servers has very limited space.

  • it does not copy srt. it creates nw boot image under /opt/ignite path. but that does not require much space.

    actual exported srt will be later accessed/mounted by client in bmr restore mode.

    thanks.

    -mandar

  • Which should mean there is no requirment for /tftpboot?

    I was thinking that there is some kind of trouble with NFS mounting the SRT. But other NFS mounts are working fine. Is there any recommended config for NFS?

     

    Thanks!

  • Then are there any space requirements on specific volumes?

     

    Thanks!

  • It requires when user wants to create ISO image of SRT. In that case it needs some free space in either LVM/VxVM volume on the boot server.

    i believe you are doing NW boot so it is not needed as much.

    thanks.

    -mandar

  • Hi Everyone,

    Believe it or not, this issue was resolved by removing a tiny error in the hosts file (incorrect name).enlightened