Solved Storage Spaces - Disks Inaccessible

Hello. Long time lurker here... finally posting because I am in over my head.

I have an old PC that I use as a NAS/backup box. I was using windows storage spaces with 6 drives. I upgraded my PCIE-SATA card, and in doing so, I had changed a few of the ports that some drives were plugged in to. As a result, windows lost the ability to access either of my two pools across two storage spaces.
I don't have any screenshots, but I can get them if necessary. This PC is usually ran headless, and I don't have a network drop in the room that I have a monitor for it.

The storage space that I am most concerned about consists of three 6TB drives in parity. I had used about 90% of the storage space. It wasn't full, but it had been showing up as red in explorer. The storage space was created on v1809 build 17763.6414.
As I said, after I moved a few things around, my PC can see the drives, crystaldisk shows they are all healthy, but storage spaces says they are inaccessible.
I attempted to add another drive to see if that would help, but it does not. I tried to add a 3TB drive to the pool. It allowed me, but I still can not access anything. Now, I can not remove the drive from the pool, and I'm receiving "the pack does not have a quorum of healthy disks".

I upgraded the PC to 11 24H2 build 26100.1742 as an attempt to help, but everything is the same here.

Get-StoragePool shows two, primordial and my storage pool, both are showing up as healthy.

If anyone has any thoughts, all are appreciated. If I can get the space online, even as read-only, then I can back up to another solution... but this is my only copy of my data (I know the rule of 3), and I didn't expect that plugging the disks in to another sata port would hose everything.

I run NAS home. I would avoid 24H2 as 24H2 has a tight security setup on networking.
(you can read many posts about this issue and its fix)

siliconbeaver said:

I run NAS home. I would avoid 24H2 as 24H2 has a tight security setup on networking (you can read many posts about this issue and its solution)

Click to expand...

Upgrading to 24H2 was only a means of troubleshooting... hoping that perhaps whatever bug I encountered got squashed in that version, but it doesn't seem to have been.

I’m NOT sure reason of the problem.

In my practice, “showing up as red in explorer” wouldn’t be a problem. My disk sometime was filled up only 5xxMB left (far less than 1GB) free room on a 2TB disk. Still working fine.
Of course, later I removed data and restored disk free room.

siliconbeaver said:

I’m NOT sure reason of the problem.

In my practice, “showing up as red in explorer” wouldn’t be a problem. My disk sometime was filled up only 5xxMB left (far less than 1GB) free room on a 2TB disk. Still working fine.
Of course, later I removed data and restored disk free room.

Click to expand...

This is what I had meant. I was using about 90% of the space on the pool. It was nearly, but not entirely full.

yes,

The "red" was seen often in my 2TB SATA disk.

here is my main PC




my NAS (NOT 24H2) sometimes much worse. as said, only 5xxMB left (far less than 1GB) free room on a 2TB SATA disk. Still working fine.

I did some powershelling, and though I'm a novice, I'm pretty sure I didn't break anything as I read what I run before I run...

In physical disk, I took out the drives that weren't relevant.
I tried to set virtualdisk IsManualAttach from false to true, and upon reboot (or perhaps if I refreshed the storage spaces UI), it said inaccessible due to user action. I changed it back, and now I'm where I started.
The drives are seen, but the pool isn't listed in disk man. If I try to remove the one drive from the pool (I added this as it was logically the only thing the UI would let me do), it gives the pictured error

Considering I'm getting the exact same errors on this version of win11 as I am on 10, I'm thinking more this may be an issue with storage spaces unrelated to the windows version.

If anything, my goal is to get read access to these so I can put them in my cloud store and finally move to a proper nas os... I did not expect that just turning on the darn computer with all the drives detached would break it all...

Well, as someone who's been burnt looking up problems only to see someone had the same problem a decade ago and they just said 'fixed' without any solution, I'm not going to pass that feeling along.

I found on a microsoft forum from a bunch of years back describing a similar problem, and they had made a note about a software called ReclaiMe.

One license later and I'm up and recovering. All my data is there, nothing is damaged. I guess Windows didn't know what to do with the storage space after it discovered that the drives were plugged in to different sata ports

Just a slow process to copy everything into a mirrored volume before I upload it to the cloud before I ditch Microsoft for software raid. This is the second time that I encountered the same problem. Thankfully I didn't lose anything last time, and I was able to recover everything the second time.