Corrupted Files after Event ID 35 Source: volsnap Aborted because the shadow copy storage failed to grow.

i have 2008 r2 server "all of sudden" stopped opening approx. 1 in 3 files error messages extension wrong or file corrupt.  approx. same time behavior started see event in system log: event id 35 source: volsnap, shadow copies of volume d: aborted because shadow copy storage failed grow.  the volume out of space.  not long after space became available again, not result of user action presumably os action.

any ideas how fix corruption?

thank you!

 

---

bob herman tropolis

hi,

hi,

please refer article event 35:

http://www.microsoft.com/technet/support/ee/transform.aspx?prodname=windows+operating+system&prodver=5.2.3790.1830&evtid=35&evtsrc=volsnap&lcid=1033%20:%20event%20id%2035

as mentioned, please try following steps 1 one see result:

using chkdsk /r, check errors on volume diff area stored , on original volume,.
check system log in event viewer errors associated volume diff area stored or original volume.
check hardware errors on disks contain volume diff area stored , on original volume.
move diff area different, dedicated volume.
move diff area larger volume.
allocate more storage space diff area.
increase diff area initial size , growth rate changing mindiffarea registry key.

note: use vssadmin move diff area

---

technet subscriber support in forum |if have feedback on our support, please contact tnmff@microsoft.com.

Windows Server  >  File Services and Storage