Skip to main content

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

Popular posts from this blog

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 configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally 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-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…