CRC error

myster2 · Tue Apr 17, 2012 2:20 pm

I’ve been using the free version of Starwind for iSCSI and after several successful months of use, the drive shows up in Disk Management as needing to be initialized. I’m trying to initialize the drive and I get an error “Data error (cyclic redundancy check).”

I noticed a bunch of these errors in the logs...
4/17 8:13:15.646 938 IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x0000000000660000, 512, 0x0) failed (21).

Can you help please help?

Also, during the registration process, there is an anti bot question “What is the capital of the United States?” which I assumed is asking "Where is the capital of the United States?" ....The answer that works is washington which is about 2500 miles off from being correct.

Tue Apr 17, 2012 4:40 pm

1) Do you have underlying disk working? It looks like StarWind cannot complete read request b/c of CRC error on underyling media.

2) I though Washington is a capital of a U.S.?

http://en.wikipedia.org/wiki/United_States_Capitol

myster2 · Tue Apr 17, 2012 5:02 pm

The disk is working fine and I can copy data to and from. I ran a chkdsk /r on the disk and it finished without any problems.

The setup up is iSCSI target goes to an external hard drive attached to the server. The iSCSI initiator is on a different server and connects to the target but in Disk Management shows up as not being initialized and get the "Data error (cyclic redundancy check)." message when I try to initialize. I'm hoping to find the problem rather than just recreate the target.

Washington is a state on the West coast of USA but "Washington D.C." is where you'll find the US capital just like your wiki link says.

Tue Apr 17, 2012 6:25 pm

OK, can you dismount the volume and copy .img file with Windows explorer to nul location?

Well, I think they've mean D.C.

myster2 wrote:The disk is working fine and I can copy data to and from. I ran a chkdsk /r on the disk and it finished without any problems.

The setup up is iSCSI target goes to an external hard drive attached to the server. The iSCSI initiator is on a different server and connects to the target but in Disk Management shows up as not being initialized and get the "Data error (cyclic redundancy check)." message when I try to initialize. I'm hoping to find the problem rather than just recreate the target.

Washington is a state on the West coast of USA but "Washington D.C." is where you'll find the US capital just like your wiki link says.

myster2 · Tue Apr 17, 2012 9:42 pm

I don't have another volume that is big enough to hold the .img file.

There was however 33GB of space left to create a new target on that disk and it worked like normal. No CRC error when I initialized it. I formatted and created a partition and it's taking data.

myster2 · Wed Apr 18, 2012 1:48 am

Ok, I got it working and didn't lose any of my data.

I removed the Target and recreated using the same .img file and it worked. YAY

Wed Apr 18, 2012 8:02 am

Copy to "nul" does not require any disk space as it's basically "copy to nowhere" action.

No... I'm interested in general availability of all the data mapped to this particular .img file so running other target is not what we want now

myster2 wrote:I don't have another volume that is big enough to hold the .img file.

There was however 33GB of space left to create a new target on that disk and it worked like normal. No CRC error when I initialized it. I formatted and created a partition and it's taking data.

Wed Apr 18, 2012 8:05 am

Good you've managed to have your config up and running. Bad we did not manage to isolate and solve the issue.

myster2 wrote:Ok, I got it working and didn't lose any of my data.

I removed the Target and recreated using the same .img file and it worked. YAY

wbfinney · Wed May 02, 2012 10:19 pm

Has there been any more information on this error? I am having almost the exact same problem except the storage is attached to a Areca SAS Raid card in my server, and after spending time with Max in a remote session we determined that the problems were limited only to the two RAID volumes created on the Areca RAID (5.45TB and 4.09 TB), which is in an external enclosure also. Changing and/or recreating the targets or the image files did not solve the problem. I'm contacting Areca Support to see if they have any insight on this, but I don't think they will. I'm going to do some experimentation and see what I learn.

Thu May 03, 2012 9:14 am

That customer solved his issue and continued going.

We're having majority of issues related to this vendor (Areca).

wbfinney wrote:Has there been any more information on this error? I am having almost the exact same problem except the storage is attached to a Areca SAS Raid card in my server, and after spending time with Max in a remote session we determined that the problems were limited only to the two RAID volumes created on the Areca RAID (5.45TB and 4.09 TB), which is in an external enclosure also. Changing and/or recreating the targets or the image files did not solve the problem. I'm contacting Areca Support to see if they have any insight on this, but I don't think they will. I'm going to do some experimentation and see what I learn.

Stiven · Tue Sep 04, 2012 10:19 am

