Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk- Creating a new disk only respects drive letter param #179

Closed
eschrader opened this issue Nov 8, 2018 · 6 comments
Closed

Disk- Creating a new disk only respects drive letter param #179

eschrader opened this issue Nov 8, 2018 · 6 comments
Labels
question The issue is a question. stale The issue or pull request was marked as stale because there hasn't been activity from the community.

Comments

@eschrader
Copy link

eschrader commented Nov 8, 2018

    WaitForDisk Disk2
    {
         DiskId = 2
         RetryIntervalSec = 60
         RetryCount = 60
    }
    Disk FVolume
    {
         DiskId = 2
         DriveLetter = 'F'
         FSLabel = 'DATA'
         FSFormat = 'NTFS'
         AllocationUnitSize = 64KB
         DependsOn = '[WaitForDisk]Disk2'
    }

This code keeps creating a drive F (no label) in File System format RAW with full capacity. Why does it not apply the label?
image

@eschrader
Copy link
Author

Possibly related to #157

@eschrader
Copy link
Author

Actually, I just waited about 27 minutes and its all fixed now it looks like. Maybe it just takes a long time?

\"Message\": \"The PowerShell DSC resource \\u0027[Disk]FVolume\\u0027 with SourceInfo \\u0027::15::9::Disk\\u0027 threw one or more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details.\",\r\n

@PlagueHO
Copy link
Member

PlagueHO commented Nov 9, 2018

Hi @eschrader - it shouldn't usually take that long to partition and format a disk. It usually takes under 10 seconds. Was the disk a virtual disk? Could you ask DSC to output the verbose logs as that should tell us the particular disk task that is taking so long (e.g. the initialization, partitioning, volume creation).

@PlagueHO PlagueHO added the question The issue is a question. label Nov 9, 2018
@eschrader
Copy link
Author

Hi @eschrader - it shouldn't usually take that long to partition and format a disk. It usually takes under 10 seconds. Was the disk a virtual disk? Could you ask DSC to output the verbose logs as that should tell us the particular disk task that is taking so long (e.g. the initialization, partitioning, volume creation).

Yea I am using an Azure IaaS VM with a new data disk. I was using Azure Automation, so maybe that's why it took so long.

@stale
Copy link

stale bot commented Dec 10, 2018

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the stale The issue or pull request was marked as stale because there hasn't been activity from the community. label Dec 10, 2018
@stale
Copy link

stale bot commented Jan 19, 2019

This issue has been automatically closed because it is has not had activity from the community in the last 40 days.

@stale stale bot closed this as completed Jan 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue is a question. stale The issue or pull request was marked as stale because there hasn't been activity from the community.
Projects
None yet
Development

No branches or pull requests

2 participants