Windows 10: Storage space on Windows 11 build 22000.588: "unhealthy, detached, reason "unknown"", but...

I have a storage space that's detached, unhealthy, but the reason is listed as "unknown." The storage pool is healthy, and all the physical disks are healthy. I reset the physical disks anyway and rebooted hoping that might clear whatever is preventing the storage space to connect. That didn't make a difference. I can't force the storage space to connect in its current state, but I haven't found a Powershell command to provide any further information about what's wrong with the space.Any ideas? The physical disks in the storage space are the six, 1.82 TB ST2000DM008-2FR102s. The storage space

:)

 

Unknown storage space taker

Hi Andrew,

In order to help you with your concern regarding unknown storage space taker, kindly answer the following questions first:

• Have you made any recent changes to your Windows 10 PC prior to getting this issue?
  
• Is your Windows 10 PC up-to-date? If not, click this
  link.
• Have you checked the helpful post of biterbit dated September 19, 2015? If not yet, please click this
  
  thread.
• What troubleshooting steps have you tried so far?

Kindly reply to this thread for us to help you further.

Regards.

 

Storage Spaces: 1 of 4 HDs failed, can’t access/repair pool

1st problem to be resolved if possible: readonly pool, detached virtualdisk
2nd problem: replacing physicaldisk, recalculating data, removing failed physicaldisk object; more on it later

Suicidal choice although it can be created; if one device influences others, any damage can arise.

try this:
Code:

and paste results here
also see event log Microsoft - Windows - Storage Spaces Driver - Operational for problems, paste them here too

If this does not work, try to extract the "failed" harddisk from USB enclosure and connect it directly to SATA interface.

 

Storage Pool Read-Only Unhealthy

Okay, I've gotten myself into a pickle. Situation:

1. I had a 4-disk, mirrored storage pool
   
2. I wanted to remove 2 disks, so I retired them (prepared them for removal)
   
3. I waited until the process was done and Get-PhysicalDisk reported "retired"
   
4. I PHYSICALLY removed them and formatted them without completing the final "remove" step.
   

SO, now I have a very odd situation. I have a 4-drive pool with two "retired" drives that have "lost communication". All data is on the two remaining drives, but they are inaccessible because the pool is "unhealthy". The pool is in a read-only OperationalStatus, so I can't modify the pool configuration.

I have tried to set the pool's -IsReadOnly flag to $false. Works. BUT the operational status remains read-only, perhaps because the health status is unhealthy? I even physically reattached the missing disks. But because the disks had been reset, they aren't recognized by the pool.

Anyway, the current relevant status of pools, physical and virtual disks is as follows:

The two "Can Pool" drives are the ones that I removed and reattached (*58 and *33). The two that are part of the pool are (probably obviously) *H4 and *QX.

Anybody have any ideas? At least short of doing a relatively expensive recovery? All I need to do is remove the two "retired" drives from the pool. Seems like it's just a database issue. Certainly no data should be lost or corrupt.

Oh, Windows 10, not server, if it matters.