NS_I_DISK_REBUILD_FINISHED (0X400D0057) – Disk Rebuild Done

Wait – this is not a real error

You see event ID 0X400D0057 with message NS_I_DISK_REBUILD_FINISHED and you're worried something's broken. I get it. But here's the thing: this event is informational. It's the same level as a log entry saying 'we finished the job'. No alert needed.

What's actually happening here is your Content Server (often part of Symantec or Veritas Cluster Server) just completed a disk rebuild operation. That's it. The disk %1 on drive %2 for server %3 is now consistent with its replica.

Simple check (30 seconds)

Open Event Viewer on your Content Server. Look under Windows Logs > System. If you see only a single 0X400D0057 event and no corresponding errors like NS_I_DISK_REBUILD_STARTED or disk failures, you're done. Ignore it.

If you see it every day at the same time, your server might be rebuilding a healthy disk unnecessarily. But a single occurrence after a crash or maintenance is normal.

Moderate check (5 minutes)

Still worried? Let's confirm the disk state. Run this command as admin on the Content Server:

diskpart
list disk
select disk X
detail disk

Replace X with the disk number from the event. Look for Status: Online and Read-Only: No. If you see No Media or Failed, that's a real problem – but it wouldn't show rebuild finished. So if it's online, your disk is fine.

Also check the Content Server logs in C:\Program Files\Veritas\VxSvc\logs or /var/VRTSvcs/log on Linux. Search for the word REBUILD around the timestamp. If you see REBUILD STARTED followed by this FINISHED event, everything worked as expected.

Advanced fix (15+ minutes) – when to actually act

I'll tell you the three scenarios where this event matters:

1. It appears every 4-6 hours – Your disk might be dropping offline briefly. Check the physical cable, HBA, or the fiber channel link. Run chkdsk /f on the disk during maintenance window. If it's a SAN volume, ask storage team to check for CRC errors.
2. It appears after every reboot – Someone configured the disk as a dynamic disk but it's not shared properly. In Veritas Cluster Server, a disk that's not in the cluster group will rebuild every time. Fix: add the disk to the correct cluster disk group.
3. You see error code 0X400D0057 paired with 0X400D0056 (rebuild started) – That's actually the normal pair. But if the time between them is less than 1 minute, the rebuild is failing silently. Check the Content Server's process logs for E_FAIL or ERROR_IO_DEVICE. That points to a bad disk sector.

The reason step 3 works is because a rebuild that finishes in under a minute on a multi-terabyte disk is physically impossible. The server is lying – it started, then immediately gave up and marked it done. Real rebuilds on spinning disks take hours or days. On SSDs, maybe minutes, but not under 60 seconds.

What not to do

• Don't restart the server – you'll restart the rebuild cycle.
• Don't reseat cables unless you see actual I/O errors.
• Don't call support unless this event repeats more than 3 times in 24 hours.

If you need to suppress the log entry (some admins hate seeing 'info' events), you can filter it in Event Viewer under Custom Views. But I don't recommend hiding it – you'll miss the pattern if it becomes frequent.

Bottom line

0X400D0057 is your Content Server saying 'I'm done fixing a disk'. Most of the time, you don't need to do anything. Keep an eye on it if it repeats, and always pair it with other events before assuming trouble. Your server is probably fine.