I/O error (torn page) #823

I have recently had a drive failure (1 of 5 in a RAID 5 config). Along with
the drive failure, removing the faulty drive resulted in a registry failure
(Windows 200 Server SP4). So after pulling my hair out all day I, finally
restore the registry file,
and get back up with 4 of 5 drives running with a replacement on it's way to
morrow.
what a day but it's over right? of course not, I'm now getting an I/O error
(torn page) error when running some select statments.
Any suggestions as to the best way of handling this? Should I wait until a
get the fifth drive back? DBCC CHECKDB WITH REPAIR_BUILD ? I don't have
a real time back-up but could if necessary back up from last week and recrea
te the current week but wha
t a pain. Can/should I export the main datafiles to txt, recreate the table
s and import back in?
any suggestions would be greatly appreciated.
thanksAs far as I know, a torn page will always be deleted by DBCC CHECKDB with an
y repair option. If it is an index
page, you are lucky, as DBCC should be able to rebuild that index. If it is
a data page, you are not so lucky.
And if it is some allocation page (like an IAM page), you are not lucky at a
ll! All this is because the page
cannot be trusted so DBCC has to not only remove the page, but also pages th
at are dependent on that page.
I suggest you start with reading the general recommendations for a corrupt
database:
http://www.karaszi.com/sqlserver/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"graham" <anonymous@.discussions.microsoft.com> wrote in message
news:90FD4BA4-D1F6-4528-9BA0-97A1E8003004@.microsoft.com...
> I have recently had a drive failure (1 of 5 in a RAID 5 config). Along with the d
rive failure, removing the
faulty drive resulted in a registry failure (Windows 200 Server SP4). So af
ter pulling my hair out all day I,
finally restore the registry file, and get back up with 4 of 5 drives runnin
g with a replacement on it's way
tomorrow.
> what a day but it's over right? of course not, I'm now getting an I/O error (torn
page) error when running
some select statments.
> Any suggestions as to the best way of handling this? Should I wait until a get th
e fifth drive back? DBCC
CHECKDB WITH REPAIR_BUILD ? I don't have a real time back-up but could if
necessary back up from last week
and recreate the current week but what a pain. Can/should I export the main
datafiles to txt, recreate the
tables and import back in?
> any suggestions would be greatly appreciated.
> thanks|||No - torn page in non-clustered indexes will be deleted when the index is
rebuilt under any of the repair options. Any other kind of torn page can
only be fixed with REPAIR_ALLOW_DATA_LOSS.
You should move to new hardware and restore from a backup before considering
running repair (as your last resort).
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OHrU9DxFEHA.2976@.TK2MSFTNGP10.phx.gbl...
> As far as I know, a torn page will always be deleted by DBCC CHECKDB with
any repair option. If it is an index
> page, you are lucky, as DBCC should be able to rebuild that index. If it
is a data page, you are not so lucky.
> And if it is some allocation page (like an IAM page), you are not lucky at
all! All this is because the page
> cannot be trusted so DBCC has to not only remove the page, but also pages
that are dependent on that page.
> I suggest you start with reading the general recommendations for a
corrupt database:
> http://www.karaszi.com/sqlserver/in..._suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "graham" <anonymous@.discussions.microsoft.com> wrote in message
> news:90FD4BA4-D1F6-4528-9BA0-97A1E8003004@.microsoft.com...
with the drive failure, removing the
> faulty drive resulted in a registry failure (Windows 200 Server SP4). So
after pulling my hair out all day I,
> finally restore the registry file, and get back up with 4 of 5 drives
running with a replacement on it's way
> tomorrow.
error (torn page) error when running
> some select statments.
until a get the fifth drive back? DBCC
> CHECKDB WITH REPAIR_BUILD ? I don't have a real time back-up but could
if necessary back up from last week
> and recreate the current week but what a pain. Can/should I export the
main datafiles to txt, recreate the
> tables and import back in?
>|||Thanks for catching my mind-slip, Paul.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:OBsovo1FEHA.3540@.TK2MSFTNGP09.phx.gbl...
> No - torn page in non-clustered indexes will be deleted when the index is
> rebuilt under any of the repair options. Any other kind of torn page can
> only be fixed with REPAIR_ALLOW_DATA_LOSS.
> You should move to new hardware and restore from a backup before consideri
ng
> running repair (as your last resort).
> Regards.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:OHrU9DxFEHA.2976@.TK2MSFTNGP10.phx.gbl...
> any repair option. If it is an index
> is a data page, you are not so lucky.
> all! All this is because the page
> that are dependent on that page.
> corrupt database:
> with the drive failure, removing the
> after pulling my hair out all day I,
> running with a replacement on it's way
> error (torn page) error when running
> until a get the fifth drive back? DBCC
> if necessary back up from last week
> main datafiles to txt, recreate the
>