NS_I_RESTRIPE_START 0X400D0193: What It Really Means

You're digging through Event Viewer after a long night of copying files to your new 4TB drive, and there it is: NS_I_RESTRIPE_START with code 0X400D0193. The event log says "Restripe operation has started." Your first instinct is to panic — anything with a hexadecimal code and the word "restripe" sounds like your data is being shredded. But relax. This is a notice, not an error. The Windows error code classification actually lists it under "informational."

Here's the specific trigger: you just added a new physical disk to a Storage Spaces pool, or you removed one that was failing. The Storage Spaces engine, which manages the virtual disks on top of your physical drives, immediately starts rebalancing data across the new layout. That rebalancing pass is called a restripe. The event fires the moment that operation starts. You'll also see this if you changed the resiliency type (for example, from Simple to Parity) on an existing volume — that forces a full restripe too.

Root cause: what's actually happening here

Storage Spaces works in stripes — it chops your data into chunks and spreads them across multiple disks. That's how you get speed (multiple disks reading at once) and redundancy (parity or mirror copies). When the physical layout of your pool changes, the old stripes no longer match the new disk count. So Storage Spaces kicks off a background job that reads every chunk, re-calculates where each chunk should live, and writes it back. That's the restripe.

The reason it's not a real error is simple: it's a status message. The operation started successfully. If the restripe failed, you'd see a different code with NS_I_RESTRIPE_FINISHED failing, or a genuine error like 0x8007001F (device not ready) or 0x8007012F (disk failure). The 0X400D0193 code just tells you the process kicked off.

That said, you don't want to ignore it entirely. A restripe that never finishes means your pool is in a degraded state — writes may be slower, and if you're using parity, you've lost your redundancy until it completes. So the fix isn't to 'fix' the error, it's to verify the restripe actually completes and your pool returns to healthy status.

How to check it's working and not stuck

Here's the practical part. You don't need to restart anything or run a repair tool. Just confirm the restripe is progressing:

1. Open PowerShell as Administrator. You can hit Win + X and pick "Windows PowerShell (Admin)" or "Terminal (Admin)" on Windows 11.
2. Run this command to see the health of your storage pool:

Get-StoragePool | Format-List FriendlyName, HealthStatus, OperationalStatus

You want HealthStatus to say Healthy. If it says Warning or Unhealthy, then you've got a separate problem that needs attention.

3. Now check for active repair/restripe jobs:

Get-StorageJob | Format-List Name, JobState, PercentComplete, IsBackgroundTask

When the restripe is running, you'll see a job with a name like Repair or Resync, a JobState of Running, and a PercentComplete that slowly climbs. That's your confirmation the operation is doing its thing.

You can also watch progress in real time with:

Get-StorageJob | Select-Object Name, PercentComplete

Run that repeatedly — from my experience on a 6-drive pool with 3TB of data, it takes anywhere from a few hours to a full day, depending on disk speed and how much data is being moved. SSDs will finish far quicker than spinning disks.

If it still fails: what to check next

Suppose you run the commands above and see no job, or the job shows a state of Failed or Suspended. Then you've got a genuine problem. Here's what to look at:

1. Check for a physical disk failing

Run Get-PhysicalDisk | Format-List FriendlyName, HealthStatus, OperationalStatus. Any disk with HealthStatus not equal to Healthy is your culprit. Replace it. The restripe won't proceed if a disk is dropping off mid-operation.

2. Verify you have enough free space

Restriping needs temporary space — it reads a chunk, writes it to a new location, then deletes the old one. If your pool is over 95% full, the operation may stall. Free up space by moving files off the pool or adding another disk.

3. Check the system event log for storage-related errors

Use Event Viewer and filter for Event ID 770 or 771 from source Microsoft-Windows-StorageSpaces-Driver. Those events give you the underlying reason the restripe stopped. A common one is 770 with a status like 0x80070070 — that's disk full.

4. Try a manual repair

If the job is stuck, you can force a repair with:

Repair-VirtualDisk -FriendlyName "YourVirtualDiskName" -Confirm:$false

Just swap in the actual name from Get-VirtualDisk. This kicks off a fresh repair pass. Note that this doesn't remove the event log entry — the 0X400D0193 you already logged will stay there. That's fine, informational events never clear themselves.

One last opinion: don't disable Storage Spaces background jobs in the name of "performance." I've seen people set the pool to never rebalance to avoid this message, and then they lose data when a disk fails because they never noticed the pool was degraded. The notice is your friend. Let it run.