Ntfs Event 153 causing an external drive to be dismounted on WIndows 8 system?

[AWS]

I am running Carbonite's Mirror Image on my Windows 8 system, using an external USB-connected hard drive as the target disk. Carbonite formats the target drive before using it for mirror images. The snapshot process works fine, but it appears

that after the snapshot is complete, Windows is doing something that causes the system to dismount the drive. I assume it is the new automatic disk maintenance service that comes with Windows 8. The Carbonite function was fine under Windows 7,

but when I upgraded to Windows 8 this problem began.

The System log details a series of events whereby a first check of Drive O/Disk 1 (the mirror image drive) is declared healthy: Event 98 (&quotVolume O: (DeviceHarddiskVolume16) is healthy. No action is needed.&quot). But

then a series of Event 153 Warnings show up (&quotThe IO operation at logical block address 1887dd98 [and others] for Disk 1 was retried.&quot), followed by an Event 140 (&quotThe system failed to flush

data to the transaction log. Corruption may occur in VolumeId: O:, DeviceName: DeviceHarddiskVolume13.(A device which does not exist was specified.)&quot)

Oddly, this sequence repeats, including the Event 98 that Drive O is healthy!

Externally, the drive is definitely dismounted from the system as reported by the Carbonite InfoCenter. Once I unplug the USB cable and then reconnect it, the mirror image resumes.

Is there any way to exclude a drive from the Ntfs maintenance? (I've already excluded it from the disk optimization process.)

Additional info: I am running System Mechanic and I have been told that SM can mess up VSS performance in other apps and that even when SM is uninstalled, the problems remain until/unless the OS is refreshed/reinstalled. Any truth to this?

 

 

 

 

View the full article