In our case, the error was due to the fact that MS SQL Server Agent engine was waiting for the MS SQL Server Engine to complete ‘system database recovery’.
Due to Hardware RAID Error, the system keep shutting down and restarting. Each time it does so, the SQL Engine needed to rollback a particularly scheduled ETL job.
Suggestively, MS SQL Server does not allow the SQL Agent Engine to fully start and resume usage activity until ‘all’ databases are ‘recovered’ and marked operational or ‘suspect’.
MS Literature and Web based SQL Forums also suggests that MS SQL Server Agent may experience this problem when MS SQL Server is running in Fiber mode.