Receiving 80070570 error when attemting to write to RAID 5 array. Worked fine
for about 30 days, then constant 80070570 when attempting a write.
Array is SansDigital TRM5 with five 1Gb WD drives, using a Sil 3132 eSata
card.
Any ideas how to resolve the error? I really don't want to lose all of my
data again. That's why I went to RAID 5. :-(

Thanks

The 80070570 error is a WU error issue. I have no idea why you should be getting it
when trying to write to the Raid5

http://support.microsoft.com/kb/910359

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Mr.E.Man" <(E-Mail Removed)> wrote in message
news:9405503F-FBC4-4231-BB40-(E-Mail Removed)...
> Receiving 80070570 error when attemting to write to RAID 5 array. Worked fine
> for about 30 days, then constant 80070570 when attempting a write.
> Array is SansDigital TRM5 with five 1Gb WD drives, using a Sil 3132 eSata
> card.
> Any ideas how to resolve the error? I really don't want to lose all of my
> data again. That's why I went to RAID 5. :-(
>
> Thanks

I know it's wierd. Depending on what I am doing, I get several different
errors. If I try to delete a file, I get a message that says the file is no
longer on the drive. Then I get a message saying to run chkdsk because there
is corruption. When I run Chkdsk I get 73% through stage 2 of 3, then after
sitting for a minute, windows pops a screen saying chkdsk has stopped working.
I can't fix it by running chkdsk, and I don't know what tool I can use to
repair the damage. The drives and eSata card are all new. I assumed if I
received an error, it would be a bad drive and I could just replace it.
The failure is not on a system drive. The array is used to store data, not
OS or programs.

"Peter Foldes" wrote:

> The 80070570 error is a WU error issue. I have no idea why you should be getting it
> when trying to write to the Raid5
>
> http://support.microsoft.com/kb/910359
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "Mr.E.Man" <(E-Mail Removed)> wrote in message
> news:9405503F-FBC4-4231-BB40-(E-Mail Removed)...
> > Receiving 80070570 error when attemting to write to RAID 5 array. Worked fine
> > for about 30 days, then constant 80070570 when attempting a write.
> > Array is SansDigital TRM5 with five 1Gb WD drives, using a Sil 3132 eSata
> > card.
> > Any ideas how to resolve the error? I really don't want to lose all of my
> > data again. That's why I went to RAID 5. :-(
> >
> > Thanks
>
>

This is what the message means, ignore the 8007 part

Error 570 (1,392) The file or directory is corrupted and unreadable.

--
..
--
"Mr.E.Man" <(E-Mail Removed)> wrote in message
news:9405503F-FBC4-4231-BB40-(E-Mail Removed)...
> Receiving 80070570 error when attemting to write to RAID 5 array. Worked
> fine
> for about 30 days, then constant 80070570 when attempting a write.
> Array is SansDigital TRM5 with five 1Gb WD drives, using a Sil 3132 eSata
> card.
> Any ideas how to resolve the error? I really don't want to lose all of my
> data again. That's why I went to RAID 5. :-(
>
> Thanks

With what you just posted can only mean one thing. You are infected with some sort
of malware\trojan. Run your Anti Virus and a few on line ones also

Then SuperAntiSpyware
http://www.superantispyware.com/

Malwarebytes
http://www.malwarebytes.org/mbam.php

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Mr.E.Man" <(E-Mail Removed)> wrote in message
news:8BCAAD3E-1027-4944-B623-(E-Mail Removed)...
>I know it's wierd. Depending on what I am doing, I get several different
> errors. If I try to delete a file, I get a message that says the file is no
> longer on the drive. Then I get a message saying to run chkdsk because there
> is corruption. When I run Chkdsk I get 73% through stage 2 of 3, then after
> sitting for a minute, windows pops a screen saying chkdsk has stopped working.
> I can't fix it by running chkdsk, and I don't know what tool I can use to
> repair the damage. The drives and eSata card are all new. I assumed if I
> received an error, it would be a bad drive and I could just replace it.
> The failure is not on a system drive. The array is used to store data, not
> OS or programs.
>
> "Peter Foldes" wrote:
>
>> The 80070570 error is a WU error issue. I have no idea why you should be getting
>> it
>> when trying to write to the Raid5
>>
>> http://support.microsoft.com/kb/910359
>>
>> --
>> Peter
>>
>> Please Reply to Newsgroup for the benefit of others
>> Requests for assistance by email can not and will not be acknowledged.
>>
>> "Mr.E.Man" <(E-Mail Removed)> wrote in message
>> news:9405503F-FBC4-4231-BB40-(E-Mail Removed)...
>> > Receiving 80070570 error when attemting to write to RAID 5 array. Worked fine
>> > for about 30 days, then constant 80070570 when attempting a write.
>> > Array is SansDigital TRM5 with five 1Gb WD drives, using a Sil 3132 eSata
>> > card.
>> > Any ideas how to resolve the error? I really don't want to lose all of my
>> > data again. That's why I went to RAID 5. :-(
>> >
>> > Thanks
>>
>>

get PC Tools Spyware Doctor + Symantec AV