1.    29 Apr 2016 #1

    Preview build causes errors in storage spaces on multiboot system


    DIY desktop computer used as test box. Both production (build 10586) and development (build 14322) installed.

    I use storage spaces (two 1TB drives pooled in two-way mirror, ReFS formatted) with build 10586 for backups and archives.

    Whenever I restart into build 14332 the storage spaces drives show constant disk activity and Storage Spaces does not appear in the This PC window in build 14332. When I return to build 10586 I again have a lengthy period of disk activity once more. However the Storage Spaces does appear in the This PC window in build 10586 as expected and I can access the space just fine. I get messages that Storage Spaces needs attention and when I access the Storage Spaces window via the Control Panel the drive statuses show that repair is under way. After a few minutes the drive statuses change to OK. However, the status bar at the top of the Storage Spaces area remains orange and I have a warning message. This status persists over restarts of build 10586.




    Question 1: Since the physical drives section shows that the devices are OK, where can I check further for the exact problem?

    Question 2: How can I clear the warning message if in fact ReFS has fixed itself?

    Question 3: Is there a method to preventing this the next time I boot into a preview build short of turning off or physically disconnecting the pooled drives?

    I have posted feedback, although I mistakenly left the type as "suggestion."

    Here is the disk management panel (build 10586):



    The storage spaces volume does not show up in the preview (build 14332).

    I would like to clear the warning message circled in the first screen shot above and would like not to have to disconnect the drives before accessing the preview. Thoughts?

    (also posted in Windows 10 Insider forum)
      My System SpecsSystem Spec


  2. Joined : Dec 2013
    Portsmouth Hampshire
    Posts : 1,197
    Windows 10 x86 14383 Insider Pro and Core 10240
       30 Apr 2016 #2

    The thing that springs out at me is that the pooled storage is attached by ATA for the WD, and by USB for the ST.

    There will be differences in speed and protocols in getting the data synced over both drives.

    They would surely be better if both were attached directly by SATA using a single protocol?
      My System SpecsSystem Spec

  3.    30 Apr 2016 #3

    Fafhrd said: View Post
    The thing that springs out at me is that the pooled storage is attached by ATA for the WD, and by USB for the ST.

    There will be differences in speed and protocols in getting the data synced over both drives.

    They would surely be better if both were attached directly by SATA using a single protocol?
    No such problem happens in build 10586 so Storage Spaces is working fine until the preview gets involved. The preview should handle Storage Spaces the same as the production branch just like it should any other feature of Windows 10. Obviously there is a bug. This is expected in previews. Even so, it is a test box and not my primary computer. Fortunately I am using ReFS for the pool and not NTFS or I might have lost my backups. ReFS simply fixed the corruptions as soon as I was back to build 10586 without the need of running chkdsk, etc.

    I don't intend to expose the pool to the preview again now that I know there is a bug affecting it, but I want to get rid of the circled message now that I am back on the production branch.

    Just so you know, Storage Spaces is specifically designed to leverage disparate connections, device characteristics, etc. It is typical to use JBOD (Just a Bunch Of Disks) like I am using. It is common to mix SSDs and HDDs in the same pool. Storage Spaces specifically supports mixing USB, eSATA, SAS, etc. in the same storage pool.

    But thanks. I am glad someone is visualizing a potential answer.
    Last edited by Cbarnhorst; 30 Apr 2016 at 11:47.
      My System SpecsSystem Spec

  4.    11 May 2016 #4

    Fafhrd said: View Post
    The thing that springs out at me is that the pooled storage is attached by ATA for the WD, and by USB for the ST.

    There will be differences in speed and protocols in getting the data synced over both drives.

    They would surely be better if both were attached directly by SATA using a single protocol?
    As it turns out, the eSATA connection was not seen as ATA by the preview. It should have been, but it was seen as RAID instead. That's a bug and I reported it via the Feedback Hub. I switched out HDD enclosures to remove the eSATA enclosure and replaced it with a USB 3.0 enclosure. That solved the issues in the preview and removed the trouble report on the build 10586 side as well. The issue with RAID is that RAID is not compatible with Storage Spaces and the false detection set off the chain of events. Here is a screenshot of the problem before switching enclosures.

    Click image for larger version. 

Name:	storage space connection error.PNG 
Views:	1 
Size:	70.1 KB 
ID:	79308

    In build 10586 the eSATA drive was identified correctly as ATA. In build 14342 it was misidentified as RAID. It is fine to mix ATA and USB, but all RAID must be disabled before pooling a device and creating a storage space. Hence the craziness.
      My System SpecsSystem Spec


  5. Joined : Nov 2013
    Toronto
    Posts : 4,289
    Win 10 Pro x64
       12 May 2016 #5

    I was just about to say that if your drives are mirrored, it must be some sort of drive detection issues on the preview build. And it was. Good thing you sorted it out.
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
Solved Storage Spaces issues adding drive
I have a 4x 2TB drive storage pool setup with storage spaces under parity mostly used for movies/tv shows. I decided to buy 2 more 4TB drives and add them, but I only have space for 1 more at the moment (only 6 SATA connectors on my MB). After...
Drivers and Hardware
Are nested storage spaces possible? (Like RAID 0+1)
I recently had a 3TB hard drive fail on me, and I am trying to come up with a much better solution for storing my data so that I don't have to recover everything from CrashPlan again. My plan is to have two 3TB Hard drives connected in RAID 0...
Drivers and Hardware
Windows 10 to 8.1 back to 10 now missing storage spaces
Hi All, 1.So I had windows 8.1 with storages spaces working fine 2.removed my windows 8.1 HD and put in a new HD installing windows 10 3.On windows 10 storage spaces is great and working fine 4. I noticed that I forgot to back up something on...
Drivers and Hardware
Error using storage spaces/mirror
I upgraded from W8.1 to W10. After the upgrade my mirrored volume was 'gone' (created with disk management). Fortunately I was able to restore the data on one of the disks. I cannot manage to recreate a mirror on Windows 10. I tried using disk...
Drivers and Hardware
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 15:32.
Find Us
Twitter Facebook Google+



Windows 10 Forums