Jump to content
RESET Forums (homeservershow.com)
Dan

My V1 acting strange

Recommended Posts

Dan
My WHS V1 that has been operating quietly for years started exhibiting 2 strange symptoms recently.
  1. When accessing some files on the shares, I started getting "can't open file" messages. 
  2. The system drive filled up with very little space left.
As you're all guessing by now, the cause of #2 above was log files going crazy. The log files, for the most part, were DEUtil and Transport. The gist of the complaints in the logs seems to be tombstone related, which would also explain #1 above (file shows as present in the share, but WHS can't find it). The voluminous log entries is likely due to backup jobs and Plex scans trying to access many files in a row.
 
Below are some excerpts from the logs showing what I mean.
 
From DEUtil.xxxxx.log:
[1/3/2016 10:39:34 PM  7f4] DEFilter!OpenOneShadowFile: FltCreateFile('\Device\HarddiskVolume1\DE\shares\Software\Operating Systems\Windows Vista x64 Recovery Disc.iso') method ImpliedPath failed with error 0xc000009d
[1/3/2016 10:39:34 PM  7f4] DEFilter!FullyOpenOneShadow: Shadow open by implied path failed, status c000009d, FO 85d2dc48
[1/3/2016 10:39:34 PM  7f4] DEFilter!OpenOneShadowFile: FltCreateFile('FileID 0x007600650044005c') method ByID failed with error 0xc000009d
[1/3/2016 10:39:34 PM  7f4] DEFilter!FullyOpenOneShadow: Reopen by ID failed with c000009d for FO 85d2dc48
[1/3/2016 10:39:34 PM  7f4] DEFilter!OpenOneShadowFile: FltCreateFile('\Device\HarddiskVolume1\DE\shares\Software\Operating Systems\Windows10_InsiderPreview_x64_EN-US_10565-2.iso') method ImpliedPath failed with error 0xc000009d
[1/3/2016 10:39:34 PM  7f4] DEFilter!FullyOpenOneShadow: Shadow open by implied path failed, status c000009d, FO 85d2dc48
[1/3/2016 10:39:34 PM  7f4] DEFilter!OpenOneShadowFile: FltCreateFile('FileID 0x007600650044005c') method ByID failed with error 0xc000009d
[1/3/2016 10:39:34 PM  7f4] DEFilter!FullyOpenOneShadow: Reopen by ID failed with c000009d for FO 85d2dc48

From Transport.xxxx.log:

[2015/12/08 00:00:30  b5c]   CTransportSinkManager::ProcessRecvQueue Routing failure.
[12/8/2015 12:00:51 AM 8980] ERROR: Sink Notifications::CProtocol::Listen (pid=2952, GUID=d4654827-0304-428e-aa02-c967212fb53f) was reported as in progress during queue overflow.

[2015/12/08 00:00:51 8980]   CTransportQueue::push ERROR: Queue overgrowth: 101 messages
[12/8/2015 12:00:51 AM  b30] ERROR: Sink Notifications::CProtocol::Listen (pid=2952, GUID=d4654827-0304-428e-aa02-c967212fb53f) was reported as in progress during queue overflow.

[2015/12/08 00:00:51  b30]   CTransportQueue::push ERROR: Queue overgrowth: 102 messages
[12/8/2015 12:00:51 AM  b30] ERROR: Sink Notifications::CProtocol::Listen (pid=2952, GUID=d4654827-0304-428e-aa02-c967212fb53f) was reported as in progress during queue overflow.

So I can still access some files through the shares, but not others. Almost all shares are duplicated. After moving the logs off of the system drive to another system, I turned off DEMigrator while I tried to figure this out, and the logs stopped growing at such a clip. I shut down the server a few hours later so as to minimize any further damage.

 

I'd like to get others opinions on what's going on. I don't want send anyone in the wrong direction, but in my mind, this may have something to do with the system drive replacement that I did 6+ months ago. In that case, the system drive started to go bad. I pulled it and repaired via chkdsk then quickly cloned using the standard instructions at Mediasmartserver.net here. I replaced the original 500G drive with a 2TB, and followed the instructions to edit the offsets, etc. Everything went as described with the one exception of the console never showing the full size of the drive in the drive list, but the pool increased by the right amount. Everything then went on as normal until about the beginning of December when I started getting the "can't open file" messages.

 

Any troubleshooting help would be very much appreciated.

 

Thanks.

 

Share this post


Link to post
Share on other sites
Drashna Jaelre

Force migrate the data off of the system drive.

http://web.archive.org/web/20100325211426/http://wiki.wegotserved.com/index.php?title=Force_Data_Migration_off_the_Primary_Data_Partition

 

Once that's done, wipe the system drive (both the C: and D: partitions), remove the pooled drives, and reinstall.

 

Then migrate the data back into the pool:

http://web.archive.org/web/20100325211426/http://wiki.wegotserved.com/index.php?title=Migrate_Shares_and_Backups_to_New_System

 

 

Ideally, this is what you should have done in the first place, as cloning the system drive is problematic *at best*. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×