Ok,
This is my last resource, prior opening an actual case with Microsoft. I've researched and looked everywhere without finding any possible explanation, so I am crossing my fingers I will here.
1st, I should clarify my instance is Cluster aware and running SQL2012.
The issue started or I noticed it, after few planned failovers due an scheduled Cluster's patch for an iSCSI / SAN issue. Everytime I try to move the whole SQL failover instance, all resources come online on the other node but the SQL one. It stays online for
a few seconds and then go down again. Here's the SQL log error:
2013-05-22 17:42:40.72 spid11s Error: 1205, Severity: 13, State: 35.
2013-05-22 17:42:40.72 spid11s Transaction (Process ID 11) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
2013-05-22 17:42:40.72 spid11s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event
log that may indicate why the tempdb files could not be initialized.
2013-05-22 17:42:40.72 spid11s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2013-05-22 17:42:41.11 Logon Error: 18456, Severity: 14, State: 38.
tempdb_data LUN is 250GB and it is currently using 20GB of that. tempdb_logs is 200GB and it is using 12GB only. I also kept an eye on those numbers for about a week and they remain the same. Upper limit was set to unlimited so if they have to growth after
a restart, they can. So the lack of temdpb space makes no sense to me.
I checked instant file initialization and SQL service is added to the local policies there.
SQL 2012 is running on top of Windows 2008R2.