Storage Spaces Direct Issue

Hi everyone.

I have an issue with Storage Space Direct (3 Nodes Cluster). I noticed by Virtual Disk was operational status “Degraded, InService” with a health status of warning. I also noticed Get-StoragePool has a job Suspended for a while.

PS C:\Windows\system32> Get-VirtualDisk

FriendlyName ResiliencySettingName OperationalStatus    HealthStatus IsManualAttach     Size

------------ --------------------- -----------------    ------------ --------------     ----

CSV-01      Mirror               {Degraded, InService} Warning      True          14.55 TB

PS C:\Windows\system32> Get-StorageJob

Name  IsBackgroundTask ElapsedTime JobState  PercentComplete BytesProcessed BytesTotal 

----  ---------------- ----------- --------  --------------- -------------- ---------- 

Repair False           27.20:25:44 Running   0                                         

Repair True            00:00:00    Suspended 0              0             273804165120

The rest look all fine. The Get-Physical Disk command return an Health Status of Healthy on all my disk. The Failover Cluster Manager look good. Yet, when looking at the event log, I have found this.

Log Name:      Microsoft-Windows-StorageSpaces-Driver/Operational

Source:       Microsoft-Windows-StorageSpaces-Driver

Date:         9/6/2017 7:03:34 PM

Event ID:     203

Task Category: None

Level:        Error

Keywords:     

User:         SYSTEM

Computer:     HyperV01

Description:

Physical disk {b42ee394-d7d2-4f18-2730-e52dfdd9782b} failed an IO operation. Return Code: The device is unresponsive.. Additional related events may be found in the System event log for Disk 5022.      

This disk may need to be replaced. To view its reliability counters, run this command in PowerShell:                 

Get-PhysicalDisk | ?{ $_.ObjectId -Match "{b42ee394-d7d2-4f18-2730-e52dfdd9782b}" } | Get-StorageReliabilityCounter                 

This disk may be located using the following information:                 

Drive Manufacturer: TOSHIBA                 

Drive Model Number: MG04SCA40EN                 

Drive Serial Number: 27B0A1EQFVNC                 

Strangely, most command show that disk were OK. But the commands result was slow. 

PS C:\Windows\system32> Get-PhysiCalDisk

FriendlyName        SerialNumber       CanPool OperationalStatus HealthStatus Usage           Size

------------        ------------       ------- ----------------- ------------ -----           ----

ATA INTEL SSDSC2BX20 BTHC649408CG200TGN False  OK               Healthy      Auto-Select 186.31 GB

ATA INTEL SSDSC2BX40 BTHC7033012Q400VGN False  OK               Healthy      Journal     372.5 GB

ATA INTEL SSDSC2BX40 BTHC703308JT400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27C0A1JEFVNC       False  OK               Healthy      Auto-Select  3.64 TB

TOSHIBA MG04SCA40EN 27C0A1JZFVNC       False  OK               Healthy      Auto-Select  3.64 TB

TOSHIBA MG04SCA40EN 27C0A1JDFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX20 BTHC649408L0200TGN False  OK               Healthy      Journal    186.25 GB

ATA INTEL SSDSC2BX40 BTHC7033012N400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27C0A1JWFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX40 BTHC703301TM400VGN False  OK               Healthy      Journal     372.5 GB

ATA INTEL SSDSC2BX40 BTHC703308JV400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27C0A1JMFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX40 BTHC7033011Z400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27B0A1EYFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX40 BTHC703308K2400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27B0A1CBFVNC       False  OK               Healthy      Auto-Select  3.64 TB

TOSHIBA MG04SCA40EN 27C0A1JCFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX40 BTHC7033012G400VGN False  OK                Healthy     Journal      372.5 GB

TOSHIBA MG04SCA40EN 27C0A1JJFVNC       False  OK               Healthy      Auto-Select  3.64 TB

TOSHIBA MG04SCA40EN 27B0A1EQFVNC       False  OK               Healthy      Retired      3.64 TB

TOSHIBA MG04SCA40EN 27C0A1JFFVNC       False  OK               Healthy      Auto-Select  3.64 TB

ATA INTEL SSDSC2BX40 BTHC703308FA400VGN False  OK               Healthy      Journal     372.5 GB

TOSHIBA MG04SCA40EN 27B0A1ETFVNC       False  OK                Healthy     Auto-Select   3.64 TB

ATA INTEL SSDSC2BX20 BTHC649408LE200TGN False  OK               Healthy      Journal    186.25 GB

ATA INTEL SSDSC2BX40 BTHC70330136400VGN False  OK               Healthy      Journal     372.5 GB

ATA INTEL SSDSC2BX40 BTHC7033012A400VGN False  OK               Healthy      Journal     372.5 GB

ATA INTEL SSDSC2BX20 BTHC649408WB200TGN False  OK               Healthy      Journal    186.25 GB

ATA INTEL SSDSC2BX40 BTHC7033012R400VGN False  OK               Healthy      Journal     372.5 GB

Then, I try to Enable Storage Maintenance Mode on the disk but it’s fail.

PS C:\Windows\system32> Get-PhysicalDisk -SerialNumber 27B0A1EQFVNC | Enable-StorageMaintenanceMode

Invoke-CimMethod : Currently unsafe to perform the operation

Extended information:

One or more virtual disks are not healthy.

Virtual Disks:

4DABF2FD1F351643B3435CDA4962346C

Recommended Actions:

- Repair associated virtual disks that have lost their redundancy.

- To continue with the operation do not use the 'VirtualDisksHealthy' flag.

The associated virtual disks may be at a greater risk of becoming unavailable.

Activity ID: {c8a15747-46f3-4bfb-b97f-69d173bc1c2c}

At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Storage\StorageScripts.psm1:3904 char:17

+ ...            Invoke-CimMethod -MethodName "Maintenance" -Arguments $ar ...

+                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   + CategoryInfo         : NotSpecified: (StorageWMI:) [Invoke-CimMethod], CimException

   + FullyQualifiedErrorId : StorageWMI 9,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand

I then try a repair function on the Virtual Disk but it fails because of this.

PS C:\Windows\system32> Get-VirtualDisk | Where-Object -FilterScript {$_.HealthStatus -Eq "Warning"} | Repair-VirtualDisk

Repair-VirtualDisk : Not enough available capacity

Please note that I only have 1 volume on this cluster create using the “New-Volume -StoragePoolFriendlyName "S2D*" -FriendlyName CSV-01 -FileSystem CSVFS_ReFS -UseMaximumSize” command.

Then, I have decided to get the disk and retired it with this command.

$Data = Get-PhysicalDisk -SerialNumber 27B0A1EQFVNC

Set-PhysicalDisk -InputObject $Data -Usage Retired

Once the disk was retired, I have stop receiving the error in the Microsoft-Windows-StorageSpaces-Driver Event Log. Then, I try resetting the disk with this command.

Reset-PhysicalDisk -InputObject $Data

It seems the disk was added in the pool and I don’t have new error in the Microsoft-Windows-StorageSpaces-Driver Event Log. But I still have a Repair StorageJob suspended my Virtual Disk is still Degraded.

PS C:\Windows\system32> Get-StorageJob

Name  IsBackgroundTask ElapsedTime JobState  PercentComplete BytesProcessed BytesTotal  

----  ---------------- ----------- --------  --------------- -------------- ----------  

Repair True            01:54:22    Suspended 0              0             3998614552576

PS C:\Windows\system32> Get-VirtualDisk

FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach    Size

------------ --------------------- ----------------- ------------ --------------    ----

CSV-01      Mirror               Degraded          Warning      True          14.55 TB

Strangely, at first, it was “Degraded, InService” and now, it only shows “Degraded”. The “InService” portion is not show any more but my VM running on top of Virtual Disk are still running fine.

P.S. The Virtual Disk is own by Node 1 but the problematic disk is on Node 2. Node 3 is healthy.

