this is probably a weird question but;

I was trying to set up a iscsi system with some drives i have in xen and long story short it wouldnt work because xen wants to format everything and the box i have xen on wont hold all the drives. so as a concept thing i moved 2 of the drives to a old computer and tried both freenas and openbox, freenas is too buggy on that box and has bad transfer speed and openfiler i just gave up on for.. (i don't remember)

anyway settled on debian, iet and openscsi.. set them up and got them working and have a target set up in my (local) domain and it works flawlessly..after fixing the windows trottling on my win7 box i get transfers in the 150+ range till the (network-server combo) bogs then about 50+ on average. (gig net) is very fast

the trouble is i used the windows initiator and comp manager to initalize the drive(s) and my linux boxes wont see the disk correctly. I do get the drive(s) connected but they can't do anything with the file system.

the drives are 2 seagate 2tb partioned on the iscsi server box as linux auto raid . they are in a raid 0 originaly formated as ext2 but windows reformated as ntfs and gpt (to windows this is a iscsi drive) my kernel does have guid on . gparted can see it and the partitions but there is no device in /dev for them (and i don't have a clue how to mknod sda1 and 2 for the partitions)

So the final question is this working 4 tb iscsi target that is really a md linux device that my windows machine is using how do i make it work in linux with out destroying the windows file system? I'm sure i can partition it and use it (linux) but i'll bet windows will cry foul

( belive it or not i never thought that mounting this would be a problem in the system that created it) either as an iscsi device or a regular block device

I think the prob is linux aint up to speed on the guid yet
and sharing the same partion ID with windows gpt screws the pooch... but i could be wrong