October 27, 2014 at 8:36 am
Hi All
I'm having issues installing SQL on one particular cluster.
This is installing on the first node of the cluster and I get the attached error message.
Simple googling returned to run setup as an administrator, which has been done but doesnt resolve the error.
I am a domain admin so there shouldn't be any permissions related issues, but as its complaining about System Volume Information it could well be something silly.
Anyone got any ideas?
Thanks
Ant
October 27, 2014 at 8:59 am
are you using mounted volumes for your shared disks or traditional drive letter based volumes?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 27, 2014 at 9:55 am
Traditional lettered drives I believe.
I didn't set the cluster up from a Windows perspective.
I tried making administrator be the owner of the file within SVI and that still didnt work (http://lokna.no/?p=1180)
October 27, 2014 at 10:03 am
anthony.green (10/27/2014)
Traditional lettered drives I believe.I didn't set the cluster up from a Windows perspective.
You'd soon know when you run the installer by the free volumes offered and the shared database install paths that will be offered.
Check which clustered roles are available\offered, have you pre staged the cluster role or are you creating a new one during install?
Which volumes were offered as part of the shared disk reources?
Screen shot?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 27, 2014 at 10:14 am
I was letting the install create the role, all of the shared volumes for backups data logs etc where presented to be selected at the shared disk selection.
It defaulted to K:\ as that was the backup volume. Switching it to F:\ for the area where to install the shared resources also resulted in the same error.
I will get screenshots of the install steps tomorrow, just removing the node from the cluster at the moment.
October 27, 2014 at 10:16 am
Double posted the above
October 28, 2014 at 12:33 pm
Anthony,
This may be a shot in the dark, but I encountered this same issue with mounted volumes (as mentioned above in another post). What I discovered was that even though I had all the permissions I was supposed to and so did the install account, the particular SAN I was installing to didn't agree. This also only began to happen to me installing to 2012 clusters.
I know you already mentioned changing the ownership, but just in case here's a similar walkthrough that helped me: http://www.derekseaman.com/2013/09/sql-2012-failover-cluster-pt-6-install-sql.html and go down to bullet 13.
Also, with my particular twitchy SAN I found I could get around this by installing to a folder on the mount point instead of the mount directly. YMMV on that but if your policy is flexible in install paths it's worth a shot.
October 28, 2014 at 1:06 pm
DB the DBA (10/28/2014)
I could get around this by installing to a folder on the mount point instead of the mount directly.
It's not a work around that's exactly what you're supposed to do, install to a folder under the mounted volume.
The reason is because Ntfs acls applied to a mounted volume do not get inherited by new subfolders and files.
See more in my article here[/url]
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 30, 2014 at 7:32 am
Sorry all, got this sorted, installed it to a subfolder rather than the root, strange how it was only this cluster that gave the error but all is now good.
Thanks
Ant
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply