May 25, 2012 at 9:24 pm
Howdy,
I've installed a windows 2008 R2 (64 bit) 4 node cluster with node and disk majority mode. The cluster was tested successfully during the install. I've added a MSDTC resource and set Allow Remote Clients, Allow Remote Administration, Allow Inbound, Allow Outbound, Incoming Caller Authentication Required.
I have added around 30 other disks to be used for other MSDTC and SQL instance with mount points for data, log, tempdb, and log dumps.
I was going through the first install of the first SQL 2008 R2 instance on the first node and it's "hung" between the Feature Selection and Instance Configuration screen with the "Please Wait" message up. It's been a little over 2 hours now. The install was setup for slipstreaming SP1.
There's no CPU, or Network Utilization activity showing in Task manager that I can see. Although I've noticed that the Memory (Private Working Set) has ticked up by about 200k (currently 97500 k in use) over say the last 20 mins. So maybe it's not really hung.
My main question is how do I go about diagnosing what caused it to "hang" in the first place?
I've installed the same versions on a two node test cluster and except I was using Developer edition.
Any help is very appreciated!
May 26, 2012 at 1:55 am
Wow I am also facing the same issue for SQL 2012 Rc0 installation.
http://www.sqlservercentral.com/Forums/Topic1304837-1549-1.aspx
--------------------------------------------------------------------------------------------------
I am just an another naive wannabe DBA trying to learn SQL Server
May 26, 2012 at 3:49 am
Check your cluster validation report. Have you put all related disks for the mount pints into an app group and set the dependencies
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 26, 2012 at 7:58 pm
Thanks for the suggestion. I ended up finding the issue in the log folder of the bootstrap folder. For me this was C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log and then in the most recent folder there's a Detail.txt file that showed me the issue.
I had a drive that gets mapped when I login where the drive letter conflicted with the drive letter of the drive I had added into the cluster. The auto-mapped-at-login drive was of type FAT-32 and caused the hanging-ness.
Once I disconnected the offending drive all is now good and I'm progressing away with my installs.
May 27, 2012 at 6:46 am
Great, thanks for posting back
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 29, 2012 at 7:56 am
Not a problem, thanks for the suggestion. It got me thinking about logging in general.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply