Error 18204 on backup of Transaction log

I have used SQL Server 2005 Database Maintenance Plans to establish full backups and hourly transaction log backups. The jobs that stem from the DB Subplans run fine and report no errors when I view the history on them, however I have noticed the following error in my SQL Server error log. I am not seeing a similar error for my database backups, only the hourly log backups. Space is not an issue. Any guidance on this one would be greatly appreciated.

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

Error 18204 on backup of Transaction log

I have used SQL Server 2005 Database Maintenance Plans to establish full backups and hourly transaction log backups. The jobs that stem from the DB Subplans run fine and report no errors when I view the history on them, however I have noticed the following error in my SQL Server error log. I am not seeing a similar error for my database backups, only the hourly log backups. Space is not an issue. Any guidance on this one would be greatly appreciated.

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

sql

Error 17883 The Scheduler 0 appears to be hung:add information

After installing the 8.00.0818 patch i receive this error messages in the log
trying to schedule the backups at night, it occurs after approx three minutes
1. Error 17883 The Scheduler 0 appears to be hung
2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
continuing to wait.
3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
any suggestions
Best wishes
Hi
There was an issue with 818 see
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q826161 try patch to
819 or 878 http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
although I don't think this is necessarily causing your problem.
Check out http://support.microsoft.com/default...b;en-us;309093
Check the event log for any hardware related problems, particularly disc
errors. Look at perfmon for high disc queue lengths.
Try running DBCC CHECKDB.
John
"Mats" wrote:

> After installing the 8.00.0818 patch i receive this error messages in the log
> trying to schedule the backups at night, it occurs after approx three minutes
> 1. Error 17883 The Scheduler 0 appears to be hung
> 2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
> 1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
> continuing to wait.
> 3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
> any suggestions
> --
> Best wishes

Error 17883 The Scheduler 0 appears to be hung:add information

After installing the 8.00.0818 patch i receive this error messages in the lo
g
trying to schedule the backups at night, it occurs after approx three minute
s
1. Error 17883 The Scheduler 0 appears to be hung
2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
continuing to wait.
3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
any suggestions
--
Best wishesHi
There was an issue with 818 see
http://support.microsoft.com/defaul...scid=kb;[LN];Q826161 try patch
to
819 or 878 http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
although I don't think this is necessarily causing your problem.
Check out http://support.microsoft.com/defaul...kb;en-us;309093
Check the event log for any hardware related problems, particularly disc
errors. Look at perfmon for high disc queue lengths.
Try running DBCC CHECKDB.
John
"Mats" wrote:

> After installing the 8.00.0818 patch i receive this error messages in the
log
> trying to schedule the backups at night, it occurs after approx three minu
tes
> 1. Error 17883 The Scheduler 0 appears to be hung
> 2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, pag
e
> 1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
> continuing to wait.
> 3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
> any suggestions
> --
> Best wishes

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I ca
n
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have th
e
same problem? Or maybe deleting the existing maintenance plan and creating i
t
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected database
s
> running at regular intervals through SQLAgent. The backups are working; I
can
> restore the databases. But starting a few weeks ago we've been getting err
or
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backup
s
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage
)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Serve
r
> "ERRORLOG" text file also contains no error messages in connection with th
e
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestion
s
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have
the
> same problem? Or maybe deleting the existing maintenance plan and creating
it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried runnin
g
> the package manually from SSIS (like using the Execute Package Utility) an
d
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
>|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:
> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
> > We have a maintainance plan for full/diff/log backups of selected databases
> > running at regular intervals through SQLAgent. The backups are working; I can
> > restore the databases. But starting a few weeks ago we've been getting error
> > messages in the system event log.
> >
> > First, there's an entry confirming the successful completion of the backups
> > with ID 18265 (source MSSQL$...)
> > Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> > followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> > Error ..." (source SQLAgent$...)
> >
> > As I said, the backups themselves seem to be successful, and the SQL Server
> > "ERRORLOG" text file also contains no error messages in connection with the
> > plans.
> >
> > This is still worrying us a bit, because we fear there might be a good
> > reason for these error messages, and obviously we want to be quite certain
> > that our backups are working properly and will be available if and when we
> > need them.
> >
> > Does anyone have any insight/advice on Error 12291?
> >
> > Thanks
> > Tom Juergens|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:
> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom Juergens
Hi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>

error

Hi

The company I currently work for backups its SQL databases by

dumping them into a shared folder on nearby sysem. Once in a blue moon

the following error appears on the screen of the SQL server:

Windows - Delayed Write Failed

Windows was unable to save all the data for the file

\Device\LanmanRedirector\10.100.20.7\backup\logs\DB backup 4 hour cycle to remotesrv

storage4_200608150615.txt. The data has been lost. This error may be caused by

a failure of your computer hardware or network connection. Please try to save

this file elsewhere.

There are other processes that talk to other shares (on the same drive

on the same remote system) and none of them gives me the above

error. What more both systems are on the same LAN and IP subnet that is

very lightly used. The network cables are all high grade CAT6

cable (machine cripmed). I'm not a windows/SQL

Administrator (Unix is my background), so if I'm asking the wrong

questions in the wrong forum please kindly redirect me to the right

forum.

Why does this error popup?

TIA

Paolo

One place you might try is to take a look at the Array Controller Read/Write Cache ratio on the target server. If the controller is set to 100% Read, this type of error could happen. You could also take a look at the array controller on the server initiating the backups. The controller should never be set to 100% Read, although even though it may be, it doesn't allow no Write caching. However, if there is too much data being written to the array and there isn't enough Write cache, you could experience the type of failures you are seeing. Also make sure there are no failed disks in the array. You may also want to make sure that all of the storage drivers are up to date as well.