OT: SQL Data on RAID5 Missing disk?

My SQL data is on a software Raid5 partition on my Windows Server 2003
Enterprise.
It appears one of my disks is not coming up and another disk is reported as
"Missing" so my SQL data is not being found!!
There is another disk that nows shows up as Unknown and uninitialized. Is
this my "missing" disk?
How do I recover from this without losing my data on the Raid?
Any help would be appreciated!!!
Attached is what it looks like in Disk Manager.
I tried to "Reactivate" the "Missing" disk but that didn't work and a bunch
of events in the System log
"The device detected a controller error on \device\harddisk1".
And there are alos informational events in the system log for harddisk3 such
as:
"dmio: Harddisk3 write error at block:145743940: status 0xc00000a2"
So it appears that one drive is just physcially dead I guess and another is
corrupted.
I'm starting to panick because our backups the the SQL are old...
Is there any safe way to recover from this situation?
"news.microsoft.com" <junk@.ijunk.com> wrote in message
news:eDwuW39DHHA.3520@.TK2MSFTNGP04.phx.gbl...
> My SQL data is on a software Raid5 partition on my Windows Server 2003
> Enterprise.
> It appears one of my disks is not coming up and another disk is reported
> as
> "Missing" so my SQL data is not being found!!
> There is another disk that nows shows up as Unknown and uninitialized. Is
> this my "missing" disk?
> How do I recover from this without losing my data on the Raid?
> Any help would be appreciated!!!
>
|||"news.microsoft.com" <junk@.ijunk.com> wrote in message
news:#oKeSA#DHHA.1196@.TK2MSFTNGP02.phx.gbl...
> Attached is what it looks like in Disk Manager.
> I tried to "Reactivate" the "Missing" disk but that didn't work and a
> bunch of events in the System log
> "The device detected a controller error on \device\harddisk1".
> And there are alos informational events in the system log for harddisk3
> such as:
> "dmio: Harddisk3 write error at block:145743940: status 0xc00000a2"
> So it appears that one drive is just physcially dead I guess and another
> is corrupted.
> I'm starting to panick because our backups the the SQL are old...
> Is there any safe way to recover from this situation?
>
You full database backups are old. Do you have an unbroken sequence of
transaction log backups dating from your last full backup?
David
|||I don't think so, but I'm not sure.
The Raid that failed is my D drive where my SQL database was located.
Are you saying there might be transaction logs on the C drive somewhere?
The last backup was months ago.
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ujOYcT%23DHHA.4680@.TK2MSFTNGP04.phx.gbl...
>
> "news.microsoft.com" <junk@.ijunk.com> wrote in message
> news:#oKeSA#DHHA.1196@.TK2MSFTNGP02.phx.gbl...
> You full database backups are old. Do you have an unbroken sequence of
> transaction log backups dating from your last full backup?
> David
|||>>> On 11/24/2006 at 9:50 AM, in message
<#AWC5i#DHHA.4464@.TK2MSFTNGP06.phx.gbl>,
news.microsoft.com<junk@.ijunk.com> wrote:
> I don't think so, but I'm not sure.
> The Raid that failed is my D drive where my SQL database was
> located.
> Are you saying there might be transaction logs on the C drive
> somewhere?
> The last backup was months ago.
If the data truly is important, don't risk screwing things up more by
trying things yourself unless you are *extremely* confident in your own
skills.
This is the time to pay someone who knows what they are doing.
Otherwise you risk turning a possibly recoverable scenario into a
non-recoverable scenario.
MS PSS might be a good place to start, as might your hardware vendor.
Make sure you explain that you don't have backups, so you want to be
very careful not to do anything that is likely to cause more problems.
|||Check Tibor's article:
Minimizing data loss when accidents happens
http://www.karaszi.com/SQLServer/info_restore_log_several_times.asp
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"news.microsoft.com" <junk@.ijunk.com> wrote in message
news:%23AWC5i%23DHHA.4464@.TK2MSFTNGP06.phx.gbl...
>I don't think so, but I'm not sure.
> The Raid that failed is my D drive where my SQL database was located.
> Are you saying there might be transaction logs on the C drive somewhere?
> The last backup was months ago.
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:ujOYcT%23DHHA.4680@.TK2MSFTNGP04.phx.gbl...
>
|||news.microsoft.com wrote:
> I don't think so, but I'm not sure.
> The Raid that failed is my D drive where my SQL database was located.
> Are you saying there might be transaction logs on the C drive somewhere?
> The last backup was months ago.
>
Painful as it may be, I suggest you first get someone on site who knows
what they are doing. Obviously a lot of damage has already been done
and now your data is at risk.
Except for a read-only database, RAID5 is not a great choice for a
database server because of the performance and availability
constraints.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||Well, I physically went to the server and found one disk on boot sounded
like two stones grinding on each other at 10k RPM...
The other failed disk just says "Media Error" on the Adeptec BIOS boot
discovery.
If I could find some temporary way of getting this drive to work for like 10
minutes then I could copy out the database.
Any ideas?
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1164397255.045467.37770@.f16g2000cwb.googlegro ups.com...
> news.microsoft.com wrote:
> Painful as it may be, I suggest you first get someone on site who knows
> what they are doing. Obviously a lot of damage has already been done
> and now your data is at risk.
> Except for a read-only database, RAID5 is not a great choice for a
> database server because of the performance and availability
> constraints.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>