ISCSI volume corrupt

%3CLINGO-SUB%20id%3D%22lingo-sub-1055237%22%20slang%3D%22en-US%22%3EISCSI%20volume%20corrupt%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1055237%22%20slang%3D%22en-US%22%3E%3CP%3EA%20new%20Microsoft%20server%202019%20standard%20has%20been%20installed%20replacing%20an%20old%20MS%20server%202008%20SBS.%26nbsp%3B%20Attached%20to%20it%20is%20a%20Buffalo%20terastation%207000%20series%20NAS%20containing%204%204TB%20hard%20drives%20RAID%205%20configured%20with%20an%20ISCSI%20volume%2C%20attached%20to%20the%202019%20server%20via%20ISCSI%20initiator%20as%20drive%20F%3A%20on%20the%20server.%20The%20new%20server%20has%20reported%20the%20ISCSI%20volume%20to%20be%20corrupt%20and%20wants%20to%20preform%20an%20%22offline%20scan%20and%20repair%22.%26nbsp%3B%20The%20old%20server%20never%20reported%20any%20issue%20with%20the%20volume.%3C%2FP%3E%3CP%3EMy%20question%20is%20what%20will%20this%20offline%20scan%20and%20repair%20do%3F%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20the%20server%20take%20the%20volume%20offline%20and%20still%20complete%20the%20scan%20and%20repair%20as%20the%20volume%20is%20not%20physically%20part%20of%20the%20server%20but%20only%20attached%20to%20it%20via%20the%20initiator%3F%3C%2FP%3E%3CP%3ECould%20data%20lost%20be%20a%20possibility%3F%3C%2FP%3E%3CP%3ECould%20we%20lose%20complete%20access%20to%20the%20NAS%20if%20the%20volume%20does%20not%20come%20back%20online%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1055237%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1062279%22%20slang%3D%22en-US%22%3ERe%3A%20ISCSI%20volume%20corrupt%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1062279%22%20slang%3D%22en-US%22%3E%3CP%3Ewell%20since%20no%20one%20seems%20to%20have%20seen%20this%20issue%20and%20cannot%20recommend%20a%20course%20of%20action%20I%20took%20it%20upon%20myself%20to%20go%20boldly%20where%20no%20one%20has%20gone%20before.%3C%2FP%3E%3CP%3EI%20ran%20the%20offline%20scan%20and%20repair%20and%20it%20failed%20to%20complete.%26nbsp%3B%20unable%20to%20access%20the%20volume%20once%20it%20went%20offline%20which%20is%20what%20I%20suspected%20would%20happen.%3C%2FP%3E%3CP%3Eno%20option%20selected%20for%20this%20utility%20could%20complete%20the%20scan%20and%20repair.%3C%2FP%3E%3CP%3EOk%2C%20so%20I%20decided%20to%20use%20the%20tried%20and%20proven%20chkdsk%20utility%20and%20it%20scanned%20and%20fixed%20the%20volume.%26nbsp%3B%20After%20a%20restart%20of%20the%20NAS%20server%20and%20volume%20reconnected%20and%20Windows%20server%202019%20now%20reports%20the%20volume%20as%20healthy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

A new Microsoft server 2019 standard has been installed replacing an old MS server 2008 SBS.  Attached to it is a Buffalo terastation 7000 series NAS containing 4 4TB hard drives RAID 5 configured with an ISCSI volume, attached to the 2019 server via ISCSI initiator as drive F: on the server. The new server has reported the ISCSI volume to be corrupt and wants to preform an "offline scan and repair".  The old server never reported any issue with the volume.

My question is what will this offline scan and repair do? 

Can the server take the volume offline and still complete the scan and repair as the volume is not physically part of the server but only attached to it via the initiator?

Could data lost be a possibility?

Could we lose complete access to the NAS if the volume does not come back online?

 

1 Reply
Highlighted

well since no one seems to have seen this issue and cannot recommend a course of action I took it upon myself to go boldly where no one has gone before.

I ran the offline scan and repair and it failed to complete.  unable to access the volume once it went offline which is what I suspected would happen.

no option selected for this utility could complete the scan and repair.

Ok, so I decided to use the tried and proven chkdsk utility and it scanned and fixed the volume.  After a restart of the NAS server and volume reconnected and Windows server 2019 now reports the volume as healthy.