1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Thank you for writing in.
The InitializeDisks.ps1 script helps you to initialize the disk and assign the drive letter as per the DriveLetterMappingConfig.json if everything is successful. Now it depends on what configuration you have inside your Drivelettermappingconfig.json file and according to that mapping would take place.
You can review the json file by going to the C:\ProgramData\Amazon\EC2-Windows\Launch\Config\DriveLetterMappingConfig.json location and make sure it reflects as Drive Letter as D. Please review this document for more information.
In case you are still facing an issue, I would suggest raising a Support Ticket with us so that we can take a deeper look.
Thanks!
answered a month ago
Relevant content
- asked a year ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 15 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks Rashid, we found out the problem.
The instances that have the issue have an outdated version of the script C:\ProgramData\Amazon\EC2-Windows\Launch\Module\Scripts\Test-Ephemeral.ps1. We spotted it by comparing to another instance where the ephemeral was correctly mapped to Z.
It seems that new hardware returns disk information slightly different and the check for ephemeral has changed from
to
The extended check picks the ephemeral correctly and maps it to Z:, the json file is not relevant, as I changed it to be Z and it's completely ignored for some reason.
To update the script pack to the latest version we just followed this steps https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-download.html
Thanks!