Hello All!
i have areca storage+windows 2008sp2 server (as iscsi target).
on areca i create 8tb raid5 volume, mount it on server and format to NTFS with default cluster size.
this volume work fine, but I cannot work with Starwind server (free edition v 5.8.2013): i create target, assign .img-basic virtual disk; but on initiator server i got CRC error when initialize disk.
on iscsi log i found:
9/4 12:38:45.769 15a4 Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
9/4 12:38:45.769 15a4 Params: >>> AuthMethod=None.
9/4 12:38:45.769 15a4 Params: >>> TargetAlias=T1.
9/4 12:38:45.769 15a4 Params: >>> TargetPortalGroupTag=1.
9/4 12:38:45.769 1860 T[64c,1]: session 0x64c, connection 0x64c : end of stage 0, next stage 1.
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'ErrorRecoveryLevel': received 0, accepted 0
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'MaxConnections': received 1, accepted 1
9/4 12:38:45.770 15a4 Params: <<< Enum param 'HeaderDigest': received 'None', accepted 'None'
9/4 12:38:45.770 15a4 Params: <<< Enum param 'DataDigest': received 'None', accepted 'None'
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'OFMarker': received No, accepted 0
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'IFMarker': received No, accepted 0
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'InitialR2T': received No, accepted 0
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'ImmediateData': received Yes, accepted 1
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'MaxRecvDataSegmentLength': received 65536, accepted 65536
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'MaxBurstLength': received 262144, accepted 262144
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'FirstBurstLength': received 65536, accepted 65536
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'DefaultTime2Wait': received 5, accepted 5
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'DefaultTime2Retain': received 20, accepted 20
9/4 12:38:45.770 15a4 Params: <<< Numeric param 'MaxOutstandingR2T': received 1, accepted 1
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'DataPDUInOrder': received Yes, accepted 1
9/4 12:38:45.770 15a4 Params: <<< Boolean param 'DataSequenceInOrder': received Yes, accepted 1
9/4 12:38:45.770 15a4 Params: >>> ErrorRecoveryLevel=0.
9/4 12:38:45.770 15a4 Params: >>> MaxConnections=1.
9/4 12:38:45.770 15a4 Params: >>> HeaderDigest=None.
9/4 12:38:45.770 15a4 Params: >>> DataDigest=None.
9/4 12:38:45.770 15a4 Params: >>> OFMarker=No.
9/4 12:38:45.770 15a4 Params: >>> IFMarker=No.
9/4 12:38:45.770 15a4 Params: >>> InitialR2T=No.
9/4 12:38:45.770 15a4 Params: >>> ImmediateData=Yes.
9/4 12:38:45.770 15a4 Params: >>> MaxRecvDataSegmentLength=262144.
9/4 12:38:45.770 15a4 Params: >>> MaxBurstLength=262144.
9/4 12:38:45.770 15a4 Params: >>> FirstBurstLength=65536.
9/4 12:38:45.770 15a4 Params: >>> DefaultTime2Wait=5.
9/4 12:38:45.770 15a4 Params: >>> DefaultTime2Retain=20.
9/4 12:38:45.770 15a4 Params: >>> MaxOutstandingR2T=1.
9/4 12:38:45.770 15a4 Params: >>> DataPDUInOrder=Yes.
9/4 12:38:45.771 15a4 Params: >>> DataSequenceInOrder=Yes.
9/4 12:38:45.771 1860 T[64c,1]: session 0x64c, connection 0x64c : end of stage 1, next stage 3.
9/4 12:38:45.771 1860 C[64c], IN_LOGIN: Event - LOGIN_ACCEPT.
9/4 12:38:45.771 1860 C[64c], LIN: T5.
9/4 12:38:47.748 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.748 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.751 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.751 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.752 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.753 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.754 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.765 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.777 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.780 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.782 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.784 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).
9/4 12:38:47.845 1cbc IMG: *** ImageFile_ReadWriteSectors: ReadFileEx(0x00424000, 512, 0x0) failed (87).

My volume parameters:

Volume Name ARC-6360-VOL#00
Member Disks 10
Volume Raid Level: Raid 5 (Raid0/Raid1/Raid3/Raid5/Raid6)
Select Volume Capacity: 8000 GB
Greater Two TB Volume Support: 4K Block (No/64bit LBA/4K Block)
Volume Initialization Mode: Background Initialization (Foreground Initialization/Background Initialization/No Init (To Rescue Volume) )
Volume Stripe Size: 64KBytes (4/8/16/32/64/128 KBytes)
Volume Cache Mode: Write Back (Write Through/Write Back)
Tagged Command Queuing: Enabled (Disabled/Enabled )
Max SCSI Speed: 320MB/Sec (Async -40MB/Sec--80MB/Sec--160MB/Sec--320MB/Sec )

can U help me with this issue?

Tue Sep 04, 2012 3:22 pm

Greater Two TB Volume Support: 4K Block (No/64bit LBA/4K Block) - changes the sector size from default 512 to 4k.

Set this value to No.

Stiven · Tue Sep 04, 2012 9:09 pm

Bohdan (staff) wrote:Greater Two TB Volume Support: 4K Block (No/64bit LBA/4K Block) - changes the sector size from default 512 to 4k.

Set this value to No.

i kill my 9TB LUN and re-create it with NEW (NO) value!
in windows i see new 2TB disk (but LUN size on areca is 9TB!!! where is my 7TB???

).

i found http://www.scribd.com/doc/86300712/123/ ... me-Support
at page 128...

so, in ftp://ftp.areca.com.tw/RaidCards/Docume ... 080612.zip
i found some words about 2TB and conversation to GPT...
so - i try tu use "lba64" and "None"+GPT conversation... i write results after my investigations.

Stiven · Tue Sep 04, 2012 9:52 pm

now i try to use "None" value in "greater 2TB Support"...

so - i have 9TB LUN in ARECA and 2TB disk in windows.
conversation between MBR and GPT not appending 7TB to disk... i have 2TB in MBR mode and only 2TB in GPT mode
so - if vendor write NO greater 2tb support - that is NO GREATER 2TB SUPPORT

i have last chance - to use "lba64" mode...- in this case i must have 9TB LUN/disk and 512bytes per block (the same size in NONE value)...just wait to initialize LUN...

Fri Sep 07, 2012 7:23 am

Stiven wrote:now i try to use "None" value in "greater 2TB Support"...

so - i have 9TB LUN in ARECA and 2TB disk in windows.
conversation between MBR and GPT not appending 7TB to disk... i have 2TB in MBR mode and only 2TB in GPT mode
so - if vendor write NO greater 2tb support - that is NO GREATER 2TB SUPPORT

i have last chance - to use "lba64" mode...- in this case i must have 9TB LUN/disk and 512bytes per block (the same size in NONE value)...just wait to initialize LUN...

This should help. Please keep us updated.