No - Haven't tried running from a USB stick yet, but I did make some progress..

I took the 200g out of the box, and then re-initialized my raid completely to have a 2g partition 1, and the rest (1.9t) as partition 2....

Booted from CD, and to my surprise, I saw THREE options for install..
SDA: 2g
SDB: 1999g
SDC: 1250g

There is DEFINITELY no other drives in there, so the ONLY thing I figured it could be is that it's detecting a FC LUN exposed by another machine on the switch. I proceeded to install on the 2G drive, and it did boot up, and confirm to me that the SDC drive was on another opensource SAN (I'm running OpenFiler, with some FC manual commands added in for FC support)

My HOPE was that after I hardcoded both FC ports (dual port QLogic card) to be target mode, that this would go away, but it didn't... I also found a hardware setting in the QLogic driver config (on the console) that let me set "Initator mode" to NEVER start, but even that didn't stop the LUN from appearing.

Now, I KNOW the RIGHT thing to do is to use some FC zoning to stop the LUN from appearing, but isn't there some way to tell Open-E that it's NOT going to use the LUNs it sees, and that I ONLY want it to be a target?

Secondarily, I've got a second issue:
The LUN from the Open-E server DOES show up, but with the wrong size...

In VMWare I see a FC disk of 229 MEGS, when in the Open-E FC Target Manager, I have a LUN0 called LV0000, which shows as 1852.97G.

I thought at first it was because it wasn't fully formatted or something, but I waited a day and did a rescan of ESX, and still have the same thing...

So, I guess technically I maybe should have 2 threads going here, but do you have any idea on either issue?
1: Shutting down initiator mode completely, and
2; Why the target shows the wrong size?

Thanks for your awesome quick responses!!

-Steve