Cannot use volume, bad blocks

[Donal]

Hi. I just installed StarWind on my file server and StarPort on my app server. I created a 1gb image file and shared it. Went to the app server and connected to it, everything peachy. Windows saw it and it shown up in disk manager. However, when it went to initalize it failed and the system log showed a ton of bad block errors.

How do I fix this?

Also, I downloaded the lowest functionality version that the site said was free, but when I launch it I get "trial version, 30 days left". Did I somehow download the wrong file or something? Thanks!

[Bohdan (staff)]

Hello,
The installer is unified for all of the StarWind types.
Please reade carefylly the received e-mail and you'll find the link to the free personal licens. Please download that license and register StarWind with it.

Also please send us logs from StarWind installation directory to find a solution for bad locks error.
Thanks.

[Donal]

Ahh, I see the license now, thanks.

I'll email those logs, thanks again!

[anton (staff)]

Got the logs from you, thank you... Checking what's wrong. Initially sounds like MS iSCSI initiator cannot get responses from the target so I/O manager decides the sector is bad. What network configuration do you have?

[Donal]

The two servers have gigabit nics and a crossover cable between them. The target is 10.0.1.1 and the initiator is 10.0.1.2. I also tried running it on my gig switch instead of direct crossover. I also tried running it via the regular LAN interface. I did notice that if I created the volume on the C:\ of the target, it would work fine. It's when I create it on the D:\ that it fails. D: is a RAID5 array. Does the freebie one not work with RAID?

[anton (staff)]

Check you local RAID performance. And check did you initialize the image with zeros during creation. With slow writes and uninitialized image it will not work.

The two servers have gigabit nics and a crossover cable between them. The target is 10.0.1.1 and the initiator is 10.0.1.2. I also tried running it on my gig switch instead of direct crossover. I also tried running it via the regular LAN interface. I did notice that if I created the volume on the C:\ of the target, it would work fine. It's when I create it on the D:\ that it fails. D: is a RAID5 array. Does the freebie one not work with RAID?

[Donal]

I didn't init 0 on the big file, but as I was testing I tried a 0 init'd 256mb file and it also didn't work.

here are the hd tach results for my two drives:

Drive C:, ATA 160gb single drive on mobo IDE:



Drive D:, RAID5 3 TB array using Areca ARC-1160ML2:

[anton (staff)]

These are read results. And in your case the problem is writes. Having ~5MB/sec sustained transfer rate for RAID5 volume is definitely an issue. And I'd kick Areca guys to fix it BEFORE using the volume as iSCSI target storage source

[anton (staff)]

Any news from ARECA support ATM?