Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, March 26, 2017 12:57 AM
I swapped motherboards and my storage space was listed there (Some disks offline) didn't try and use it.
Did a reset of windows (That didn't reset anything).
Rebooted into windows no storage space listed in the ui or Get-VirtualDisk.
All drives listed in device manager but not disk manager. Get-PhysicalDisk yields:
FriendlyName SerialNumber CanPool OperationalStatus HealthStatus Usage Size
WDC WD30EZRX-00DC0B0 W -DCW1C0T180355 False Starting Unknown Unknown 2.73 TB
ST3000DM001-1CH166 W1F4425B False Starting Unknown Unknown 2.73 TB
WDC WD30EZRX-00DC0B0 WD-WCC1T0815338 False Starting Unknown Unknown 2.73 TB
WDC WD30EZRX-00MMMB0 WD-WCAWZ0808067 False Starting Unknown Unknown 2.73 TB
ST3000DM001-1ER166 Z5005NAB False Starting Unknown Unknown 2.73 TB
WDC WD30EZRX-00DC0B0 WD-WCC1T0875478 False Starting Unknown Unknown 2.73 TB
ST3000DM001-1CH166 W1F42DE9 False Starting Unknown Unknown 2.73 TB
WDC WD30EZRX-00DC0B0 WD-WCC1T0764305 False Starting Unknown Unknown 2.73 TB
WDC WD30EZRX-00DC0B0 WD-WCC1T0875885 False Starting Unknown Unknown 2.73 TB
SAMSUNG MZVLV128HCGR-00000 0000_0000_0000_0000. False OK Healthy Auto-Select 119.24 GB
All the member disks are stuck in a "Starting" state. I used ReclaiMe Storage Spaces Recovery and it sees 3? good spaces with varying sizes.
Is there anything I can do to recover the space without building a new array and copying over the data with ReclaiMe?
Jesse Foltz
All replies (14)
Monday, March 27, 2017 6:35 AM
Hi Jesse Foltz,
I'm afraid you may need to retire the disk. And replace the bad disks.
Please refer to the thread discussed before for more details
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, March 27, 2017 8:39 AM
Which disk all 9 are in the starting state. I don't think any of the drives are hot spares. I am able to pull any data off the drives with ReclaiMe. I'm backing up all the data now. I don't see any virtual disk listed and all the drives are stuck in "starting" status.
Is there a better way to see what the error might be?
Jesse Foltz
Tuesday, March 28, 2017 8:18 AM
Hi,
Thanks for your feedback.
Based on my knowledge, with the build-in feature, could only check about the event viewer or run the Get-PhysicalDisk to identify the disk status. For the current scenario, there seems to be something wrong with the disk. If you need to do further check for the disks, you may consult the disk vendors.
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, August 17, 2017 10:19 PM | 1 vote
Did you ever get this resolved without data loss? I think I'm seeing the same issue for the very first time ever. Thx, much obliged.
Sunday, April 15, 2018 9:19 AM
I had the same issue.
My "mistake" was, to
- have a dual boot "playaround" System with Windows 10 Insider Preview and Windows Server 2016 and
- boot Windows 10....
After rebooting into Windows Server 2016, physical disks are only in device Manager. The physical disks were not shown up in Server Manager or disk Management.
With powershell get-physicaldisk all missings disks were in Operational Status "Starting".
My "solution" was to Inplace Update the Windows 2016 Server to the Windows Server 2019 LTSC Preview from Spring 2018.
Now Server can read them again, Storage Pool is back again and the vdisks just needed to be brought online from offline mode.
It Looks like, Windows 10 wrote something onto the physical disks, that was not covered from Server 2016.
So this error is very rare because nobody would do such things in production. :)
Saturday, October 19, 2019 11:02 AM
Hi Peter
I managed to replicate the error, by restoring WSE2016 system drive using WIN10 bootable usb.
As I needed only to get to boot trouble-shooter and select system backup from external drive.
To my surprise, storage spaces pool was gone and all the drives are in starting mode.
I will try to in place update server to WS2019 and then restore back to WSE2016.
if this is the last solution, I will try it. Honestly I ran out of options. I have no means of getting the data back
Thursday, November 7, 2019 9:52 PM
Hi zulu at al,
All my storage spaces drives are in starting as well and I am stuck in the same sort of situation.
Frankly, I am quite disappointed that no one from Microsoft has stepped up to help out with these issues, as storage spaces and ReFS is promoted as being a safe choice for storing important data.
I am currently short somewhere around 3.5 TBs worth of files, which are on a pool of disks stuck in starting.
All of the recovery suites available including ReclaiME has failed, but I haven't given up on my stuff yet.
You will hear from me if I find a way, currently I am hoping for the 1909 as a potential saviour.
Cheers
Monday, March 23, 2020 7:34 PM | 1 vote
I've got the same problem. Last night I removed an older 2TB HDD from my StoragePool and everything seemed to be OK. Then I added a new 6TB HDD to the pool, SS recognized the HDD as available to add, attempted to add new 6TB HDD, and got an error code stating that HDD had failed. Evidently the new 6TB HDD was DOA.
Unfortunately, Stoarge Spaces no longer sees the StoragePool on my other HDDs. Get-PhysicalDisk reports all disks are still there but Operational Status is (Starting, OK). Get-StoragePool only lists the Primodridal as OK, Healthy, IsReadOnly (False), and size of 19.1 TB. So, it looks to me that the data is still all there, just for some reason Storage Spaces is no longer seeing the StoragePool on the drives. Get-VirtualDisk returns nothing, but there were 3 Mirrored Virtual Disks in the StoragePool before I lost it.
Windows10 GUI for Storage Spaces starts up in Create a New StoragePool screen, but even then returns no disks available. Would like to restore my data if possible. Any help appreciated.
Monday, March 23, 2020 7:37 PM | 1 vote
I wonder how we get Microsoft to address this problem.
It does seem like it is impacting a lot of people as this is far from the only discussion about it.
FYI, my upgrade to 1909 did not solve the issue and I have also tried installing Windows Server - both 2016 and 2019 - no luck :-(
Monday, March 23, 2020 9:55 PM | 2 votes
I wonder how we get Microsoft to address this problem.
It does seem like it is impacting a lot of people as this is far from the only discussion about it.
FYI, my upgrade to 1909 did not solve the issue and I have also tried installing Windows Server - both 2016 and 2019 - no luck :-(
This has been my 3rd time with catastrophic failures of Storage Spaces over the past 7 years (since Windows 8). I really like Storage Spaces - when it works - but have found that when it fails I have lost all my data despite having 2-way or 3-way redundancy. All my other failures where reported to MS support and these forums, but I guess they all fall into the category of never to be fixed by MS. It's really too bad as I had hoped Storage Spaces by MS would be a more robust system with continual improvements. Instead, I have had continual failures with problems that others have also reported but never fixed.
I lost confidence in Storage Spaces after my 1st catastrophic failure (1 HDD failure in a pool of 28 HDDs and everything was lost!). So I really reduced my usage of Storage Spaces in my second attempt. Again, I had a single HDD failure and everything, again, was lost despite having 2-way and 3-way mirroring. So, my third attempt I had even less data and less HDDs in the Storage Pool, but again I managed to lose everything. All my data was backed up elsewhere, so I will move on. But it's the unexplained failures of Storage Spaces and the time spent having to rebuild the Storage Pools that are just getting too much for me to deal with. Maybe it's 3 strikes and I'm out.
I am now looking at other Drive Pooling options such as Drive Bender or Drive Pool. I don't know if they will be any better for me, but at least if one drive fails you can still access all the data on the other HDDs because they just use the NTFS files system and the drive can be read on any computer. Unfortunately, Storage Spaces HDDs only work in Storage Spaces and if the Storage Pool is broken, the HDD is unreadable. If anyone has any comments on Drive Bender or Drive Pool as an option instead of Storage Spaces, please let me know. Thanks.
Tuesday, March 24, 2020 6:39 AM
Try to boot one of the newest Windows 10 Insider Editions from USB on the same computer, if you are able to.
This could be your last hope.
Tuesday, March 24, 2020 5:02 PM
Try to boot one of the newest Windows 10 Insider Editions from USB on the same computer, if you are able to.
This could be your last hope.
Thanks, but after trying to restore the Storage Pool on another computer without any success, I decided to pull the plug on Storage Spaces and formatted all the HDDs in the pool. I have loaded up a trial version of Drive Bender, but, to be honest, so far I'm not too impressed. I might end up just using external USB HDDs and share them on the network and be done with all these Drive Pooling software solutions.
Again, I really like the promise of Storage Spaces and when it works it is great. However, after my 3rd catastrophic failure with Storage Spaces, I can say that when things go bad with Storage Spaces your data is pretty much guaranteed to be lost despite using 2-way or even 3-way mirrored Virtual Disks.
Monday, April 27, 2020 4:06 PM
I was running Win 10 Enterprise with a 4 disk parity space, when the boot disk (SSD) died. I replaced the SSD and reinstalled Windows.
Like others here, all 4 drives are now shown as "Starting" and do not appear anywhere else except the BIOS.
Has anyone figured out a way to recover? Do I need to install a Windows server version? What happens during "Starting" - what is going on in the background? Is it trying to read the disks and put the space back together?
Monday, April 27, 2020 5:36 PM
For some reason, I got an email to mark this problem as Solved so the issue can be closed. To be clear, I lost all my data and was never able to recover my Storage Spaces. None of the interventions I tried worked to recover my lost data. All this, despite having 2-way and 3-way mirrored disks.
After my third catastrophic failure and data loss with Storage Spaces, I have since moved on to Stablebit Drivepool. In my first 30 day evaluation period, I suffered a database corruption of the DrivePool after a Windows 10 update. I contacted DrivePool support and they sent me instructions that reset the database. All my data was still on the drives and DrivePool rebuilt the pool over night. DrivePool is not as fast, or as flashy as Storage Spaces, but it just works and if/when the DrivePool database gets corrupted, it can be rebuilt as the underlying data is still on the HDD as standard NTFS files.
Ditto on redundancy, as you can select target directories and determine how many DrivePool backup copies you want of those files. The backup copies of those files will be saved on other disks in the pool, so a loss of any pool HDD will not result in total loss of files duplicated on other drives. The Drivepool duplication process is not as fast as Storage Spaces, but IMHO, it's more reliable. For my home media server needs, DrivePool is fast enough.
In short, I have Solved my Storage Spaces problem by migrating to other software. I have chosen to give up on the promise of Storage Spaces for the DrivePool software that is not as fancy, not as fast, but just works and protects the data better.