CBT disabled after live disk resizing

After live growing client disk (VM) from 400 to 450gb and resizing the NTFS partition to max size, CBT stop working with status :

Getting status of S: failed. Error code: 317
Change block tracking disabled
Volumes with active change block tracking and no crash consistency (v2.5): 
C:

Volumes without change block tracking: 
A:, D:

Last driver log messages:
Write outside of bitmap offset 483180674560 size 512 bitmap size 106496
Change tracking disabledChange tracking disabled in IOCTL_URBCT_RESET_START
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_RESET_START
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS

Is there a way to enable CBT again for this volume without rebooting the client ?
Should a reboot fix the problem ?

Server 2.1.19 / client 2.1.16-cbt

Regards,

Yes, it needs a reboot to fix the problem.

OK, thanks.
This could be an axis of evolution in the future versions of the CBT driver :sunglasses:

Regards,

I recently ran into the same issue, however I did not perform a disk resize. I noticed image backups were taking much longer to run on the 2 clients that had the issue.

Does the CBT client report to the windows event log when this occurs? If so, I can trigger an alert via my RMM tool to get someone’s attention. Is there something that could be done on the server to alert if a client that should be using CBT is not using it?

It would be better if I get more details about the problem and then fix it

I have not rebooted the systems exhibiting the symptoms so if you need me to gather any diagnostic data from them, let me know what you need.

The log messages in the “CBT status” window would be helpful, as well as the volume size(s). If there is something connected with CBT in the client debug log, that would be helpful as well.

This just started sometime on 4/21-4/22. Before that CBT was working properly.

Here is CBT Status messages:

Getting status of E: failed. Error code: 317
Change block tracking disabled
Volumes with active change block tracking and no crash consistency (v2.5): 
C:
Volumes without change block tracking: 
D:
Last driver log messages:
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_RESET_START
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_RESET_START
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS
Change tracking disabled in IOCTL_URBCT_STATUS

Volume C: 99.65GB
Volume E: 749.87GB

Output of client debug log:

2017-04-13 20:16:10: ERROR: Not found
2017-04-14 20:21:11: ERROR: Not found
2017-04-15 20:23:32: ERROR: Not found
2017-04-16 20:25:18: ERROR: Not found
2017-04-17 20:29:30: ERROR: Not found
2017-04-18 20:32:06: ERROR: Not found
2017-04-19 20:35:26: ERROR: Not found
2017-04-20 23:42:11: ERROR: Not found
2017-04-21 23:47:03: ERROR: Not found
2017-04-22 23:47:50: ERROR: Not found
2017-04-23 23:49:01: ERROR: Not found
2017-04-24 23:59:44: ERROR: Not found

You should try to disable / enable CBT again for D: volume.
Under C:\Program Files\UrBackup :

urbctctl.exe uninstall D:

Reboot the client

urbctctl.exe install D: n-c

Maybe a second reboot should be be required.

Regards,

The D: volume is a CD/ROM drive. Does that make a difference?

Replace D: with the volume which failed, in your case E: i guess …

Thanks! Unfortunately the error cause seems to be too long ago, so the log message isn’t present anymore.

Bummer. I will try TomTomGo’s recommendation and a reboot. If the issues happens again I will be watching and can hopefully grab the log in time.