Closed eschrader closed 5 years ago
Possibly related to #157
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
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).
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.
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.
This issue has been automatically closed because it is has not had activity from the community in the last 40 days.
This code keeps creating a drive F (no label) in File System format RAW with full capacity. Why does it not apply the label?