The Storage Pools menu includes disks w/ Basic Data Partitions in its list of Physical Disks for Storage Pools then BSODs if you select one them to create a Storage Pool.

Question

What I'm saying is that to my surprise when I go to create a Storage Pool the Server Manager lists and allows me to select disks that are currently partitioned and in use as regular Basic Data partitions. (Even if I have the Server Manager do a refresh). Then if I try to select one of these partitioned in use disks to create a Storage Pool it just BSODs.

1. Have 2 blank disks (could be Initialized but no partitions) and reboot with them connected.
2. Open Server Manager -> File and Storage Services -> Volume -> Storage Pools notice that the 2 blank disks are listed in the PHYSICAL DISKS menu. Leave it all opened.
3. Open Disk Manager and create a Basic Data Partition with a drive letter on each of the disks.
4. In Windows Server Manager force a rescan by clicking the round button with the 2 curved arrows. Notice that the same 2 disks are still listed in the PHYSICAL DISKS menu.
5. Use the "TASKS" dropdown list next to the PHYSICAL DISKS menu to select "New Storage Pool". In the wizard select the 2 disks to be included in the Storage Pool.
6. Proceed with the wizard to create the Storage Pool with these two non-blank, Basic Data Partitioned disks. When you click the "create" button it will BSOD.

In the screenshot below the disk depictions pointed to by the red line are the same disk: A Samsung Disk with a Basic Data Partition and the drive letter 'L', also available in the Storage Pool menus to be in the Storage Pool, but Windows will BSOD if I select that disks and try to create a Storage Pool.

Answer 1

Hello Joe, I am Henry and I want to share my insight about your sharing.

I've reviewed the details and see your screenshots and workflow demonstrate that the Server Manager GUI seems to overlook the rule regarding unallocated disks.

According to Microsoft’s documentation on deploying Storage Spaces via command line (Step 3 – Configure Storage Spaces Direct), it's essential to ensure that the disk contains no existing partitions or data prior to configuration. This requirement helps avoid conflicts during deployment.

https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/deploy-storage-spaces-direct#step-3-configure-storage-spaces-direct, Regarding the Blue Screen of Death (BSOD), I suspect it's caused by the spaceport.sys driver. This could lead to a predictable SYSTEM_SERVICE_EXCEPTION crash—especially if the system attempts to hand over control of a disk that’s already in use. Based on your description, this does seem like the correct error associated with the bug you've encountered.