2008 R2 troubles continued, but solved

Once I got the disk portion working, it failed at the 'Copying files' part, got to between 15 and 40%, then gave an error (0x80070750 - files missing). I burned another DVD at 4x speed, same error. I re-downloaded the ISO, checked the SHA-1 hash, and burned another DVD at 4x speed. Same error. I made one of my USB sticks an install disc (http://myitforum.com/cs2/blogs/bbird/archive/2008/10/01/making-a-usb-stick-bootable-for-vista-or-server-2008.aspx , an excellent post, btw), and STILL the same error.

At this point I was pretty frustrated. There was no way it was install media-related...so back to the basics. I pulled all the expansion cards and did more googling. I came up with someone mentioning that over 4GB of RAM caused their Win7 install to fail. Win7 and 2008 R2 are similar, so I pulled 3 of the 6GB RAM I had installed (2x2,2x1). Bingo!! Installed 100% from there.

Pretty dumb problem...especially since it's an x64-only OS.

The hardware I'm using is most likely the culprit: Asus P5E-VM HDMI with the 0604 BIOS

At any rate...all good now.

Comments

  1. UnknownDecember 22, 2010 at 3:14 AM

    Same problem was when I was trying to install the SBS 2011 on a 8GB system with ASUS P5Q.
    Removing my extra 4GB solved it after several hours of trying.....
    Thanks!!!

    ReplyDelete
  2. ErichApril 20, 2011 at 1:27 AM

    I have the same problem installing SBS2011 as a virtual machine under Hyper-V 2008R2 SP1 or under VmWare ESX1 4.1. Any solutions ?

    ReplyDelete

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