Hyper-V 2012 & boot-from-SAN - installation

Finally...a non-Miata post.

Had a devil of a time trying to get Hyper-V 2012 installed on one of our spare servers (HP DL360 G5).  Was installing from a DVD (iLO was not online originally) and using a USB key for the Qlogic drivers.  iSCSI HBA is a Qlogic 4062c.

Note this was an ESX 3.5 host when I started.

The error: "We couldn't create a new partition or locate an existing one. For more information, see the Setup log files."

Googling around gave me options...here is the order I tried them in:

  1. Boot off physical DVD, load drivers from USB
  2. Deleted old ESX partitions
  3. Got error
  4. Use repair function to clean drive and create/assign a new partition
  5. Got error
  6. Use the HP update DVD to bring firmware/BIOS up to date
  7. Got error
  8. Use iLO DVD image and USB key drivers (this was silly)
  9. Got error
  10. Checked inside server to ensure no USB devices plugged in (there were none)
  11. Removed USB key, attached USB key to PC, then to server via iLO as virtual device
  12. Got error
  13. Used 'bfi.exe' to build a floppy image, attached via iLO
  14. Successful installation!

Moral of the story:  You CANNOT have any USB devices attached in any way/shape/form when trying to install in a boot-from-SAN environment. (maybe any environment?)

Also...40GB is not enough, apparently wants 42GB (documentation says 32GB...?).  Just a warning.

Sources
* http://ixrv.blogspot.ca/2012/09/unable-to-install-windows-server-2012.html

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more