Windows 10: Storage spaces - My OS drive failed.

I have a small PC with 3 hard drives, 1 is the OS drive and the other 2 are in a drive pool using Storage Spaces.

Now my OS drive has failed and my Macrium backup files are in the Drive Pool. I have a new drive for my OS.

What is my best course of action? *cry

:)

 

Storage Space

Hi,

My question is the storage space so let's assume I have created a storage space on my computer, but my computer failed and I need it to run it urgently. Can I migrate these storage space hard disk to other computer and let it perform like normal?

Thank You

 

Cannot remove a "Retired" drive in Windows 10 Storage Spaces

After spending a few more hours on YouTube looking at everything about Storage Spaces, I found one video where a guy shows how to use the Powershell commands to "retire" a specific drive in the Storage Space pool of drives. This essentially tells Storage
Spaces to reallocate the data on the selected drive and prepare it for removal. The reallocation works on Parity and 2 and 3 way mirror volumes, but NOT for Simple volumes, which he added in his comments section. Since I no longer use Simple volumes in my
Storage Spaces pool, the "retire" Powershell command would do everything else I wanted in my proposed "vacate drive" command. I can live with the Powershell retire command until the Storage Spaces GUI adds a method to retire a drive.

BTW, I talked to a few other local computer guys who tried Storage Spaces on their systems. Both said that they had used Simple volumes as part of their pool, and everything was great until it wasn't. Both reported that they lost ALL their data in their
Simple volumes when one drive failed. Fortunately for me, my failed drive was still seen by my Storage Spaces and was automatically "retired." I was able to manually transfer all the data on the Simple volume to a Parity volume. If the drive had totally failed
and was no longer recognized by Storage Spaces, I guess I would also have lost everything!?

I was under the impression that if you had a Simple volume on a multi drive pool, and one drive failed, you would only lose data on that drive. What I think people are experiencing, is that the ENTIRE Simple volume, spanning multiple drives, will lose ALL
data when the Simple volume becomes inaccessible due to a drive failure (Storage Spaces no longer sees the failed drive at all).

At best, if you need faster read/write times than a Parity or Mirror volume on your server, then a Simple volume should only be considered as a limited TEMP file storage solution. For me, it's no longer worth it and if I need a simple backup of my data,
I'll just use a standalone USB HDD not associated with Storage Spaces.

 

Storage Spaces/Drive Pool makes independently checking each of the data hard-drives impossible? Quick-read via Google has me believing the software needed to view data folders & files resided on the now-defunct OS hard-drive, is that correct? And, there was no way to make a WinPE-like Storage Spaces/Drive Pool & Macrium Reflect usb boot stick or DVD boot, correct? Or, was there a way originally and such boot was not made?

 

I could find no easy way to get my backup file off of my Storage Spaces drives. I just connected the new hard drive and did a fresh Win 10 install.

Windows then immediately picked up my Storage Spaces drives and I could copy my Macrium backup file from it. Then used Macrium to restore to the new drive and I am now back up and running. *Biggrin

I just wish there was an easier way to get files off of Storage Spaces drives.