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

If WriteCache disk on master is GPT-partiton then uniqueid doesn't match #69

MathiasSVA opened this Issue Sep 27, 2018 · 1 comment


2 participants
Copy link

MathiasSVA commented Sep 27, 2018

If the WriteCache disk on the master is formatted in GPT-style the uniqueid that is saved to the registry will not be applied correctly because BIS-F always creates a MBR-partition for the writecache.

Suggestion: If the uniqueid saved in the registry has a length of a GUID, then create a GPT partition, else if length = 8 create MBR

furthermore when getting the uniqueid via diskpart the curly brackets have to be removed. diskpart will return the guid in curly brackets:

DISKPART> uniqueid disk
Disk ID: {C1C66B06-6C5D-4AD8-BE48-0405694202A7}

But when setting the uniqueid it expects the brackets to be removed:
DISKPART> uniqueid disk ID={C1C66B06-6C5D-4AD8-BE48-0405694202A7}

The specified identifier is not in the correct format.
Type the identifier in the correct format:
in hexadecimal form for an MBR disk or as a GUID for a GPT disk.

So best when tested if it is a GPT uniqueid do a $str = $str -replace '[{}]' to remove the brackets before saving to registry.


This comment has been minimized.

Copy link

matthias-schlimm commented Sep 28, 2018

thx, good point

@matthias-schlimm matthias-schlimm added this to To do in Bugs Bunny via automation Oct 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment