1 Answer
- Newest
- Most votes
- Most comments
1
Is the volume in MBR format? This only supports up to 2TB, for anything more the disk format needs to be GPT.
See this question & answer on the Microsoft website, which seems to deal with a physical device rather than a cloud instance, but the underlying explanation is the same https://answers.microsoft.com/en-us/windows/forum/all/disk-partition-limit-of-2tb-in-windows-10-64-bit/3f8df997-6638-489f-a3cd-e12b0625deec
Much more detail is here https://learn.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/support-for-hard-disks-exceeding-2-tb
Relevant content
- asked 8 months ago
- asked 2 years ago
AWS OFFICIALUpdated 7 months ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
To add to this it's typically not recommended to setup SQL server on the root volume of the OS, instead it's better to partition out the usage to several different disks with the needed performance specification for those disks.
Thanks, To fix this, which senario would be the best? <S1> Copy all existing root ebs volume to a new one which can be bigger than 2TB (because it is not root volume), then delete the root volume and use only other newly created volume. and add more volume as needed in the future. <S2> Reinstall SQL in a new ebs volume and attach necessary database resources (or copy) into the same volume or the separate volumes. I also thank Rob_H's comments. Could you elaborate bit? Cheers