Tag Archive for Intel

Looking Forward to Storage Field Day 9 (#SFD9)

Storage Field Day

So for those of you who love to nerd out on storage like I do, you have probably already heard of the awesome streaming events put on by Stephen Foskett and the crew from Tech Field Day, otherwise known as Storage Field Day. These have grown so popular that Stephen is having to put on extra events just to cater for demand, which I think speaks volumes as to their efficacy and indeed quality!

For those not yet indoctrinated, these events involve taking a group of around a dozen storage and technology delegates to visit a number of different startups (think Pure, NexGen, Coho, etc) and more established companies (think Intel!) to talk about the latest things going on both at those organisations and in the industry in general. Each session lasts a couple of hours, but is generally broken down into several bite sized chunks for consumption at your leisure.

As a stream viewer you get the opportunity to learn about your favourite vendors latest funky stuff and watch them answer questions about all the things you probably wanted to know but never got the chance to ask. It is also a great way to get your head around an unfamiliar technology or vendor. Lastly, if you watch live, you can also ask questions via twitter for the delegates to ask of the presenters.

As a delegate this goes to a whole new level as you get to spend almost an entire week mahoossively geeking out on tech, learning from some of the smartest people in the tech industry, and meeting with the senior people at some of the industry’s best-known companies. I find it generally safest just to wear multiple layers to avoid any embarrassing nerdgasms! ūüėČ

So with that in mind I am really chuffed to have been invited back to attend Storage Field Day 9, next month (16th-18th March) in San Jose!

Not all of the companies have been announced as yet, but we already know that the likes of Cohesity, Intel, VMware & Violin Memory will be in attendance. More will be confirmed over the next coupe of weeks and having seen the provisional list I can tell you it is definitely going to be a great event!

vendors

Needless to say the lineup of delegates is awesome as usual, with many well known bloggers from the EU, US and APAC. Make sure you check them out and follow the crew on twitter if you are so inclined. Most delegates post their opinions around the vendors and tech both during and after the event, so make sure you check out their blog feeds. For example, here is mine:

http://www.tekhead.org/blog/feed/

If you want to tune in live, simply go to http://techfieldday.com from 16th-18th March (PST) or catch up with the recordings on youtube later.

Finally, be warned my Twitter stream does get rather busy during the event, so feel free to temporarily mute me if need be! ūüėČ

NanoLab – Part 10 – Your NUCs are nice and cool, but what about your stick?

I have been running a variety of Intel NUC nodes in my vSphere homelab over the past 3 years now, including the D34010WYKH, DC3217IYE & DC53427HYE.

In that time I have unfortunately seen more than my fair share of USB drive failures and corruptions, generally with an error which looks something like this:

Error loading /k.b00
Fatal error: 33 (Inconsistent data)

 
These are not cheap and nasty, or freebie USB drives, so I would not normally expect to see this rate of failures. The error only occurs when you reboot the host, and the startup bombs out at the start of the hypervisor launch. I have often managed to recover the stick by copying back corrupted files from another instance, but generally I needed to rebuild and restore the image. An unnecessary pain in the rear!

The Root Cause
The NUC case can become quite warm during normal operation with or without the fans spinning up, and I have come to believe that the main reason for the corruptions is that the USB stick itself is getting too hot and therefore eventually failing. Having pulled a USB out from a recently shut down node, they are really quite hot to the touch. You don’t actually see the symptom / failure until a reboot because the ESXi image actually runs in memory, so is only loaded from the USB stick at boot time.

The Solution
As for the solution, it’s really quite simple. I purchased a number of 12cm (5 inch) USB 2.0 extender cables on eBay for just 99p each (including delivery!).

These keep the USB stick indirectly attached to the NUC chassis, and as such the heat does not transfer into the flash drive. Since doing this I have not seen any further issues with the corruptions. Job done!

Keeping things cool: USB extender on Intel NUC

Keeping things cool: USB extender on Intel NUC

NanoLab – Part 9 ‚Äď Installing VMware vSphere ESXi 5.5 on Intel NUC

I successfully ran my VMware vSphere ESXi 5.1 Nanolab for 18 months on my pair of Intel NUC DC3217IYE hosts. Early this year I got around to upgrading to 5.5. I had experienced some issues with my vCenter Server Appliance so ended up just rebuilding the lab from scratch and reattaching my old data stores. Having written all of this up, I then promptly forgot to post it! So for the sake of continuity (before I do the same for 6.0 shortly), this article covers the process.

In addition I also purchased a 3rd node for my lab, the 4th Gen D34010WYKH model (also with a Core i3), with which I was able to test and prove the process on as it uses the same NIC chipset.

The following are updated instructions for installing vSphere 5.5 on Intel NUC (any model with the¬†Intel¬ģ 82579V or Intel¬ģ I218V onboard NIC should work).

I recommend before you start, you upgrade the NUC¬†to the latest firmware, to avoid any potential bugs (of which there were a few when they were first released). Copy the latest firmare image onto a USB stick, boot the NUC, hit F7 at the bios, find your firmware on the USB stick and let it do it’s thing:

Intel NUC Firmware Upgrade

Intel NUC Firmware Upgrade

vSphere 5.5 Install Requirements

  • A USB Stick. This should work on anything over 1-2GB but personally am using 8GB PNY Micro Sleek Attache & 16GB Kinston DataTraveler Micro drives as they’re tiny, so less likely to catch on anything as they stick out the back of the NUC box, and they cost less than ¬£5 each.
  • A copy of VMware Workstation 8 / Fusion 6 or newer.
  • ESXi-Customizer 2.7.2 (created by Andreas Peetz)
    http://v-front.blogspot.com/p/esxi-customizer.html¬†for adding VIBs to your image. NOTE: This can also be done by Powershell, but I like the GUI as it’s easy! (http://blogs.vmware.com/vsphere/2012/04/using-the-vsphere-esxi-image-builder-cli.html)
  • The ESXi driver for the¬†Intel¬ģ 82579V Gigabit Ethernet Controller¬†(e.g. for the original¬†models using ESXi 5.5):
  • OR The ESXi driver for the¬†Intel¬ģ I218V Gigabit Ethernet Controller (e.g. for the Haswell based D34010U models):
  • (AND) The ESXi AHCI driver for the SATA controller (if you want to use local drives in the¬†¬†Haswell based D34010U models):
    • sata-xahci-1.10-1.x86_64
    • If you do choose to add this in as well to your image, simply run the customiser twice, once for the network VIB, then a second time for the SATA vin, using the interim image as your source for the final image.

Process Overview

  • Create a customised ISO with the additional Intel driver.
  • Install ESXi to your USB stick using VMware Workstation / VMware Fusion and the customised ISO you will create below.
  • Plug in your NUC, insert the USB stick, boot and go!

Part One – Create the Custom ISO

  1. Run the ESXi-Customizer-v2.7.2.exe (latest version at time of writing).
  2. This will extract the customer to the directory of your choosing.
  3. Navigate to the new directory.
  4. Run the ESXi-Customizer.cmd batch file. This will open up the GUI, where you can configure the following options:
  • Path to your ESXi Installer
  • Path to the Intel driver downloaded previously
  • Path where you want the new ISO to be saved
  1. Ensure you tick the Create (U)EFI-bootable ISO checkbox.
ESXi-Customizer with 2.3.2 vib

ESXi-Customizer with 2.3.2 vib

This will output a new custom ESXi installer ISO called ESXi-5.x-Custom.iso or similar, in the path defined above.

Part Two – Install bootable ESXi to the USB stick.
I stress that this is my preferred way of doing this as an alternative is simply to burn your customised ISO to a CD/DVD and boot using a USB DVD-ROM. That would however be a whole lot slower, and waste a blank CD!

  1. Plug your chosen USB stick into your PC.
  2. Open VMware Workstation (8 or above), VMware Fusion, or whatever you use, ideally supporting the Virtualize Intel VT-x/EPT or AMD-V/RVI option (allowing you to nest 64-bit VMs).
  3. Create a new VM, you can use any spec you like really, as ESXi always checks on boot, but I created one with the similar¬†specs as my intended host, single socket, 2vCPU cores. RAM doesn’t really matter either but I use at least 4GB normally. This does not require a virtual hard disk.
  4. Once the VM is created, and before you boot it, edit the CPU settings and tick the Virtualize Intel VT-x/EPT or AMD-V/RVI checkbox. This will reduce errors when installing ESXi (which checks to ensure it can virtualise 64-bit operating systems).

VMware Workstation Nesting

Screen Shot 2014-08-29 at 22.09.01

VMware Fusion Nesting

  1. Set the CD/DVD (IDE) configuration to Use ISO image file, and point this to the customised ISO created earlier.
  2. Once the above settings have been configured, power on the VM.
  3. As soon as the VM is powered on, in the bottom right of the screen, right click on the flash disk icon, and click Connect (Disconnect from Host).

Attach USB in VMware Workstation

Screen Shot 2014-08-29 at 21.38.18

Attach USB in VMware Fusion

  1. This will mount the USB stick inside the VM, and allow you to do a standard ESXi installation onto the stick.
ESXi Install

ESXi Install

  1. At the end of the installation, disconnect the stick, un-mount and unplug it.
Install Complete

Install Complete

Part Three – Boot and go!
This is the easy bit, assuming you don’t have any of the HDMI issues I mentioned in the first¬†post!

  1. Plug your newly installed USB stick into the back of the NUC.
  2. Don’t forget to plug in a network cable (duh!) and keyboard for the initial configuration. If you wish to modify any bios settings (optional), you will also ideally need a mouse as the NUC runs Visual BIOS.
  3. Power on the NUC…
  4. Have fun!

That’s it!

Any questions/comments, please feel free to hit me up on twitter as I have recently disabled comments on my blog due to the insane volumes of spam bots they were attracting!

Quick Tip: Install a VIB into an Existing vSphere 5.5 ESXi Host

The following will likely work in other versions of vSphere, but I used it in vSphere 5.5 a while ago, then forgot to hit publish on this post!

In that case I had installed a new ESXi host and not included the custom VIB with the drivers for the SATA card. I did this deliberately as I thought I would have no need at this time to use the local HBA. The thing I forgot is that the host profiles I had created from other hosts included a local HBA, therefore the host profiles would not remediate without one. Annoying! So I used the following steps to manually add the specific VIB I needed (in this case sata-xahci-1.10-1.x86_64.vib).

SSH to your ESXi host (having enabled the SSH server from the vSphere Client):

# ssh [email protected]<hostip>
# cd /tmp

 

Copy the vib file into the host image (in my case I had it stored on my web server, but you could equally use any other standard method to get the file onto the host):

# wget http://www.tekhead.org/wp-uploads/www.tekhead.org/sata-xahci-1.10-1.x86_64.zip

 

Unzip the vib file:

# unzip sata-xahci-1.10-1.x86_64.zip

 

Install the vib:

# esxcli software vib install -v file:/tmp/sata-xahci-1.10-1.x86_64.vib
 
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VFrontDe_bootbank_sata-xahci_1.10-1
VIBs Removed:
VIBs Skipped:

 

Check that the vib is installed:

# esxcli software vib list | grep -i <vib name in my case ahci>
sata-xahci   1.10-1   VFrontDe   CommunitySupported   2014-10-31

 

Remove the old files (no longer needed):

# rm sata-xahci-1.10-1.x86_64.*

 

Finally, reboot your ESXi host, job done!

 

%d bloggers like this: