Skip to main content
Solved

Failed to collect disk block information - What does that mean?

  • January 13, 2022
  • 8 replies
  • 1008 views

Forum|alt.badge.img+4

Hello,

I’m getting a partial failure when doing a backup operation to one of my client in vmware.

 

The failure reason goes as follow: 
SERVERNAME\[DATASTORENAME] SERVERNAME/VMDKNAME-000001.vmdk Failed
Failed to collect disk block information.

 

After doing some google fu and trying to find something in commvault KB I failed short. Anyone can help me in resolving this?

 

Thanks

Best answer by Mike Struening RETIRED

Sharing the solution:

Development has updated that they have discovered the issue at hand and released a diagnostic update. Please download the diag and install on the VSA proxies/MA and backup copy proxies/MA, we need to be at least on minimum version of 11.25.23 on the Proxy MAs.

View original
Did this answer your question?

8 replies

Alireza B
Vaulter
Forum|alt.badge.img+9
  • Vaulter
  • 69 replies
  • January 14, 2022

Hey Martin,

There is a known issue which is addressed with a ceratin hotfix in FR24 and 25.

What’s the environment version?

Cheers,

Ali


Forum|alt.badge.img+4
  • Author
  • Byte
  • 10 replies
  • January 14, 2022

Hello Alizera,

 

I’m on 11.25.14. Should be on the hotfix after the logj4 thing.


MichaelCapon
Vaulter
Forum|alt.badge.img+14

Hi @MartinD ,

 

11.25.14 already contains the HotFix that I had in mind for “Failed to collect disk block information” issues.

Has this error occurred since applying 11.25.14? and does it always occur for the same VM disk?

-Can you confirm if this specific disk has any special configuration? i.e. RDM / Independent, etc.

 

Best Regards,

Michael


Forum|alt.badge.img+4
  • Author
  • Byte
  • 10 replies
  • January 14, 2022

It started since the first time I applied the hotfix on December 14th.

Last week I’ve updated from 11.23 to 11.25 with the hotfix and the issue is still present.

We haven’t made any configuration change in vmware since the update.


Mike Struening
Vaulter
Forum|alt.badge.img+23

@MartinD , if you’re already at the level that contains the expected fix, I would suggest opening a support case for a full analysis.

Can you share the case number here so I can track it accordingly?


Mike Struening
Vaulter
Forum|alt.badge.img+23

Sharing the solution:

Development has updated that they have discovered the issue at hand and released a diagnostic update. Please download the diag and install on the VSA proxies/MA and backup copy proxies/MA, we need to be at least on minimum version of 11.25.23 on the Proxy MAs.


Forum|alt.badge.img

Do we happen to know if this is also an issue for FR26? 

I’m seeing the error occur for one of our customers on 11.26.23


Mike Struening
Vaulter
Forum|alt.badge.img+23

@CommvaultJesus , the solution was a diag update, which has not been released yet.

I would suggest opening a support case (reference this thread) to have a diag cut for 11.26 (or to get the official release ETA).


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