Fix 0X800D019A Catatonic Disk Auto-Online

Quick answer

Run a disk check with chkdsk /f on the affected drive, then reset the disk timeout in the registry under HKLM\SYSTEM\CurrentControlSet\Services\Disk\TimeOutValue to 120 seconds.

This error shows up when a disk that went into a catatonic state (basically locked up or timed out) comes back online automatically. The Content Server logs it as an informational event, not a critical failure, but it's a red flag. The disk had a hiccup—maybe a bad sector, a loose cable, or a driver glitch—and the system recovered on its own. But if it keeps happening, you've got a hardware or configuration problem brewing.

Step-by-step fix

Identify the disk
Open Event Viewer. Look for event ID 0X800D019A under Windows Logs > System. The message says "Disk %1 ( %2 ) on Content Server %3". %1 is the disk number. Write it down.
Run a disk check
Open Command Prompt as Administrator. Type chkdsk X: /f (replace X with the drive letter for that disk). Press Enter. You'll see "Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?" Type Y and press Enter. Reboot the server. After the reboot, the disk check runs before Windows loads. It'll scan for bad sectors and file system errors. This takes a while—a few hours for a 2 TB drive.
Check disk timeout setting
The default disk timeout in Windows is 60 seconds. For Content Server workloads, a disk can take longer to respond during heavy I/O. Open Registry Editor (regedit). Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk. If you see a key named TimeOutValue, double-click it. If not, right-click the Disk folder, select New > DWORD (32-bit) Value, name it TimeOutValue. Set it to decimal 120. Click OK. Close Registry Editor. Reboot the server for the change to take effect.
Check the disk's S.M.A.R.T. status
Open Command Prompt as Administrator. Type wmic diskdrive get status. Press Enter. It should say "OK" for all drives. If any say "Bad" or "Pred Fail", replace that drive immediately.
Update disk drivers and firmware
Open Device Manager. Expand "Disk drives". Right-click the affected disk and select "Update driver". Choose "Search automatically for drivers". If it finds nothing, go to your disk manufacturer's website and download the latest firmware. Apply it per their instructions. Reboot.

Alternative fixes if the main one fails

Check the cable connections
Power down the server. Open the chassis. Reseat the SATA or SAS cable on both ends—the drive and the controller. Also reseat the power cable. Look for bent pins or corrosion. Close it up and boot.
Replace the cable
If reseating didn't help, swap the cable with a known good one. Bad cables cause intermittent timeouts.
Move the disk to a different port
On the controller, plug the disk into a different port. If the error moves to the new port number, the controller port is bad. If the error stays on the same disk, the disk is faulty.
Disable and re-enable the disk in Disk Management
Open Disk Management (diskmgmt.msc). Right-click the disk and select "Offline". Wait 30 seconds. Right-click again and select "Online". This resets the driver state.

Prevention tip

Set up regular S.M.A.R.T. monitoring on your Content Server. Use a tool like CrystalDiskInfo or the built-in Windows Storage Spaces health check. Replace any drive that shows reallocated sectors or pending bad sectors. Also, keep your RAID controller firmware up to date. A lot of these catatonic state errors come from stale firmware that can't handle modern drive timeouts.

One real-world example: I saw this error every hour on a Dell R730 with a SAS SSD. Turned out the drive's firmware was three years old. After updating it, the error never came back. Always check firmware first on SSDs.