-
Notifications
You must be signed in to change notification settings - Fork 52
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 Initializing disk with UniqueId #224
Comments
Hi @briefcase-Wanker (Inbetweeners fan 😁), this does look like a bug. It does look like it could be similar to this issue: #80 And it looks like I wasn't able to solve the problem. Could you run the following command on your machine and show the output? Get-Partition `
-DriveLetter 'G:' `
-ErrorAction SilentlyContinue | fl * Also, what is the result of this command: Get-Partition `
-DriveLetter 'G:' `
-ErrorAction SilentlyContinue | Get-PartitionSupportedSize |
Hi @PlagueHO Cheers for the reply output of the commands is below.
|
Hi @briefcase-Wanker - ah right, this explains why the error occurs: It looks like this is caused by clustering because there are three partition objects with G: drive assigned. The first object is the physical partition and the second two appear to be some representation of the clustered partition on each node of the cluster. It is possible that we can fix this by ignoring all but the first partition, but this may have unwanted side affects and will be difficult to test with automation. But we should try and release a preview version with the fix in place so you can test it - would you be OK testing a preview version? |
Additional Note: I can't release new versions of this module until I've updated this to the new CI/CD pipeline. This is #223 |
Happy to test the preview when it’s ready. |
Hi,
I am initializing a number of disk using the disk resource. When I push a configuration it works no issue. If I push the configuration again the test fails. If the servers are restarted the disk drives are marked offline until either I enable them again or I push the configuration again in which case it is successful.
Is this expected behavior or am I doing something incorrectly.
Below is the output of the push.
I am using windows clustering for SQL AAGs not sure if that could be effecting it somehow.
The text was updated successfully, but these errors were encountered: