| Event Id | 3 |
| Source | dmboot |
| Description | dmboot: Failed to start volume <volume name> (<volume letter>:) |
| Event Information | CAUSE: This problem can occur if Windows 2000 was re-installed and during Setup a volume on the dynamic disk was deleted and recreated, or another disk partitioning tool like Fdisk was used to create a new partition. Windows 2000 Setup and other disk partitioning tools can only create basic partitions. Creating any partitions on a dynamic disk outside of Windows 2000 or during Setup creates a disk with both dynamic and basic partition table entries. Re-creating a volume during Windows 2000 Setup changes the partition system-id byte from type 0x42 (dynamic) to a basic partition system-id byte based on the file system chosen, usually 0x06 for FAT, 0x0B for FAT32 or 0x07 for NTFS. Anytime there is a mix of basic and dynamic system-ID bytes, the disk will be viewed as Dynamic Unreadable in Disk Management. |
| Reference Links | RESOLUTION:To work around this problem, use a disk editing tool (such as DiskProbe) and save a copy of the master boot record (sector-0 of the physical disk) to a floppy disk, and then change the incorrect system or boot partition system-ID back to a type 0x42. Next run Regedt32 and ensure the following three services have a Start value of zero: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Dmboot Start:REG_DWORD:0 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Dmio Start:REG_DWORD:0 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Dmload Start:REG_DWORD:0 After you make these manual repairs, if the computer starts successfully, the dynamic disk should be recognized and associated volumes should become accessible again. More Information |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.