March 9, 2017 at 8:30 am
Ok I know we should be off of 2008 tied to vendor can't change this. Here is what I have
windows 2008 cluster, sql server 2008 active/passive cluster physical machine tied to SSD on SAN.
D Drive for Data (disk 5), G drive for Tempdb (disk 4)
Server stated slowing down with some unexplained problems. Needed to create new database on cluster. WHen tried to create on the D drive it told me drive was not part of disk resource or has no dependency cant create.
I went to dependencies and saw no disk five (I am including screen shot). I thought that this data drive (disk 5 should be listed)
Now the odd part the sql server is up and running and the database are available and running. Just can't backup or create to D drive. This seems like a no brainer but shouldn't the D drive (disk 5 be there). This server is ancient and so is the old SSD storage so almost everything is out of support
March 9, 2017 at 11:09 am
I've not done much (ie anything) with windows failover clustering,but that dependencies list doesn't look like it lists cluster disk 5 as being included in the failover.
As a guess, is disk 5 possibly running on your secondary?
Failing that, does your SQL Server Service and SQL Agent Service have the appropriate permissions to see and manipulate data on drive D?
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
March 10, 2017 at 7:07 am
tcronin 95651 - Thursday, March 9, 2017 8:30 AMOk I know we should be off of 2008 tied to vendor can't change this. Here is what I have
windows 2008 cluster, sql server 2008 active/passive cluster physical machine tied to SSD on SAN.
D Drive for Data (disk 5), G drive for Tempdb (disk 4)
Server stated slowing down with some unexplained problems. Needed to create new database on cluster. WHen tried to create on the D drive it told me drive was not part of disk resource or has no dependency cant create.
I went to dependencies and saw no disk five (I am including screen shot). I thought that this data drive (disk 5 should be listed)
Now the odd part the sql server is up and running and the database are available and running. Just can't backup or create to D drive. This seems like a no brainer but shouldn't the D drive (disk 5 be there). This server is ancient and so is the old SSD storage so almost everything is out of support
Drive D is a local disk on the Windows Server is it?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply