| Previous | Next |
| VDS_S_REMOUNT_FAILED | VDS_S_VSS_FLUSH_AND_HOLD_WRITES |
VDS_S_RESYNC_NOTIFICATION_TASK_FAILED
This warning concerns notification reporting, not necessarily failure of the mirror or RAID-5 resynchronization itself. MS-VDS states that when the notification task fails, resynchronization notifications will not be sent for the affected mirror or RAID-5 volume. Clients that rely exclusively on progress callbacks can therefore appear stuck even though the underlying volume state continues to change.
Why this state matters
Volume modification notifications can carry a percentage-completed field for operations such as synchronization. A robust management client should retain the affected volume ID and be able to requery volume/plex state instead of assuming “no progress event” means “no progress.” The final operational state and provider/driver events are more important than the missing notification task.
Diagnostic focus
- Record the volume and plex topology associated with the resynchronization operation.
- Do not declare the resync failed solely because expected progress notifications stopped.
- Query current volume/plex properties and health after allowing the underlying operation to proceed.
- Inspect VDS/provider events for notification-task failure separately from disk I/O or plex regeneration errors.
Technical references
MS-VDS error codes · VDS_VOLUME_NOTIFICATION · Volume Plex Object · IVdsAdviseSink::OnNotify · VDS_NOTIFICATION
Looking for a different code? Search another status or error code.