danaxmidnight.blogg.se

1. #DATA ERROR CYCLIC REDUNDANCY CHECK WHEN INITIALIZING DISK MANUAL#
2. #DATA ERROR CYCLIC REDUNDANCY CHECK WHEN INITIALIZING DISK WINDOWS#

We're going to have a storage expert come take a look asap.We're between a rock & hard place on this one, because we needed this storage online last week and we can't have the existing array down during business hours, so it might come down to installing a 2nd HBA dedicated to our other two enclosures, then doing some fancy footwork to migrate over to it.Įdit3: We bought two spares with the latest set of drives. However, I'm at the office now, with a new configuration and it's not looking good.Įdit2: Starting to suspect bad HBA or cable. If not, we have a bailout strategy (some old drobo enclosures, that I hope support SAS, and I can use to temporarily use the 8TB disks to offload the 40TB array, then rewire it correctly).Įdit: I Should have noted that the reason I suspect the wiring, is that we had tried TrueNAS before realizing that ZFS wouldn't work for our needs, and I had previously wired it as such that TrueNAS threw an error about suboptimal multipathing before I hooked it up another way. It turns out that I indeed screwed up on the first two enclosures, according to the manual, but I'm hoping that I can find a way to make the daisychained ones work anyway.

#DATA ERROR CYCLIC REDUNDANCY CHECK WHEN INITIALIZING DISK MANUAL#

Long version, if you're bored: I couldn't find the manual for the SAS enclosures we're using until after I already had our first array online, so I was very unsure if I had hooked them back up correctly (my company recently moved, and apparently nobody bothered to label the cables when they tore that server down). TL DR - I don't think I have the daisychained enclosures hooked up correctly, or possible HBA issue. Since you think it's hardware (and I don't disagree), then I might already know what the issue is. It finished successfully in 14hrs (would rather not do that again, if I can avoid it).Īny help is greatly appreciated. We also had some trouble initializing it the first time - I told the controller to do the work in background mode so we could boot the OS & still access the first array, but after 48hrs, it hadn't completed so I had to abort & retry over the weekend in foreground mode. I have pretty limited experience with such storage setups (especially iSCSI).I've set a few up in my life but they always just work.Īll I can think of, is maybe the array is just too big? Haven't found any evidence of that possibility. Again, it all works fine with the first array. The iSCSI is set up to use a dual port 10Gbps fiber channel adapter, and has MPIO configured. Both arrays are set to 4kn in the controller. Otherwise, all the disks are HGST SAS 12Gbps, 4kn, RAID6, and are attached to an Areca ARC-1883X controller.

#DATA ERROR CYCLIC REDUNDANCY CHECK WHEN INITIALIZING DISK WINDOWS#

However, the new array gives the error in the post title, when I try to initialize it in Windows Disk Management. We previously set up a 40TB array without any issues and it's still working fine. The server is running Enterprise Storage OS (ESOS). We're trying to get an 80TB array mounted in Windows Server 2012r2 via iSCSI (Windows is not activated but I can't imagine that being the issue).