IFW 2.83 Location of "Bad sectors"

[mschiffrin]

Sorry if this is a duplicate, but the forum software says "bad sectors" are too common words to search for.

I have an internal drive that's going bad, will be RMA'ing with Western Digital. Neither WD's diagnostics nor chkdsk nor Spinrite are able to repair.

As in subject line, I'm using IFW 2.83. Running backup with options "Validate", "Omit Page File Data", "Omit Hibernation Data", "Ignore IO Errors" (so I don't need to babysit it), "Log Results to File".

In my log, I get entries like:
[10/8/2013 9:38:47 PM] Bad Sectors - Reading:2 Writing:0 (1)

I'd like to find out whether those bad sectors are occupied, and if so by what file(s), so when I copy to the new drive I can know whether to try to find those files in an older backup or re-create some other way. I've seen forum references to FINDLBAF.ZIP, and downloaded that, but now don't know what locations to send in to findlbaf.

Any advice? E.g. if I don't check "Ignore IO Errors" will I get the locations?

Thanks.

[TeraByte Support]

Enable the /logl:10 for more details. Once you have the LBA you can use the
findlbaf utility to try and find the file (ftp://terabyteunlimited.com) -
needs to run as administrator (open command prompt as administrator).

You only had two bad sectors it hit.


"mschiffrin" wrote in message news:6513@public.image...

Sorry if this is a duplicate, but the forum software says "bad sectors" are
too common words to search for.

I have an internal drive that's going bad, will be RMA'ing with Western
Digital. Neither WD's diagnostics nor chkdsk nor Spinrite are able to
repair.

As in subject line, I'm using IFW 2.83. Running backup with options
"Validate", "Omit Page File Data", "Omit Hibernation Data", "Ignore IO
Errors" (so I don't need to babysit it), "Log Results to File".

In my log, I get entries like:
[10/8/2013 9:38:47 PM] Bad Sectors - Reading:2 Writing:0 (1)

I'd like to find out whether those bad sectors are occupied, and if so by
what file(s), so when I copy to the new drive I can know whether to try to
find those files in an older backup or re-create some other way. I've seen
forum references to FINDLBAF.ZIP, and downloaded that, but now don't know
what locations to send in to findlbaf.

Any advice? E.g. if I don't check "Ignore IO Errors" will I get the
locations?

Thanks.

[mschiffrin]

Worked perfectly!

And even better news, findlbaf shows both bad sectors are occupied by files in the recycle bin, so no harm if I lose them.

When I restore onto new drive, do I need to do anything special about the bad regions on the source drive?

Thanks again.

[Brian K]

mschiffrin,

Does the IFW /logl:10 tell you the LBA of the bad sectors? Individual or a range?

[mschiffrin]

Brian -

Yes, /logl:10 gave me the addresses. Here are the log lines:

[10/9/2013 8:27:15 PM] Disk Read Error at LBA 176878058
[10/9/2013 8:27:19 PM] Disk Read Error at LBA 176878546

And here are the findlbaf 'conversations':
C:\>findlbaf 1 176878058
Finding file using LBA 176878058 on drive 1...
Found Partition: MBR 0 953867MB (0001) HPFS/NTFS
Scanning files...
Unable to process file \$Secure
Unable to process file \$Extend\$ObjId
Unable to process file \$Extend\$Quota
Unable to process file \$Extend\$Reparse
Unable to process file \$Extend\$UsnJrnl
Found file \$RECYCLE.BIN\S-1-5-21-3631067614-3652189540-2994467547-1000\$RY0UYU2
.pdf uses LBA 176878058

C:\>findlbaf 1 176878546
Finding file using LBA 176878546 on drive 1...
Found Partition: MBR 0 953867MB (0001) HPFS/NTFS
Scanning files...
Unable to process file \$Secure
Unable to process file \$Extend\$ObjId
Unable to process file \$Extend\$Quota
Unable to process file \$Extend\$Reparse
Unable to process file \$Extend\$UsnJrnl
Found file \$RECYCLE.BIN\S-1-5-21-3631067614-3652189540-2994467547-1000\$RY0UYU2
.pdf uses LBA 176878546

Thanks.

[TeraByte Support]

No, nothing special.

"mschiffrin" wrote in message news:6515@public.image...

Worked perfectly!

And even better news, findlbaf shows both bad sectors are occupied by files
in the recycle bin, so no harm if I lose them.

When I restore onto new drive, do I need to do anything special about the
bad regions on the source drive?

Thanks again.