We recently ran into this same issue. At the time the best advise we found was to "...wait and retry starting the sql server server after a few minutes...", seems...