CHKDSK needed on volume (CSV). Unable to do VM storage migration

%3CLINGO-SUB%20id%3D%22lingo-sub-708186%22%20slang%3D%22en-US%22%3ECHKDSK%20needed%20on%20volume%20(CSV).%20Unable%20to%20do%20VM%20storage%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-708186%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20everyone%20is%20well.%20Needed%20some%20advice%20if%20possible.%3C%2FP%3E%3CP%3EI%20have%202012%20cluster%20and%20the%20SAN%20is%20hanging%20on%20by%20a%20thread.%3C%2FP%3E%3CP%3EI%20managed%20to%20migrate%20all%20of%20the%20VMs%20to%20the%20new%20SAN%20except%20for%202.%3C%2FP%3E%3CP%3EEvery%20time%20I%20try%20doing%20a%20storage%20migration%2C%20I%20get%20CRC%20errors.%3C%2FP%3E%3CP%3EShutting%20down%20the%20VM%20and%20doing%20a%20file%20level%20copy%20also%20fails.%3C%2FP%3E%3CP%3EThe%20problematic%20CSV%20has%20the%20following%20error%20listed%20on%20it%20%E2%80%93%20%E2%80%9Cchkdsk%20scan%20needed%20on%20volume%E2%80%9D.%3C%2FP%3E%3CP%3EI%20am%20guessing%20this%20is%20due%20to%20the%20SAN%20on%20its%20way%20out.%3C%2FP%3E%3CP%3EI%20have%202%20production%20VMs%20remaining%20on%20there%20so%20I%20need%20to%20proceed%20with%20caution.%3C%2FP%3E%3CP%3EI%20tried%20running%20%E2%80%9C%3CSTRONG%3Echkdsk.exe%20%2Fscan%3C%2FSTRONG%3E%E2%80%9D%20however%20I%20get%20the%20following%20error%3A%20%3CSTRONG%3EThe%20shadow%20copy%20provider%20had%20an%20unexpected%20error%20while%20trying%20to%20process%20the%20specified%20operation.%20A%20snapshot%20error%20occurred%20while%20scanning%20this%20drive.%20You%20can%20try%20again%2C%20but%20if%20this%20problem%20persists%2C%20run%20an%20offline%20scan%20and%20fix%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3EI%20read%20so%20many%20articles%20where%20I%20must%20put%20the%20CSV%20in%20maintenance%20mode%20but%20what%20will%20happen%20to%20the%202%20VMs%20running%20on%20there.%3C%2FP%3E%3CP%3EI%20also%20came%20across%20an%20article%20that%20mentioned%20I%20run%20chkdsk.exe%20%2FSpotFix%3C%2FP%3E%3CP%3EWhat%20are%20repercussions%20of%20doing%20this%3F%3C%2FP%3E%3CP%3EAppreciate%20any%20advice.%3C%2FP%3E%3CP%3EMy%20goal%20is%20to%20ultimately%20do%20a%20storage%20migration%20of%20the%20remaining%202%20VMs%20to%20the%20new%20SAN%20and%20CSV.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-708186%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Regular Contributor

Hi All

 

Hope everyone is well. Needed some advice if possible.

I have 2012 cluster and the SAN is hanging on by a thread.

I managed to migrate all of the VMs to the new SAN except for 2.

Every time I try doing a storage migration, I get CRC errors.

Shutting down the VM and doing a file level copy also fails.

The problematic CSV has the following error listed on it – “chkdsk scan needed on volume”.

I am guessing this is due to the SAN on its way out.

I have 2 production VMs remaining on there so I need to proceed with caution.

I tried running “chkdsk.exe /scan” however I get the following error: The shadow copy provider had an unexpected error while trying to process the specified operation. A snapshot error occurred while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.

I read so many articles where I must put the CSV in maintenance mode but what will happen to the 2 VMs running on there.

I also came across an article that mentioned I run chkdsk.exe /SpotFix

What are repercussions of doing this?

Appreciate any advice.

My goal is to ultimately do a storage migration of the remaining 2 VMs to the new SAN and CSV.

0 Replies