SQL Server 2008 R2 SP1 Installation - The cluster disk device name is not valid

Question

Post reply

SQL Server 2008 R2 SP1 Installation - The cluster disk device name is not valid

nevhirion

SSC Veteran

Points: 295
More actions
September 26, 2011 at 2:38 am

#244402

Hi,
I am trying to update a fresh two-node SQL Server 2008 R2 cluster with Service Pack 1, but it fails. The Summary log in the Log folder shows this:-
Final result: The patch installer has failed to update the following instance: S1. To determine the reason for failure, review the log files.
Exit code (Decimal): -2067791871
Exit facility code: 1216
Exit error code: 1
Exit message: The patch installer has failed to update the following instance: S1. To determine the reason for failure, review the log files.
Start time: 2011-09-26 10:02:26
End time: 2011-09-26 10:11:44
Requested action: Patch
Instance S1 overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2067791871
Exit facility code: 1216
Exit error code: 1
Exit message: The cluster disk device name '' is not valid. Supported devices names include drive letters, OS object name, and volume IDs.
Start time: 2011-09-26 10:09:48
End time: 2011-09-26 10:11:41
Requested action: Patch
The cluster disks are all online and there are no issues failing them over from node to node. I then ran the Validate This Cluster (Windows Server 2008 R2) test and there is one test that is failing - List Cluster Volumes. I wonder if this has to do with the installation of SP1 failing.
All the validation report has to state is that
'An error occurred while executing the test.
The given key was not present in the dictionary.'
Has anyone faced this problem before? Any tips are greatly appreciated. Thanks.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

okbangas SSChampion Points: 11773 More actions · Answer 1

It may not be your exact problem, but I think this article will help you.

Ole Kristian Velstadbråten Bangås - Virinco - Facebook - Twitter

Concatenating Row Values in Transact-SQL[/url]

Perry Whittle SSC Guru Points: 234013 More actions · Answer 2

Try unpacking the SP to the local C drive and then execute the Setup from there

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

nevhirion SSC Veteran Points: 295 More actions · Answer 3

Thanks for your responses Guys.

Yeap, I did try the trick in the Symantec link, but it is still failing the List Cluster Volume test and the SP installation.

I was also installing the service pack from the local drive C:\ .

Perry Whittle SSC Guru Points: 234013 More actions · Answer 4

Is this a Windows cluster or a Veritas Cluster Server?

Are you saying that you saved the SP executable to the C drive and ran it from there?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

EdVassie SSC Guru Points: 60479 More actions · Answer 5

I have found problems when I install a SQL 2008 R2 cluster followed by applying SP1. What I always do now is build a slipstreamed install media set containing the SP and any CUs that are wanted.

If you use FineBuild to install your SQL cluster, it will dynamically build the slipstream media. It can also create the MSDTC cluster (or MSDTC clusters if you install more than one SQL cluster on W2008 /W2008R2).

The other thing you obviously need to do is check that you have the disks you need in either the Available Storage group or the cluster group you have specified for your SQL install. If one of the disks you need is in another cluster group then it cannot be used for the SQL cluster install.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

nevhirion SSC Veteran Points: 295 More actions · Answer 6

Hi,

It's a windows cluster. Yes, I saved the executable to C:\ and ran it from there.

The fix is already updated on the server.

Anyway, the installation succeeded. I have no idea what caused it to fail or to succeed now.

The last thing we did is this

http://connect.microsoft.com/SQLServer/feedback/details/381293/sql-express-2008-configuration-system-failed-to-initialize-0x84b10001

and it's still failing. But one fine morning, it just worked.

Thanks for the FineBuild link. Gonna try that the next round.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 7

nevhirion (9/27/2011)
Yes, I saved the executable to C:\ and ran it from there.

Ok, but that's not what I suggested you do. I suggested you unpack the SP using the /X: switch to a folder on the C drive and then run the SP setup from within the extracted folder. This forces setup to use the C drive during installation instead of some random cluster drive.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