I’m very confused by all this. My Virtual Disk is only using 13.3 TB on the 14.55 TB. I know in the pass, I had issue when I patch the server where the disk wouldn’t sync after a reboot. If I remember correctly, I had to repair de Virtual Disk with this command “Get-VirtualDisk | Where-Object -FilterScript {$_.HealthStatus -Eq "Warning"} | Repair-VirtualDisk” but this time, it doesn’t work. I also try the “Get-StoragePool<storage pool friendly name> | Optimize-StoragePool” and it didn’t help either.

I could have a bad disk but I would find it strange only the EventLog would show that to me and not PowerShell.

Anyone have any suggestion for me? At some point, I wanted to reboot Node2 but I couldn’t gracefully put in maintenance mode because my Virtual Disk was not healthy. The 3 idea I have at this moment.

1. Put the disk was as Retired and leave it Retired for a while.
2. Forcedly reboot node 2.
3. Change the disk.

Anyone have more idea?

P.S. Sorry for any grammatical error. It late for me now.

Hello Community,

I have faced interesting issue (or not a issue). I have dell R540 with 4 SSD drives (Samsung SM863A) and 3 HDD (Seagate 2 TB NLSAS) which is controlled by HBA H330. I want to build tiered Storage Spaces. Recently I have tested Windows 2016 and everything worked as expected (all incoming data were written to hot tier). Then, I installed Windows 2019 for testing. Absolutely the same config (in both hardware and Storage Spaces config). During the benchmarking I've found that all incoming data were written directly to cold tier. I am also found that if I am using ReFS instead NTFS in WS 2019, the all incoming data written to hot tier. So, the issue is how tiered Storage Spaces works with NTFS.

Does someone know what was changed in Storage Spaces 2019 in comparison with SS 2016?

Can we set one work folders to use both windows authentication from joined domain client on internal network and ADFS for mobile client from external network?

We want to retain currently working windows authentication for client on internal network. We have also configured ADFS and ADFS Proxy servers but Android Work Folder client still cannot connect to Work Folder. Can we deprecate ADFS and ADFS Proxy, so that Android Work Folder client can authenticate using windows authentication via Web Application Proxy?

I'm running Windows 2008 server enterprise r2 and I got hit by a nasty virus that modified a bunch of my services and its dependencies.  Since then I'm having a problem getting the workstation service to start.  When I try to start it, it reports:

Error 2: The system cannot find the file specified.

I confirmed c:\windows\system32\svchost.exe & wkssvc.dll exist and have the proper dates (they match another 2008 install I have).

For DependOnService I have:

Browser, MRxSmb10, MRxSmb20, NSI

Any suggestions?

Hi All:

I use Windows Server 2016 Datacenter

This is my step:

1. Create a new VirtualDisk disk on storage pool (partiy,thin)

New-VirtualDisk -StoragePoolFriendlyName pool -FriendlyName vdisk -ResiliencySettingName Parity -Size 10GB -ProvisioningType Thin -WriteCacheSize 1GB

It works.

2. Extend the new VirtualDisk to 11GB

Resize-VirtualDisk -FriendlyName vdisk2 -Size 11GB

It works.

3.  Then, I want to shrink the virtual disk.

Resize-VirtualDisk -FriendlyName vdisk2 -Size 10GB

But it doesn't work

Resize-VirtualDisk : Not Supported

Extended information:
The Windows Storage Provider does not support shrinking virtual disks.

Activity ID: {a951cc0d-3f7c-4abd-983f-e9757c79c2f5}
所在位置 行:1 字符: 1
+ Resize-VirtualDisk -FriendlyName vdisk2 -Size 9GB+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : InvalidOperation: (StorageWMI:ROOT/Microsoft/...SFT_VirtualDisk) [Resize-VirtualDisk]，Ci
    mException
    + FullyQualifiedErrorId : StorageWMI 1,Resize-VirtualDisk

PS C:\Users\Administrator> Resize-VirtualDisk

I also try for Resiliency with [Mirror/Simple]， it doesn't work too. : - (

I think it is the defect of Windows Storage Space.  Iextend and do nothing, then I want to shrink to the origin size. Why can't do this?

Hi guys,

I have 2-Node S2D Failover Cluster built on Dell PowerEdge R720xd.

The operating system on both nodes is Windwos Server 2016 Datacenter.

I configured and run CAU but hardly one of the nodes was restarted I got this. 



CAU itself seems runs fine. 

I'm just wondering if CAU or any other way of patching works with 2-Node S2D failover Cluster or no matter how it is done it affects storage. 

Regards,

Hello,

Hoping someone may be experiencing the same issues that we have at one of our customers sites.

We have implemented a 2 node Server 2019 S2D (Azure HCI Stack) solution, the hardware was purchased from Dell and is completely HCI compliant (the nodes we have on the bezels "Storage Ready Nodes", however, I believe its now called Azure HCI Stack).

This is a 2 node ROBO installation, 2 x 25GB adapters for storage networking, back to back (no switches). The VM network and management are in a SET team using 2 x 10GB adapters (going through 10GB switches).

We have implemented these as per the Dell HCI best practice guide;

https://www.dell.com/support/manuals/uk/en/ukbsdt1/microsoft-storage-ready-node-r740xd/robos2dreadynodedg/notes-cautions-and-warnings?guid=guid-5b8de7b7-879f-45a4-88e0-732155904029&lang=en-us

We are seeing no issues in stability at all, the solution is functioning and generally speaking we and the customer are very happy with it.

Of course there is a BUT...

We are finding that certain guest OS's (namely Server 2008 R2) are performing badly on throughput testing (using iPERF). The general performance of the 2008 R2 VMs is great. Booting/Shutting down and running tasks (SQL, Exchange) on them perform brilliantly. Its when clients (Windows 7) or other guest VMs (on the other node to it) try to copy data its very slow.

I have run lots of iPERF tests and I will list them below;

*** S2D Troubleshooting ***

Node Owner for S2D disk makes no difference to performance, either node can be owner and I get the same results.
Any VM on same node (Doesn't matter what Guest OS) - No Issues (Masking the problem) - Using local BUS.

VM to VM (Servers)

Server 2008 R2 writing to Server 2008 R2 different node - 166MBit/s
Server 2008 R2 writing to Server 2019 different node - 2.65GBit/s
Server 2019 writing to Server 2008 R2 different node - 638MBit/s
Server 2019 writing to Server 2019 different node - 3.23GBit/s

Client to Servers

Windows 7 writing to Server 2008 R2 (any node) - 232MBit/s
Windows 7 writing to Server 2012 R2 (any node) - 175MBit/s
Windows 7 writing to Server 2019 (any node) - 1GBit/s

Servers to Client

Server 2008 R2 (any node) writing to Windows 7 - 820MBit/s
Server 2012 R2 (any node) writing to Windows 7 - 800MBit/s
Server 2019 (any node) writing to Windows 7 - 832MBit/s

All Guest Integration Tools are up to date, I have tried previous versions also.

As you can see its an issues with the older OS's, we are planning on removing these (upgrading or building new) soon. I am wondering if we are the only ones seeing this particular issue? I also have a case open with Dell and they are looking into it.

If it makes any difference this was a migration from VMware to Hyper-V 2019 S2D, VMware Tools removed and the VM disks we converted and VM guests created from scratch. No legacy network cards on any VM.

Disabling VMQ makes no difference, same with any TCP offload, this issue seems tied to the guest OS and its driving me mad!

Any thoughts would be very welcome!

I'm configuring all the user's profile in AD and having it point to a file server on the network.

What are best practices as far as the folder structure?

\\servername\share$\userprofile 

or

\\servername\share$\users\userprofile

What am getting at is there an advantage to adding another folder like "users" in the second example or can the profiles start at the root of the share like in example 1?

What does Microsoft recommend?

Hello,

we are using a server 2012R2 file server and i enabled the file server resource manager. I created a quota template (soft) and added the quota template to a directory and subfolders.

In the template i enabled the "send reports" if 95% and 100% of the quota is reached. The quota is set to 1GB

In the FSRM Opitons i set the "notification limits" to 5 minutes.

Now i copy i file (950MB) to a folder (where the quota is enabled). I reached the 95% and i get an mail that i reached 95% but not report is attached. i copied a second file to the same folder with 20 MB - so 970MB is used on this quota but i didnt recive a second mail.

If i copy a third file (50MB) to the folder i reached the 1GB quota and i get the mail that i reached 100% of the quota. But the same problem here - i didnt recive any further mails. I thought if i set the "notification limit" to 5 minutes i will get the mails every 5 minutes.

Did i misunderstand something or is my configuration wrong?

It would be great if someone can help me.

Greeting

I have two Windows 2016 NAS servers running DFS replication. I need to apply Windows patches to each server. I have experienced corruption of the database journal in the past either due to a previous Windows patching or a reboot of one of the NAS servers for another issue. What is the best practice for patching the servers. Do I stop the DFS service, other services, etc? 

Thanks, 

Milty 

milty60

Hello,

I am migrating Active Directory domain. We have and old.com and new.com. Apparently, Users are already created on new.com. I want to migrate Old Sid history to new domain. fetched users SID from source and on destination tried putting it manually. so it gave insufficient rights error.  Found lots of scripts which talks to delete SID history with power shell. Can anyone please help me with power shell script/method/command to add SID history.

Thanks.

Sayyed Imran

Hi.

Is possible to change ClusterFaultDomain(in windows 2019) after create cluster. ?

Because i fount information that it's recommend to create that fault domains (chassis, rack, site etc. ) before creation s2d cluster.  And create s2d cluster creator ask me if i want user that fault domains. But what if i have already operational cluster and i want to change ClusterFaultDomain from node to rack ?

Hi all

I have another question, I have a folder with 32TB in files (.jpg .png, etc), in another server i want to replicate the folder using DFSR.

The traffic between both servers is a Vlan with a dedicated MPLS 1GB.

I think that the best scenario to create the Replica is:

-First create the Folder in server 2
-Copy all files from Server 1 to Server 2 using Robocopy (with all specific parameters, /MT, /Copyall, etc)
-And then, create the DFSR between both servers with all files in both folders, just for keep the replication)

