Trying to give something back to the Community...
If you ever need to perform any sort of disk maintenance on your Site Servers it’s always a good idea to stop the SMS Services BEFORE doing so as demonstrated by one user who decided to extend the drive on their SAN containing the Site Database of their Central without doing so first.
My understanding is that for some reason SMS decided it wanted to move the existing CAP that existed on a different drive onto the newly extended drive.
As soon as SMS “saw” the newly created disk it attempted to create the CAP which it couldn’t as the drive wasn’t fully operational at the time. As a result the Central ground to a standstill and none of it’s Child Primaries could communicate with it.
To resolve the issue the new CAP was removed and the Site Server rebooted.
I’ve asked if possible for more details so i can formulate this into a proper article but in the mean time here is the error they were seeing:
Possible cause: The destination drive is full.
Solution: Make more space available on that drive.
Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
Possible cause: SMS In box Manager does not have sufficient access rights to remotely administer the site system.
Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system.
Possible cause: Network problems are preventing SMS In box Manager from properly accessing the site system.
Solution: Investigate and correct any problems with your network.
If you ever need to perform any sort of disk maintenance on your Site Servers it’s always a good idea