Windows 2019 RDS sessionhost Filesystem error after some time

%3CLINGO-SUB%20id%3D%22lingo-sub-2000810%22%20slang%3D%22en-US%22%3EWindows%202019%20RDS%20sessionhost%20Filesystem%20error%20after%20some%20time%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2000810%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20community%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20cli%C3%ABnt%20using%20an%20RDS%20farm%20with%206%20sessionshosts%20(all%20virtual%20machines%2C%20running%20on%20Hyper-V%20with%20several%20more%20(application%20and%20service)%20VM's%20without%20any%20problem.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20appr.%202%20days%20of%20running%20the%20filesystem%20reports%20errors%20and%20a%20repair%20is%20needed.%20This%20eventually%20happens%20on%20all%20sessionhosts.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20executing%20chkdsk%20or%20repair-volume%20(-scan)%2C%20which%20by%20the%20way%20is%20working%20fine%20and%20reports%20no%20problems%20until%20ot%20goes%20wrong%2C%20we%20see%20the%20following%20message%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20snapshot%20error%20occured%20while%20scanning%20this%20drive.%20Run%20an%20offline%20scan%20and%20fix.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFollowed%20by%3A%26nbsp%3B%3C%2FP%3E%3CP%3ERepair-volume%20%3A%20A%20snapshot%20error%20occurred%20while%20scanning%20this%20drive.%20Run%20an%20offline%20scan%20and%20fix.%3C%2FP%3E%3CP%3EActivity%20ID%3A%20%7Bffc7a4d1-d448-0005-c9b1-c7ff48d4d601%7D%3C%2FP%3E%3CP%3EAt%20C%3A%5CWindows%5CLogs%5Ccheckfs.ps1%3A14%20char%3A1%3C%2FP%3E%3CP%3E%2B%20Repair-volume%20-driveletter%20C%20-scan%20-verbose%26nbsp%3B%20%26gt%3B%26gt%3B%20%24Logfile%3C%2FP%3E%3CP%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%2B%20CategoryInfo%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%3A%20NotSpecified%3A%20(StorageWMI%3AROOT%2FMicrosoft%2F...age%2FMSFT_Volume)%20%5BRepai%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3Br-Volume%5D%2C%20CimException%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%2B%20FullyQualifiedErrorId%20%3A%20StorageWMI%2043012%2CRepair-Volume%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20way%20to%20fix%20is%20to%20execute%3A%26nbsp%3B%3C%2FP%3E%3CP%3Evssadmin%20add%20shadowstorage%20%2Ffor%3Dc%3A%20%2Fon%3Dc%3A%20%2FMaxSize%3D20%25%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20we%20are%20able%20to%20scan%20and%20spotfix.%20The%20filesystem%20is%20damaged.%20Rebooting%20does%20not%20work%2C%20we%20have%20to%20atach%20the%20disk%20to%20another%20server%20to%20do%20a%20repair.%20When%20fixed%2C%20again%20after%20about%202%20days%20same%20issue..%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDone%20so%20far%3A%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Checked%20all%20Hypervisors%20for%20scheduled%20tasks%20etc.%20Nothing%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Spreaded%20the%20RDS%20session%20hoste%20over%20physical%20servers%2C%20same%20result%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Created%20a%20blank%20(new%2C%20fresh%20install)%20RDS%20session%20host%2C%20did%20a%20scan%20after%20each%20installed%20application%2C%20no%20problem.%20After%202%20days%2C%20same%20issue%20Filesystem%20defective..%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Shadow%20copy%20is%20disabled%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20in%20the%20System%20eventlog%20we%20see%20severall%20messages%20of%20(automatic%20maintenance%20scheduling%3F%3F)%20NTFS%20checks%20all%20with%20%22no%20error%22%20no%20action%20needed.%20Then%20suddenly%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3Bvolume%20C%3A%5C%20(device%5Charddiskvolume4)%20needs%20an%20online%20scan.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20moment%20we%20have%20no%20clue%20where%20to%20go.%20Any%20suggestions%20would%20be%20highly%20appreciated!%20Especially%20on%20the%20error%20message%20regarding%20the%20snapshot%20(!%3F)%20Apart%20from%20the%20defective%20filesystem%20we%20cannot%20explain%20how%20and%20why%20this%20error%20message%20appears.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdded%20information%2C%20in%20one%20occasion%20we%20noticed%20a%20message%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%22Low%20on%20registry%20space%3A%20%22the%20system%20has%20reached%20the%20maximum%20size%20allowed%20for%20the%20system%20part%20of%20the%20registry%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2000810%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Dear community, 

 

We have a cliënt using an RDS farm with 6 sessionshosts (all virtual machines, running on Hyper-V with several more (application and service) VM's without any problem. 

 

After appr. 2 days of running the filesystem reports errors and a repair is needed. This eventually happens on all sessionhosts.  

 

When executing chkdsk or repair-volume (-scan), which by the way is working fine and reports no problems until ot goes wrong, we see the following message: 

 

A snapshot error occured while scanning this drive. Run an offline scan and fix. 

 

Followed by: 

Repair-volume : A snapshot error occurred while scanning this drive. Run an offline scan and fix.

Activity ID: {ffc7a4d1-d448-0005-c9b1-c7ff48d4d601}

At C:\Windows\Logs\checkfs.ps1:14 char:1

+ Repair-volume -driveletter C -scan -verbose  >> $Logfile

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

    + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...age/MSFT_Volume) [Repai 

   r-Volume], CimException

    + FullyQualifiedErrorId : StorageWMI 43012,Repair-Volume  

 

The only way to fix is to execute: 

vssadmin add shadowstorage /for=c: /on=c: /MaxSize=20% 

 

Then we are able to scan and spotfix. The filesystem is damaged. Rebooting does not work, we have to atach the disk to another server to do a repair. When fixed, again after about 2 days same issue.. 

 

Done so far: 

- Checked all Hypervisors for scheduled tasks etc. Nothing 

- Spreaded the RDS session hoste over physical servers, same result 

- Created a blank (new, fresh install) RDS session host, did a scan after each installed application, no problem. After 2 days, same issue Filesystem defective.. 

- Shadow copy is disabled 

 

Looking in the System eventlog we see severall messages of (automatic maintenance scheduling??) NTFS checks all with "no error" no action needed. Then suddenly 

 volume C:\ (device\harddiskvolume4) needs an online scan. 

 

At this moment we have no clue where to go. Any suggestions would be highly appreciated! Especially on the error message regarding the snapshot (!?) Apart from the defective filesystem we cannot explain how and why this error message appears.  

 

Thanks! 

 

 

Added information, in one occasion we noticed a message: 

"Low on registry space: "the system has reached the maximum size allowed for the system part of the registry"

 

2 Replies

@PeterPodvodnik 

This is weird issue and need to be investigate and look into log files and reproduce this problem which is NOT possible through forum. I would recommend you either contact Microsoft Support (in case this is an urgent issue) or in case you have access to Windows 10 PC, copy log files and move it to Windows 10 PC and then open start and search for feedback and open Feedback Hub app and report this issue and under operating system select Windows Server (Feedback Hub is not available in Windows Server) so it would be investigated.

Are you running SSD or HDD on your physical disk?

@Reza_Ameri-Archived A supportcase has been made. The RDS host are running as VM's and the datastores on a HPE MSA with various disktypes. This environment run's severall VM's without problems, only RDS has issues. I posted ther question to find out if anyone ran in to this issue previously. 

 

Kind regards,