hey guys,
I've recently bought a mediasonic hf2-su3s2 enclosure and have to connected to my h340 via eSata. I've had some inconsistent behaviour when trying to boot into my OS (WS2012R2). I have 3 drives that I have installed in the enclosure. let's call them:
SD1 (system drive 1: the old WHSv1 system drive, 1 20GB partition and 1 ~1TB paritition)
SD2 (system drive 2: a test WS2012R2 system drive, 1 320MB partition, and 1 ~450GB paritition)
PD3 (pool drive: 1 2TB partition)
When I have SD1 and SD2 installed in any two slots of the mediasonic enclosure on eSata, the H340 hangs during boot.
When I have SD1 and SD2 installed in any two slots while on USB, the h340 boots fine.
So it seems like PD3 is allowing the h340 to boot while the mediasonic is connected via eSata... So what the heck is PD3 doing?
I thought it was because SD1 and SD2 had bootable partitions but I've since marked them inactive and even deleted the parition (I kept the 2nd larger parititons untouched) but it had *no* affect. I thought it was the position of the drives in the mediasonic enclosure but it didn't matter. SD1,SD2,PD3 worked just the same as PD3,SD1,SD2
Unfortunately, I don't have a forth drive to test with and I don't have the VGA cable to debug the POST results.
My actual H340 is running a 240GB SSD, and 1x1TB,2x2TB drives all with single partitions. I was under the impression that by default, the h340 does *not* boot from eSata.
Can anyone here explain what's going on?
Thanks!