{"id":14788,"date":"2020-06-17T05:36:58","date_gmt":"2020-06-17T03:36:58","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=14788"},"modified":"2020-09-28T07:28:59","modified_gmt":"2020-09-28T05:28:59","slug":"windows-10-2004-storage-spaces-issues","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/06\/17\/windows-10-2004-storage-spaces-issues\/","title":{"rendered":"Windows 10 2004: Storage Spaces issues"},"content":{"rendered":"

[German<\/a>]The recently released Windows 10 May 2020 Update (version 2004) contains many bugs. Administrators in enterprise environments that rely on storage spaces should wait with the upgrade. There are issues with storage spaces. I've put together a few things for your information.<\/p>\n

<\/p>\n

What is Storage Spaces?<\/h2>\n

\"\"Storage Spaces is a technology introduced by Microsoft for Windows clients and Windows servers to protect data from drive errors. The technology is conceptually similar to RAID, but is implemented by software. Users can use storage space to group two or more drives into a storage pool and then use the capacity from that pool to create storage. Multitier caching of HDDs (if necessary of different manufacturers \/ speeds) by means of SSDs is also possible. These usually store additional copies of the data. If a drive from this group fails, Windows can still access an intact copy of the data.<\/p>\n

When the capacity of a storage space is exhausted, administrators can simply add more drives to the storage pool. Microsoft has described this in this document for Windows Server<\/a>. And the Wikipedia provides a description of the function for Windows 8 here<\/a>..<\/p>\n

Error 0x00000057\u00a0 known for months<\/h2>\n

One issue that has been bothering administrators for months is the 0x00000057 error when creating new storage space storage pools. On Microsoft Answers you can find this thread<\/a> from September 2019, which deals with the Storage Spaces Error 0x00000057. There are also several entries in the Microsoft Feedback Hub (see for example aka.ms\/AA7jko4).<\/p>\n

\"Storage<\/p>\n

Users will not be able to create new storage spaces pool or volumes. The post referred to a Windows 10 Insider Preview Build 18951.1 (the development branch that culminated in Windows 10 version 2004). Jason from Microsoft has also talked to the responsible developers – but when browsing through the 3 pages, little came up. A moderator, Don Culbert, responded<\/a> with a post naming PowerShell commands that could be used to create the required operation. There was no real resolution. Now I read at Windows Latest<\/a>,\u00a0 that the Storage Spaces Error 0x00000057 is still an issue – the management interface is probably pretty broken.<\/p>\n

Probable reason: Powershell does not know the new version level for pools. In Powershell only the creation of a pool in Version-Level Server 2019 is possible. The upgrade of the Pool Function Level can \/ must be done subsequently. It looks like I'm trying to create the GUI pools on the new level. This is a speculation why it still only works via Powershell, but not via GUI. German blog reader Karl mentioned it in this tweet<\/a>. This was first reported in the Feedback Hub 8 months ago.<\/p>\n

Windows 10 Version 2004 destroys parity storage<\/h2>\n

On reddit.com there is this post<\/a>, where a user points out another problem. In Windows 10 version 2004, there are probably memory errors with storage spaces:<\/p>\n

Do not upgrade to 2004 if you're using parity storage spaces.<\/p>\n

Ever since updating to 2004 I have been experiencing severe corruption & chkdsk errors on my parity drives (and only parity) in storage spaces. (See any of my recent post history) I managed to reproduce the corruption on a new pool, with a new set of disks, with a new set of SATA controllers, but I've been assuming I must have some other kind of hardware failure instead.<\/p><\/blockquote>\n

In this Reddit post<\/a>, the affected person received confirmation that another user had the same experience after upgrading to Windows 10 version 2004. MSPU has collected a lot more here<\/a>.<\/p>\n

Deleting doesn't free any storage space<\/h2>\n

And there is another hammer with storage spaces, that affects all Windows 10 builds down to version 1903. I've had this topic on my agenda since spring, but I haven't gotten around to editing it here on the blog yet. If files are deleted in a storage space storage pool, this should cause the occupied storage to shrink again. Karl noticed that the volume formatted on a ReFS with mirroring (Mirror aka RAID 1) is not the case. He already mentioned the whole thing on Twitter in January 2020.<\/p>\n

\n

I think I have found something critical in #20H1<\/a>, sorry.
\nStorage Spaces will not free up space (thin prov).
\nDrives are reportingly full even if I delete GB of data from @windowsserver<\/a> might also affect 20H1 Srv SAC@JenMsft<\/a> @NorthFaceHiker<\/a>
\ndetails: https:\/\/t.co\/3pgXR9yloj<\/a><\/p>\n

\u2014 al Qamar (Karl Wester-Ebbinghaus) (@tweet_alqamar) January 11, 2020<\/a><\/p><\/blockquote>\n