Hello. I recently bought a lightweight VMware environment consisting of a pair of HP N40L servers coupled to a pair of HP ML110 G7 servers. The ML110s are diskless, and using the N40Ls for their data storage. One N40L has 4x2TB drives and an extra dual port NIC and connects to the ML110 vSphere hosts via iSCSI. The second N40L has 4x250GB drives shared via NFS, and is destined to be the backup repository. The iSCSI box contains all of the VMware datastores for the virtual machines. This has all been working great for the last six weeks, but it has all gone horribly wrong today... We had a faulty light in the bathroom, so we had an electrician over to take a look at it. While he was here, we also needed a couple of wall sockets fixed. Unfortunately, the fuse box in our rented accommodation was incorrectly labelled, and so my office power was brought down hard, and all of my servers with it. Yes, yes, yes, UPS, blah blah, yada yada. If the fuses had been properly labelled, things would have been fine. Anyway, the upshot is that one of my physical servers has suffered a terminal failure. I have put the drives into another box so I can get to the data. This server was destined to be moved to the virtual environment in the next couple of weeks, so this is just bringing forward the plan. However, the VMware datastore N40L now won't boot up. The NFS one has come back up just fine, but I really need my VMware datastores back online so I can get on with the migration. So, my FreeNAS problem is this: When the N40L boots, it gets as far as the boot menu (F1, F2 etc), appears to start the bootstrap loader, but hangs at the message Loading /boot/defaults/loader.conf | <--This normally spins while things load up This is booting from a 2GB USB memory stick, so I am pretty confident that my data is still OK and sitting on the drives. But how do I go about fixing FreeNAS so it boots again ? I am toying with just trying to install it again but telling it to keep the config, which I seem to remember was an option. I would really prefer not to have to build the config from scratch again, and rely on importing the volume. Oh, I did try choosing F2 from the boot menu, but it just sat and filled the screen with # signs for about 30mins before I got bored and power cycled it. Thanks in advance, Stuart.