2008 R2 File Server Issues

[blu4]

Hi,

 

I'd appreciate help with this as it's critical... and I'm pulling my hair out

 

We are running a virtual file server that has got three disks atattched:

 

E: Admin Data

F: Teacher Data

G: Other shares

 

This is the problem- there are multiple shares on the E: drive and people can connect to them and browse folders but they are ALL empty. The F: and G: drives are unaffected. Weird thing is, since all the folders are empty, why is the VHD still 240GB? It's the size that it normally is. I have checked the logs and I'm getting a LOT of the following:

 

Event 57: NTFS

The system failed to flush data to the transaction log. Corruption may occur.

 

Event 51: Disk

An error was detected on device \Device\Harddisk3\DR3 during a paging operation.

 

I have tried removing and re-atattching the VHD to the virtual machine. Did not work. I have also checked the SAN's where the CVS resides for disk errors. All fine. I did not reboot the server yet as the other two shares are in heavily in use. There is pleny of RAM to spare and CPU overhead. It was working fine last friday and I come to work, on a monday morning, to this. Please help. I'm about to lose my sanity (I'm on my own at the moment).

 

Thank you for all the help.

[pantscat]

If the VHD had grown to 240GB it'll only shrink back to the size it's actually using if you tell it to using Hyper-V manager.

 

Should the files be there? or have they been deleted by a user/something else?

 

Looking at your event logs, it looks like there might be a problem with the filesystem on that VHD - have you done a chkdsk from the VM?

[blu4]

If the VHD had grown to 240GB it'll only shrink back to the size it's actually using if you tell it to using Hyper-V manager.

 

Should the files be there? or have they been deleted by a user/something else?

 

Looking at your event logs, it looks like there might be a problem with the filesystem on that VHD - have you done a chkdsk from the VM?

 

The disk is a fixed size, 511GB. Files have to be there, not possible they were deleted. It's not letting me do a chkdsk even in elevated CMD- error chkdsk cannot open volume for direct access.

 

Update: I can do a chec disk on all the other two VHDs but not on the one that has the issue.

Edited October 17, 2016 by blu4

[pantscat]

Sounds like a corrupt file table or similar - Do a chkdsk and prepare to restore a backup.

[blu4]

Can't do a checkdisk on the affected VHD.. "cannot open volume for direct access". Check disk works fine on the other two.

[pantscat]

Does Event Viewer give any more detail related to that error?

 

You might have to do a chkdsk /r /f and reboot the server.

[blu4]

Does Event Viewer give any more detail related to that error?

 

You might have to do a chkdsk /r /f and reboot the server.

 

It doesn't. Very generic error. This is the XML view:

 

- [/b]

-

 

57

 

3

 

2

 

0x80000000000000

 

 

1032573

 

System

 

FILESTAFF01.domain.local

 

 

 

 

 

-

 

00000000010000000200000039000480000000000E0000C000000000000000000000000000000000

 

 

 

 

 

[rrrrr]

Think check disk and restart is 1st port of call.

Are the directories empty when browsing on server too? Or just when looking at the share?

[blu4]

Think check disk and restart is 1st port of call.

Are the directories empty when browsing on server too? Or just when looking at the share?

 

Same thing when browsing the server directly, logged on as local administrator.

[rrrrr]

Have you performed checkdisk?

[blu4]

Problem solved... Only took a reboot. I don't like the idea of it happening again though.

 

Thank you for all the suggestions!

 

I will still perform a checkdisk on that drive.