What he means is that WHS has its own Storage Management called Drive Extender which basically offers Data Duplication to 2 different hard drives. This comes in handy when you have an issue like the one your experiencing in that you can remove the data or Storage Pool Drives and read them in another computer thus not losing access to your data when the server is offline.
Drive Extender or DE as its often referred to is a simple way to manage your data in the server. It has its quirks but so does all storage solutions. One thing about DE is if you have a failed drive all you do is replace it and no harm done and the only data you would lose would be the data not duplicated for what ever reason.
With WHS it was not intended to run any other way.
As for your recovery you have to have the client direct connected to the server and not have the server on the network. When the server is in recovery mode it will use a predefined IP to work with TFTP the method used to transfer the recovery image from the client PC over to the server.
I recommend you pull the system disk out and connect it externally to another PC and run a CHKDSK on the drive to see if that will correct your boot issue. If your luck it will and you will have access to your server and let me tell you while there are times when a Recovery is necessary its always best to see if you can resolve your issue first because Recoveries are no joy and the updates take quite along time too.
What I can not help you with is your RAID configuration or how to recover your server and have it work with the RAID Array again.
_________________ Exploring the possibilities!
Migrated from WHS2011 to WS2012E: HIGHLANDER
~ Norco 4220 Enclosure ~ Gigabyte GA-990FXA-UD5 ~ AMD Phenom II X4 995 3.2 GHz ~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800) ~ 3 Supermicro AOC-SASLP-MV8
|