- Documentation
Elastic Compute Service
Elastic Compute Service
Troubleshooting
Storage classes issue
EBS Volume issue
How to handle "Not Initialized" disks on Windows
EBS Volume issue
How to handle "Not Initialized" disks on Windows
How to handle "Not Initialized" disks on Windows
When multiple volumes are mounted to a Windows instance, a disk with a "Not Initialized" error is displayed in disk management settings.
In the Windows operating system, each disk is identified by a unique DiskID. When multiple volumes are created from the same snapshot, these volumes inherit the same DiskID. If multiple volumes with the same DiskID are mounted to the same instance at the same time, and you perform operations on them, such as modifying disk status or formatting, the Windows operating system may fail to correctly identify target disks.
- Log in to the target instance.
- Expand "Windows PowerShell", right-click "Windows PowerShell", and then select "More > Run as administrator".
- In PowerShell, execute the following command to open DiskPart.
- Execute the following command to select the faulty disk.
tip
- In the example provided in this topic, Disk 2 is the faulty disk. Replace 2 with the actual serial number of the faulty disk.
- Execute the following command to clear the read-only attribute of the faulty disk.
- Select "Windows System > Run".
- Enter diskmgmt.msc and click the "OK" button.
- In "Disk Management", right-click the target disk, and then click the "Online" button.
- Then, the disk identification exception is successfully fixed.
Last updated: 2026.04.13 16:50:03