Skip to main content
Solved

Browse failed due to error while mounting virtual machine: FBR mount failed

  • 18 May 2021
  • 1 reply
  • 5539 views

Kamil W
Commvault Certified Expert
Forum|alt.badge.img+11
  • Commvault Certified Expert
  • 83 replies

Hi Guys,

 

I need your help.

 

I have deployed a new FREL (VMware FR20) in the Customer’s environment.

 

During Live Browse operation I am getting the following error.

 

 

Browse failed due to error while mounting virtual machine: FBR mount failed: Caught Exeption [][664][CvBlkDisk::waitForDeviceReady]:[Device FBR_2030087400-5005c102-1b7-2dcd=5495-25226756bafb-1 is not ready to mount] (CV .0x5).

 

It doesn’t matter which virtual machine I choose.

Any ideas?

Best answer by Sebastien Merluzzi

Hi Kamil,

I have checked the error, it can be many things.

it can be Live Browsing from Tape(s), a communication issue with the Media Agent, the OS of the VMs.

First of all, I would like to confirm you are not Live Browsing from Tape(s)?

Then, can you confirm the OSs of these VMs?

CS Client Name and Hostname are correct (case sensitive)?

Can you reboot the FREL and try again?

Can you check the interfaces on FREL, confirm it can communicate with the Media Agent and create a DIP if needed and try a new Live Browse?

 

If none of the above is fixing this, then I would recommend you log a case with us so we can review the logs.

Best Regards,

Seb

View original
Did this answer your question?

1 reply

Forum|alt.badge.img+14

Hi Kamil,

I have checked the error, it can be many things.

it can be Live Browsing from Tape(s), a communication issue with the Media Agent, the OS of the VMs.

First of all, I would like to confirm you are not Live Browsing from Tape(s)?

Then, can you confirm the OSs of these VMs?

CS Client Name and Hostname are correct (case sensitive)?

Can you reboot the FREL and try again?

Can you check the interfaces on FREL, confirm it can communicate with the Media Agent and create a DIP if needed and try a new Live Browse?

 

If none of the above is fixing this, then I would recommend you log a case with us so we can review the logs.

Best Regards,

Seb


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings