Cluster validation error – the wrong diskette is in the drive

While configuring a new MSCS Cluster in VMware ESXi 5.1 I encountered the following error when running the Cluster Validation Tool:

The wrong diskette is in the drive
Insert %2 (Volume Serial Number: %3) into drive %1.

I was very surprised to see an error indicating that the problem was with a diskette. Obviously this wasn’t right, my suspicion was that it was storage related so I requested a SAN Engineer to take a closer look. The cursory checks were made such as ensuring PR (Persistent Reservations) was set on the LUN but no glaringly obvious causes were identified.

After trying a few things (and failing) I ‘cleaned’ the clustered disks, which fixed the problem. This involved converting the disks from GPT to MBR and then back again. The following steps  were performed:

  1. Open Disk Management by running diskmgmt.msc from a command prompt
  2. The disk contained a volume, so right-clicked on the volume (within the disk) and then clicked Delete Volume.
  3. Right-clicked the GPT disk and then clicked Convert to MBR disk.
  4. Once the disk had converted to MBR I right-clicked on it and then clicked Convert to GPT disk.

I then re-ran the Cluster Validation Test and it passed successfully!

Reference:
Change a GUID Partition Table Disk into a Master Boot Record Disk
Change a Master Boot Record Disk into a GUID Partition Table Disk

WordPress theme update fails with ‘Could not remove the old theme..’

I finally got round to updating WordPress to version 3.4.2. This went smoothly. I then tried to update the Twenty Eleven and Twenty Ten themes to version 1.4 and was met with the following error:

An error occurred while updating Twenty Eleven: Could not remove the old theme..

A screenshot of the error is below:

We can see that the updates downloaded successfully so we know that the IIS worker process has write permissions. The updates failed at the ‘removing the old version of the theme stage’ which indicated that the IIS worker process did not have permissions to delete the \themes\twentyeleven folder.

A quick check confirmed this. So I added the modify permissions for the IIS worker process account to the themes folder:

I then re-ran the theme update process and it was successful because the IIS worker process was able to delete the older Twenty Eleven theme folder:

I now have up-to-date WordPress themes. The same principle applies for plugin updates – just modify the relevant plugin directory and give the IIS worker process modify permissions and updates will run successfully.