Forum Discussion
[ISSUE] b20251 b20257 b20262 b20270 b20282 b20287 Formatting a volume fails
affected builds (tested): b20251,b20257,b20262,b20270,b20282 remotely via Server Manager from b20201 initializing as GPT / reset / clean works fine. creating partition works ...
Sure I can try this too. Yet by design create part pri will automatically select the new part and it should be active as well by default.
YanranHao I tried to repo with the latest 20317 build.
Repro steps: reset drive via Server Manager
Try format via Server manager (incl. initialize GPT)
fails at formatting
This is the output after the known error in diskpart.
Interestingly everything seems fine here.
The Server Manager
OK - initialized the drive as GPT
OK created partitions as expected
NOT OK - even created a volume but it is marked offline (corrected manually - diskpart online)
NOT OK - both volumes are RAW
As suggested I marked it online. As said it is selected by default
assign letter x
format fs=ntfs quick
Format-Volume and also Server Manager Format... works either way.
So the issue is in the commandlet "New-Volume" which is used in the Server Manager wizard to complete following tasks
OK - initializing
OK - Partitioning
FAIL - formatting (volumes remain RAW and primary partition if marked offline with no mounting point or FileSystemLabel
YanranHao it is clear now that the root cause is in Server Manager and the underlying PowerShell command "New-Volume" used by Server Manager
as pure formatting works with:
- diskpart > format
- Server Manager aka PowerShell Format-Volume
- format.com
How should I proceed with the time travel debugging. Which process to monitor? Thanks!
YanranHao I have decided to install this server from scratch. I can confirm this has fixed the issue.
It seem there was a problem with PowerShell New-Volume introed in B20251 which did not fix with upgrades to later versions.
Now I have installed b20234 from scratch the issue is completely gone.
Maybe you can find something in the logs but it seems to be a local issue that happens when upgrading from previous versions.Thanks for your time. I will retry the behaviour once after upgrading to 20239 or later to make sure it does not reappear, is this ok?
Hello YanranHao i have reproduced the issue with Server Manager and recorded it. I have sent you the Onedrive link in a direct message.
let me know if there is anything else I can do and if the file is helpful. Otherwise I can also try to repeat directly with PowerShell New-Volume if this record does not include enough or relevant data.
YanranHaoMicrosoft
smphost- Hello it smphost or snmphost?
- YanranHaoThanks for the followup. To collect time travel, first set up time travel debugging as described at Recording Time Travel Traces. Then run the below commands.
net start smphost # this is to ensure that the mispace process is up and running
$id = (Get-Process | ? { $m = $_ | Get-Process -Module -ErrorAction SilentlyContinue; $m.FileName -like "*mispace*"}).Id
start tttracer.exe "/attach $id" # note the ""
<run repro>
tttracer.exe /stop $id
The file will be dropped at .\svchost01.run.
