Diatoms and Cyano Bacteria

Now this is weird. In an established tank, I all of a sudden have red dust and red algae covering everything. I will be performing some water changes, but I have taken photos for those who are searching the net for examples.

  • First image with the green arrow is the Cyano Bacteria or red slimy algae as it is sometimes referred to.
  • Second image is the diatoms or the red/brown dust.

Both of these should not appear in an established tank! It should only occur during cycling.

A good article I ran across is here: http://www.nano-reef.com/forums/index.php?showtopic=132956

Hyper-V WordPress Appliance

After my server crash, I moved from Vmware Server to Hyper-V. I wanted to go ESX, but I haven’t got hardware fully support by ESX. Nonetheless, using Hyper-V I’m extremely impressed by it’s speed and reliability.

The problem with Hyper-V is that there is not as many appliances readily available. And those that are available are generally a port of a VMware appliance and not really tested.

I had an issue looking for a WordPress appliance that would work on Hyper-V without too much mucking around as I’m not really a hardcore Linux person. I managed to find a VMware appliance that would port straigh over to Hyper-V with little fuss. It’s the TurnKey WordPress appliance available here: http://www.turnkeylinux.org/wordpress

Just use the StarWind Converter on it to port the vmdk files to a VHD file. Then chuck it into Hyper-V and start it up. Make sure you use the legacy Network Adapter. Everything works error free and without hassle! Great appliance that is ready to go!

Migrating WordPress Blog to new server using same domain name

The import/export feature of WordPress is excellent. The issue is when you choose to import the images/media files and it needs to download them from your old WordPress site. You won’t have an issue if your old and your new site use different domain names (ie. oldblog.fuelip.com and newblog.fuelip.com).

However, if you’re like me and you just want to move from blog.fuelip.com to another server whilst still maintaining blog.fuelip.com then it’s a little more work. You’ll probably find that images may not display properly because WordPress embeds the full path of the image when it’s being uploaded.

Please note that I am writing this blog which details a method I used to get my site across. There may be alternative ways/easier ways, but this worked for me and I thought I’d share it.

This is how I did it.


  • Windows PC
  • Ability to modify DNS records on the linux server or a DNS server

Setup your new blog and have your old blog up and running.

For arguements sake, let’s say:
blog.fuelip.com ->
new wordpress ->

Now use the export feature to export your current blog to an XML file. This does not export the images. Images are pulled from the old site automatically (it’s an option) when you use the Import Feature.

Here’s the tricky bit.
Edit the host file on your Windows PC so that blog.fuelip.com points to (which is the new site). This means that on your PC only, blog.fuelip.com will point to the new/empty blog site.

On the new WordPress server, the DNS should point to a DNS server you have access to. This should still be pointing to the OLD WordPress server ie. blog.fuelip.com still points to

So let’s recap, we have got a Windows PC that thinks blog.fuelip.com points to which is the NEW WordPress server. The actual server hosting the new WordPress application thinks blog.fuelip.com points to which is the OLD WordPress server.

Not on the Windows PC, lets use the Import feature and import the XML file we saved earlier. Make sure you choose to download images/media. Also make sure the users are setup the way you want. Then hit Import.

You should find that the whole site is imported perfectly.

Why does this work?

  • The references for the images are based on the URL that is shown whilst you’re browsing the site on the Windows PC (host file makes DNS point to the new site)
  • The downloading of the images from the old site is handled behind the scenes by the actual WordPress server which is looking at a different site due to the DNS change.

Hope this is not too confusing…

Comments welcome!

VMware to Hyper-V (STOP 0×0000007b)

Been migrating from Vmware to Hyper-V after my server crash. I was pretty damn impressed with Hyper-V. It’s extremely fast and easy to manage. It’s a great hypervisor, with the only draw back being the base OS taking just under 1GB of RAM. But that’s what you pay for to get a highly versatile virtualisation OS that will install onto any hardware.

Just a tip for those migrating from VMware to Hyper-V. It’s highly documented on the net that VMware uses SCSI hard drives to boot off (as this is what VMware suggests). Hyper-V only boots off IDE (even Hyper-V in 2008 R2).

To not get a STOP 0x0000007b BSOD error, you have to add a IDE hard drive into the virtual machine whilst it’s still running in VMware. Make sure you choose IDE Channel 1:0 or 1:1 as this installs the Primary IDE Channel. You probably already have a Secondary IDE Channel from the CDROM drive.

Last but not least, for me anyway I had to go to Computer Management and initialise the newly created IDE Hard Drive in VMware. I found that if I didn’t do this I’d end up with a BSOD in Hyper-V after the migration.

To summarise the steps in full (it’s been done a million times on the net already – but this is for those who want a one stop shop)

  1.  Uninstall VMware tools
  2. Shutdown virtual machine whilst it’s still in VMware
  3. Install an IDE hard drive on channel 1:0 or 1:1
  4. Startup the virtual machine
  5. Initialise the disk in Computer Management
  6. Shutdown virtual machine
  7. Convert from vmdk to vhd using the tool of your choice (I had most success with VDMKtoVHD from http://vmtoolkit.com/)
  8. Mount the image into Hyper-V
  9. Using the Legacy Network Card will allow the network to work without drivers but restricts you to 10/100.
  10. Otherwise, use the standard Network Card but make sure you install the Integration Services (requires SP2 or higher if you’re running Windows 2003 Server)
  11. You’ll probably get Service Failed to Start errors, so you’ll have to check in Event Viewer and teeth through those issues. Nothing is perfect right? Just keep in mind that it may be caused by some of the VMware Services still installed on the system (check in Service.msc). For some reason, the VMware Tools uninstall does not get rid of them all.

eTrust Threat Management Console (ITM) Password Reset

If anyone else is struggling to work out how to reset this password, hopefully this will help. It follows the local administrator password (NOT the domain administrator). So right-click on My Computer, choose Computer Management – Local Users and Groups. Reset the Administrator password there and you should be good to go.

For good measure, restart the following services:

  • eTrust ITM Server Service
  • eTrust ITM Web Access Service

Server Crash!

Just had a server crash. Think its faulty memory… caused a heap of corruption across all my virtual machines.

I’ll be updating this blog with the missing articles again!
Apologies about the downtime!

Update: Wasn’t memory in the end. Weirdest of problems… after replacing all the SATA cables in the server (RAID and CDROM drive), it all worked??? Craziest problem I think I’ve ever had! Was pulling my hair out trying to isolate the different combination of memory sticks and was about to scrap the server until the last ditch effort to try the SATA cables…

 FYI – the error that occured was that the Windows install kept on saying that the files were corrupt! I’d occasionally fluke an install, but when I blew everything away and tried to reinstall it again, I’d get the same error!