This has been an interesting experience so far. It shows that I need to read more to figure out what is happening.
To pick up from where I left off earlier after adding a Virtual Machine to the N5200 Pro via iSCSI. Bouncing back between the physical server, two virtual servers and a Windows 7 RC machine ( I know using beta software to test stuff) I get a message about the file system having errors and needing to be fixed. Will look at that later and remove the Win 7 machine and use a XP or Vista machine. Everything appeared to be working fine. I could stop/start the NAS VM without issue. Next step was to test what would happen if the power went out. So I shut down all three VMs on the server and powered off the server. Since this is a test box there was no UPS. Powered on the server and waited. The physical server boots and then loads a virtual SBS2008 and five minutes later starts Server 2008 Standard and after another 5 minutes starts the test VM from the N5200 Pro NAS via iSCSI. Except it didn't work out that way. After a while I logged on to the physical server and started Hyper-V Manager. Hmmm.. the NAS VM was off. The first two VMs (each on a separate disk on the physical server) booted just fine. OK maybe I forgot to set the auto startup correctly. No it's set correctly. Try to start the NAS VM and nothing except file not found. What! Looked on the physical server for the network connection and found nothing there. It was blank. Alright I must have set up something wrong. Checked the settings on the server and NAS and all look correct. In Hyper-V Manager created a new hard drive again using the iSCSI connection to the NAS. Then create a new virtual server and it creates the folders and installs fine. Install Integration Services and it looks good. Change the Time Zone and join to the SBS2008 domain. Joins fine. Sits overnight. Checked for updates needed and there are several. Install the updates and reboot, Comes up fine. Check for updates again and see the .NET 3.5 one. Click install, goes through install and shows reboot now. Click reboot, look away, look back and see a blue screen in the NAS VM. Now what did I do? Looked at the screen and went to get a pen to write down the error but not thinking click start the VM again. No go. Get a message about the file or directory being corrupted or unreadable. While deciding I need to start over from scratch, I've decided to update this adventure, go get something to eat and drink and start over again without Win 7 this time. From: Eric E Eskam [mailto:[email protected]] Sent: Wednesday, May 20, 2009 6:21 AM To: NT System Admin Issues Subject: RE: Drobo Pro "Art DeKneef" <[email protected]> wrote on 05/19/2009 01:01:56 PM: > Added N5200 Pro and configured for iSCSI. Ah, thought you had a Drobo Pro. I have been looking at Thecus - they seem to be a tight competitor to Qnap. The more I think about it, for the price if it performs you can't beat the Drobo Pro - even if I can't boot off of it. I think I'm going to go ahead and order one as I just don't need all the extra features that Thecus and Qnap offer. I'll post back once I get it and have a chance to test it out. Eric Eskam =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The contents of this message are mine personally and do not reflect any position of the U.S. Government "The human mind treats a new idea the same way the body treats a strange protein; it rejects it." - P. B. Medawar ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