In your opinion, is better to use Robocopy for the initial replication or is the same if I configure DFS between both folders and make initial the copy using DFS)

I was checked a lot of Microsoft and forums documentations, but I want to read your opinions and experience.

hi

can someone help me out from one issue facing in my server
my server Disk Space Usage of goes to 100% automatically even i deleted about 10 gb but again came to 0 bites available

i think  i have a malware  in system  who hit again n again and using spac

can you plz suggest some disk clean tool or any malware removable tool so that i can fix (i think)

if  i wrong plz suggest something in big trouble

I have a file server with a share, Standard$. I have my users in an OU that has full share rights. In this share I have about 25 departmental folders, each with a lot of subfolders. We have been having users deleting departmental folders a bit more than I like. I want to setup these dept. folders so users cannot delete them, but I still want them to have modify rights on the subfolders. I was thinking of giving my users OU traverse folder, list folder, read, read ext., and read permissions.  And then on the each subfolder give that OU group modify rights.  Does this sound like the best way?

Hello, Im getting some strange results for Msft_Volume query

Get-WmiObject -Query "SELECT * FROM Msft_Volume"  -Namespace Root/Microsoft/Windows/Storage

I see 'D' drive six times! I there any explanation and which one is real?

__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{0074c0a4-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{0074c0a4-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : DATA
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{0074c0a4-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{0074c0a4-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 48756031488
UniqueId             : \\?\Volume{0074c0a4-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12


__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{2d4b4fad-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{2d4b4fad-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : DATA
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{2d4b4fad-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{2d4b4fad-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 128554635264
UniqueId             : \\?\Volume{2d4b4fad-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12


__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{4491b922-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{4491b922-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : DATA
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{4491b922-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{4491b922-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 50788323328
UniqueId             : \\?\Volume{4491b922-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12

__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{95162798-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{95162798-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : DATA
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{95162798-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{95162798-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 160064081920
UniqueId             : \\?\Volume{95162798-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12

__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{d2744786-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{d2744786-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : New Volume
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{d2744786-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{d2744786-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 139896598528
UniqueId             : \\?\Volume{d2744786-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12

__GENUS              : 2
__CLASS              : MSFT_Volume
__SUPERCLASS         : MSFT_StorageObject
__DYNASTY            : MSFT_StorageObject
__RELPATH            : MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{e77f52c6-0000-0000-0000-100000000000}\\\""
__PROPERTY_COUNT     : 18
__DERIVATION         : {MSFT_StorageObject}
__SERVER             : DELL590HV12
__NAMESPACE          : Root\Microsoft\Windows\Storage
__PATH               : \\DELL590HV12\Root\Microsoft\Windows\Storage:MSFT_Volume.ObjectId="{1}\\\\DELLCSPRHV02\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Volume.ObjectId=\"{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\\\?\\Volume{e77f52c6-0000-0000-0000-1000000
                       00000}\\\""
AllocationUnitSize   : 4096
DedupMode            : 4
DriveLetter          : D
DriveType            : 3
FileSystem           : NTFS
FileSystemLabel      : DATA
FileSystemType       : 14
HealthStatus         : 0
ObjectId             : {1}\\DELLCSPRHV02\root/Microsoft/Windows/Storage/Providers_v2\WSP_Volume.ObjectId="{60fd5c97-6507-4543-99f1-daf47227f21e}:VO:\\?\Volume{e77f52c6-0000-0000-0000-100000000000}\"
OperationalStatus    : {2}
PassThroughClass     :
PassThroughIds       :
PassThroughNamespace :
PassThroughServer    :
Path                 : \\?\Volume{e77f52c6-0000-0000-0000-100000000000}\
Size                 : 162522984448
SizeRemaining        : 46635180032
UniqueId             : \\?\Volume{e77f52c6-0000-0000-0000-100000000000}\
PSComputerName       : DELL590HV12

There are no spanned volumes.

The sum of all SizeRemaining = 535GB

The only second disk has correct SizeRemaining

Size                 : 162522984448
SizeRemaining        : 128554635264

128554635264/(1024*1024*1024) = 119.725833892822 Gb

Hi,

problems with WF encryption was discussed here many times before, but I think that now it's related to Windows 10 1903, because Windows 10 1809 is working fine.

Error message is still the same:

Sync failed. Work Folders path: C:\Users\MYUSER\Work Folders; Error: (0x80c80314) The Work Folders path has to be encrypted. You might have an application holding the Work Folders folder open or the folder might be compressed. Close File Explorer and any open files or apps, and check the folder's Advanced properties to ensure that the folder is not compressed. EventID 2100

I had tried Windows 10 1903 domain joined / not domain joined, followed tips on https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Troubleshooting-Work-Folders-on-Windows-client/ba-p/425627 but WF encryption is still failing.

Has anyone working WF on Windows 10 1903 with encryption enabled?

Best regards,

Jiri

hi friends

an strange problem. when i connect any USB flash drive to my computer (windows 2012 datacenter), in diskmanagment console, there is no "offline" command.

only these commands exist there: change drive letter- eject - properties- help

whay make offline does not exist ?  i must first be able to offline that so that i can continue your solution.

any help please

After installing KB4503276 on June 12, 2019, our Mac clients can no longer connect to SMB file shares on our Windows 2012 R2 server. Mac clients at our company regularly mount SMB volumes from the server onto their Mac desktops in order to access files stored on the server. Please observe that this problem has been noted as a product alert to its customers (such as our company) by Kodak, Inc. on June 12, 2019, and it also pertains to KB4503292 on Windows 2880 R2 servers; see their knowledgebase Answer ID 74519, quoted below.

"After installing Windows 2008 R2 KB4503292 update or Windows 2012 R2 KB4503276, macOS client users will be unable to connect to any SMB file share on the Windows server."

Link to the full alert article at Kodak: https://services.kodak.com/app/answers/detail/a_id/74519

As a graphic arts customer using Kodak-supplied software we received the abovementioned product alert and followed Kodak's recommendation to uninstall the update, after which our SMB file shares were again useable by Mac clients.