Data Recovery - why do they let the damaged HD run all nig..

Previously David D <netrate.RemoveThis@yahoo.com> wrote:
> Data Recovery - why do they let the damaged HD run all night?

> I talked to a Data recovery house and they told me they sometimes have
> to let the drive run all night - why is that? Won't that cause more
> damage?

> Also, they tell me that it sounds like it might be internal problems
> (The drive is seen in the Bios after about 10 minutes of the motor/
> chirping cycling up and down), so how is running the drive all night
> going to help? Is this something I should do first?

1) Don't do this yourself
2) I expect that they do this in special circumstances or after
repairs only.

Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

Previously sean.RemoveThis@easyrestore.co.uk wrote:
> If the drive has bad sectors it might take numerous read attempts
> before the data from that sector gets correctly read - this is what
> takes the time.

> Drives that have failing motors or crashed heads would not be run in
> that condition for extended periods of time as that would probably
> just distroy the data.

About what I thought. Makes eminently sense, but requires a correct
diagnosis before doing it.

Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

"Arno Wagner" <me.TakeThisOut@privacy.net> wrote in message news:5ef16kF38tfk4U1@mid.individual.net
> Previously sean.TakeThisOut@easyrestore.co.uk wrote:
> > If the drive has bad sectors it might take numerous read attempts
> > before the data from that sector gets correctly read - this is what
> > takes the time.
>
> > Drives that have failing motors or crashed heads would not be run in
> > that condition for extended periods of time as that would probably
> > just distroy the data.

> About what I thought.

Easy claim, babblebot.
If that's what you thought, then that's what you would have said.

> Makes eminently sense, but requires a correct diagnosis before doing it.

Another deadbeat.

>
> Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

>
> Easy claim, babblebot.
> If that's what you thought, then that's what you would have said.
>
>
> Another deadbeat.
>

And on what basis have you made these comments?

Sean Moore
www.easyrestore.co.uk
Professional Data Recovery
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

David D <netrate.RemoveThis@yahoo.com> wrote:

> Data Recovery - why do they let the damaged HD run all night?

Because it can take that long to get the data off it.

> I talked to a Data recovery house and they told me they sometimes have
> to let the drive run all night - why is that? Won't that cause more damage?

Depends on the fault. If its just a cracked trace or dry joint, not necessarily.

> Also, they tell me that it sounds like it might be internal
> problems (The drive is seen in the Bios after about 10
> minutes of the motor/chirping cycling up and down),

Thats the drive recalibrating.

> so how is running the drive all night going to help?

If it takes a lot of retrys to get the data successfully, that can take that long.

> Is this something I should do first?

Nope, and you shouldnt do anything first if you want to maximise the chances of recovery.
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

sean.RemoveThis@easyrestore.co.uk wrote:
>> Easy claim, babblebot.
>> If that's what you thought, then that's what you would have said.
>>
>>
>> Another deadbeat.
>>
>
> And on what basis have you made these comments?

The problem he has between his ears.

Look at his posting history, pathetically bitter and twisted.
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

"Rod Speed" <rod.speed.aaa DeleteThis @gmail.com> wrote in message news:5ehb1mF394ejfU1@mid.individual.net
> sean DeleteThis @easyrestore.co.uk wrote:
> > > Easy claim, babblebot.
> > > If that's what you thought, then that's what you would have said.
> > >
> > >
> > > Another deadbeat.
> > >
> >
> > And on what basis have you made these comments?

> The problem he has between his ears.

Bwahahah. This coming from
Roddles " pity about 0 bad sectors are bad in a new drive" Speed.

" > There are no reallocated sectors reported,

Wrong, pity about

5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0

> and IMHO, this is the key value to watch for impending failure.

It is indeed, and that many in a new drive is a real problem."

>
> Look at his posting history, pathetically bitter and twisted.

Must be why some people accidentally mistake him for being you,
isn't that so, Roddles.
Strange then how he still hasn't got a website devoted to him, like
you have, huh.
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

Previously sean.DeleteThis@easyrestore.co.uk wrote:
>>
>> Easy claim, babblebot.
>> If that's what you thought, then that's what you would have said.
>>
>>
>> Another deadbeat.
>>

> And on what basis have you made these comments?

Folkert resents anything I say, since I am not intimidated by him.
(By now I expect nobody here is...). My advice is to ignore him.

BTW, I have not seen you posting here before. Welcome! You will
find the content here is mixed, but there are quite a few good
contributions and you get to hear about new problems with storage
pretty early.

Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

"Arno Wagner" <me.DeleteThis@privacy.net> wrote in message news:5ekj4aF38i38lU3@mid.individual.net
> Previously sean.DeleteThis@easyrestore.co.uk wrote:
> > >
> > > Easy claim, babblebot.
> > > If that's what you thought, then that's what you would have said.
> > >
> > > Another deadbeat.
> > >

> > And on what basis have you made these comments?

If you go back to the original post you can read what you snipped and find
out for yourself, Troll.

> Folkert resents anything I say, since I am not intimidated by him.

Actually, the git isn't even strong enough for that. It needs a killfile to keep
it from reading about it's ongoing stupidity and from going into complete in-
sanity. It's glued to it's PC, day *and night*, so it can answer *each and every*
question *first*, before anyone else can, whether it knows anything about
the subject or not makes no difference. It must have major low esteem
issues to go that far in trying to please everyone and think good of itself.

> (By now I expect nobody here is...).

> My advice is to ignore him.

Babblebot, the advisor.

>
> BTW, I have not seen you posting here before. Welcome!

> You will find the content here is mixed,

Thanks to our babblebot when he is sleeptyping behind his keyboard again.

> but there are quite a few good contributions and you get
> to hear about new problems with storage pretty early.

Babblebot, c.s.i.p.h.s. chairman .... err chairgit.

>
> Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

Previously Bugs <Bugs.RemoveThis@bunny.oz> wrote:
> "Arno Wagner" <me.RemoveThis@privacy.net> wrote in message news:5ekj4aF38i38lU3@mid.individual.net
>> Previously sean.RemoveThis@easyrestore.co.uk wrote:
>> > >
>> > > Easy claim, babblebot.
>> > > If that's what you thought, then that's what you would have said.
>> > >
>> > > Another deadbeat.
>> > >

>> > And on what basis have you made these comments?

> If you go back to the original post you can read what you snipped and find
> out for yourself, Troll.

>> Folkert resents anything I say, since I am not intimidated by him.

> Actually, the git isn't even strong enough for that. It needs a
> killfile to keep

Hehe. That is also called a "noise reducer". Pretty pathetic that you
seem to desparately want me to see your postings. For all the other
posters you could just post normally, but for some reason it seems to
bug you that I do not even spare you the attention of seeing your
posts. Now here is a little attention for you, since I am in a good
mood. Bask in it. It will not last.

Arno
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

In news:1182898328.040198.239320@m36g2000hse.googlegroups.com David D wrote:

> Data Recovery - why do they let the damaged HD run all night?
> I talked to a Data recovery house and they told me they sometimes have
> to let the drive run all night - why is that? Won't that cause more
> damage?

Hi David, that's also my experience!
Windows needs much extra times to recover from faulty sectors!
e.g. on a Win98SE system with a faulty boot HDD it takes sometimes
about 2 HOURS before the Boot completes!
Then it tells me the HDD ist ok, but on the next ReBoot it takes
again that long time until it complietes!
In fact the HDD seems to have a faulty area withing the FAT Table
and this causes Win98SE to perform several recoveries including
copying the second FAT table before Boot completes.

> Also, they tell me that it sounds like it might be internal problems
> (The drive is seen in the Bios after about 10 minutes of the motor/
> chirping cycling up and down), so how is running the drive all night
> going to help? Is this something I should do first?

I don't agree. The BIOS detection is a seperate problem path.
You cannot do anything on that besides running CHKDSK with Repair.
But last not least Your HDD has a problem, which needs to be repaired.
e.g. some faulty area may need to be set to inactive (not used).
Horst
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig.. 

Horstshit is back.

"Horst Franke" <nospam@invalid> wrote in message news:f7flpg$oe4$02$1@news.t-online.com
> In news:1182898328.040198.239320@m36g2000hse.googlegroups.com David D wrote:
>
> > Data Recovery - why do they let the damaged HD run all night?
> > I talked to a Data recovery house and they told me they sometimes have
> > to let the drive run all night - why is that? Won't that cause more
> > damage?
>
> Hi David, that's also my experience!
> Windows needs much extra times to recover from faulty sectors!
> e.g. on a Win98SE system with a faulty boot HDD it takes sometimes
> about 2 HOURS before the Boot completes!
> Then it tells me the HDD ist ok, but on the next ReBoot it takes
> again that long time until it complietes!
> In fact the HDD seems to have a faulty area withing the FAT Table
> and this causes Win98SE to perform several recoveries including
> copying the second FAT table before Boot completes.
>
> > Also, they tell me that it sounds like it might be internal problems
> > (The drive is seen in the Bios after about 10 minutes of the motor/
> > chirping cycling up and down), so how is running the drive all night
> > going to help? Is this something I should do first?
>
> I don't agree. The BIOS detection is a seperate problem path.
> You cannot do anything on that besides running CHKDSK with Repair.
> But last not least Your HDD has a problem, which needs to be repaired.
> e.g. some faulty area may need to be set to inactive (not used).
> Horst
 >> Stay informed about: Data Recovery - why do they let the damaged HD run all nig..