The other day, I has cause to question what happens if the IFL restore operation is per formed to a drive that has had bad sectors blocked out? Does IFL know to stay off those sectors? Thanks in advance!
The details of what happened: I restored a backup of my XP system to a brand new WD Black 500GB drive. The restore seemed to work at first, then after about 30 minutes, executions of any program got slower and slower and ground to a halt (as if the drive was having re-read errors). I had to pull that drive and go back to the original. On formatting the WD drive (using the built in XP format tool found in drive "properties") to see if it had problems, none were reported. However,I know from some experience that almost every brand new drive has many blocks already mapped out as bad during the manufacturing and formatting process. So how can IFL avoid such bad sectors when doing a restore? What is the workaround to this situation? Thanks again.
What if Target Drive has bad sectors?
Re: What if Target Drive has bad sectors?
Defective blocks are handled entirely by the hard drive, and don't
involve the operating system, other than reporting a read error.
Stated simply, when the drive determines that a block is defective it
swaps in a spare good block so that reads and writes to the defective
block are re-directed automatically to that spare block.
On Thu, 2 Oct 2014 15:28:26 PDT, PhysicsDavid wrote:
>The other day, I has cause to question what happens if the IFL restore operation is per formed to a drive that has had bad sectors blocked out? Does IFL know to stay off those sectors? Thanks in advance!
>
>The details of what happened: I restored a backup of my XP system to a brand new WD Black 500GB drive. The restore seemed to work at first, then after about 30 minutes, executions of any program got slower and slower and ground to a halt (as if the drive was having re-read errors). I had to pull that drive and go back to the original. On formatting the WD drive (using the built in XP format tool found in drive "properties") to see if it had problems, none were reported. However,I know from some experience that almost every brand new drive has many blocks already mapped out as bad during the manufacturing and formatting process. So how can IFL avoid such bad sectors when doing a restore? What is the workaround to this situation? Thanks again.
>
involve the operating system, other than reporting a read error.
Stated simply, when the drive determines that a block is defective it
swaps in a spare good block so that reads and writes to the defective
block are re-directed automatically to that spare block.
On Thu, 2 Oct 2014 15:28:26 PDT, PhysicsDavid wrote:
>The other day, I has cause to question what happens if the IFL restore operation is per formed to a drive that has had bad sectors blocked out? Does IFL know to stay off those sectors? Thanks in advance!
>
>The details of what happened: I restored a backup of my XP system to a brand new WD Black 500GB drive. The restore seemed to work at first, then after about 30 minutes, executions of any program got slower and slower and ground to a halt (as if the drive was having re-read errors). I had to pull that drive and go back to the original. On formatting the WD drive (using the built in XP format tool found in drive "properties") to see if it had problems, none were reported. However,I know from some experience that almost every brand new drive has many blocks already mapped out as bad during the manufacturing and formatting process. So how can IFL avoid such bad sectors when doing a restore? What is the workaround to this situation? Thanks again.
>
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: What if Target Drive has bad sectors?
If there are bad sectors that chkdsk is reporting, those can cause problems. Bad sectors that get mapped out by the drive itself generally don't cause issues. Did chkdsk report any bad sectors?
Did you check the Event Viewer to see if any drive/controller related errors were logged? Depending on the situation, if there are errors, the connection speed may be reduced to an unacceptable level.
Did you check the Event Viewer to see if any drive/controller related errors were logged? Depending on the situation, if there are errors, the connection speed may be reduced to an unacceptable level.
-
TeraByte Support
- Posts: 3616
- Joined: Thu May 05, 2011 10:37 pm
Re: What if Target Drive has bad sectors?
If you have a drive with bad sectors showing (relocation table is full) -
get rid of it. You're just asking for problems. Image often as well using
validation as memory issues is another thing that will cause a creep of
corruption into everything.
"PhysicsDavid" wrote in message news:8714@public.image...
The other day, I has cause to question what happens if the IFL restore
operation is per formed to a drive that has had bad sectors blocked out?
Does IFL know to stay off those sectors? Thanks in advance!
The details of what happened: I restored a backup of my XP system to a
brand new WD Black 500GB drive. The restore seemed to work at first, then
after about 30 minutes, executions of any program got slower and slower and
ground to a halt (as if the drive was having re-read errors). I had to pull
that drive and go back to the original. On formatting the WD drive (using
the built in XP format tool found in drive "properties") to see if it had
problems, none were reported. However,I know from some experience that
almost every brand new drive has many blocks already mapped out as bad
during the manufacturing and formatting process. So how can IFL avoid such
bad sectors when doing a restore? What is the workaround to this situation?
Thanks again.
get rid of it. You're just asking for problems. Image often as well using
validation as memory issues is another thing that will cause a creep of
corruption into everything.
"PhysicsDavid" wrote in message news:8714@public.image...
The other day, I has cause to question what happens if the IFL restore
operation is per formed to a drive that has had bad sectors blocked out?
Does IFL know to stay off those sectors? Thanks in advance!
The details of what happened: I restored a backup of my XP system to a
brand new WD Black 500GB drive. The restore seemed to work at first, then
after about 30 minutes, executions of any program got slower and slower and
ground to a halt (as if the drive was having re-read errors). I had to pull
that drive and go back to the original. On formatting the WD drive (using
the built in XP format tool found in drive "properties") to see if it had
problems, none were reported. However,I know from some experience that
almost every brand new drive has many blocks already mapped out as bad
during the manufacturing and formatting process. So how can IFL avoid such
bad sectors when doing a restore? What is the workaround to this situation?
Thanks again.
-
PhysicsDavid
- Posts: 2
- Joined: Thu Oct 02, 2014 10:18 pm
Re: What if Target Drive has bad sectors?
Thanks for the replies folks. I am not particularly fluent with the various tools, but I did look through the event log and found nothing relating to the disk that suggested a problem. Ckdsk reported nothing after I had reformatted the drive (I did not run it prior to re-formatting - in retrospect, that was an obvious mistake...).
How do I view the bad block relocation table? I would assume that would be a very low level utility specific to the drive maker....
When I removed the WD drive to put the old one back in, I found it to be what I thought was unreasonably hot. That again made me think the drive was having re-read problems (or maybe just other problems). How would I know if the drive were having to do many re-reads? Would that have shown up in the event log, or does that stay internal to the drive controller? What else would cause the drive to get excessively hot (where the other comparable drive did not)?
Thanks again.
How do I view the bad block relocation table? I would assume that would be a very low level utility specific to the drive maker....
When I removed the WD drive to put the old one back in, I found it to be what I thought was unreasonably hot. That again made me think the drive was having re-read problems (or maybe just other problems). How would I know if the drive were having to do many re-reads? Would that have shown up in the event log, or does that stay internal to the drive controller? What else would cause the drive to get excessively hot (where the other comparable drive did not)?
Thanks again.
Re: What if Target Drive has bad sectors?
Sorry to drag up an old thread but I was wondering if there has been any resolution of this problem (either by OP or Terabyte), it looks very similar to mine in:
viewtopic.php?f=4&t=702
I imagine it's exactly the same thing, and was never anything to do with the drive. The only reason I ask is I'm sorting out some backup issues and would like to use Image for Windows to backup a 750GB drive, but it is my experience that this is impossible due to the weird slowdown. No biggie, I would just like to get it working. Thanks in advance.
viewtopic.php?f=4&t=702
I imagine it's exactly the same thing, and was never anything to do with the drive. The only reason I ask is I'm sorting out some backup issues and would like to use Image for Windows to backup a 750GB drive, but it is my experience that this is impossible due to the weird slowdown. No biggie, I would just like to get it working. Thanks in advance.
-
TeraByte Support
- Posts: 3616
- Joined: Thu May 05, 2011 10:37 pm
Re: What if Target Drive has bad sectors?
if you've mapped out clusters with chkdsk /r then they will be skipped, when
you restore the areas will still be marked out, you'd run chkdsk /b to have
it unmap the clusters.
if you run the drive manufactures scan utility on the system it will usually
relocate bad sectors so they are no longer used. Once the relocation table
is full, it's time for a new drive or you risk more issues going on since
once failures start they tend to grow and cause problems.
"adx" wrote in message news:10758@public.image...
Sorry to drag up an old thread but I was wondering if there has been any
resolution of this problem (either by OP or Terabyte), it looks very similar
to mine in:
[
viewtopic.php?f=4&t=702
](https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=702)
I imagine it's exactly the same thing, and was never anything to do with the
drive. The only reason I ask is I'm sorting out some backup issues and would
like to use Image for Windows to backup a 750GB drive, but it is my
experience that this is impossible due to the weird slowdown. No biggie, I
would just like to get it working. Thanks in advance.
you restore the areas will still be marked out, you'd run chkdsk /b to have
it unmap the clusters.
if you run the drive manufactures scan utility on the system it will usually
relocate bad sectors so they are no longer used. Once the relocation table
is full, it's time for a new drive or you risk more issues going on since
once failures start they tend to grow and cause problems.
"adx" wrote in message news:10758@public.image...
Sorry to drag up an old thread but I was wondering if there has been any
resolution of this problem (either by OP or Terabyte), it looks very similar
to mine in:
[
viewtopic.php?f=4&t=702
](https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=702)
I imagine it's exactly the same thing, and was never anything to do with the
drive. The only reason I ask is I'm sorting out some backup issues and would
like to use Image for Windows to backup a 750GB drive, but it is my
experience that this is impossible due to the weird slowdown. No biggie, I
would just like to get it working. Thanks in advance.