If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How to "scrub" for bad blocks/files on a Windows file system?
Hello,
Do utilities exist to "scrub" for bad blocks/files/metadata on a Windows file system? More details: While managing my personal storage (anywhere from 10-20GB storage rignt now) and my associated backup drives, I'm finding that disk drives and/or file systems are having problems reading from some file systems. I suspect different root causes here, anything from damaged file system(s) to bad blocks on disk drives. I would like to be able "scrub" all my file systems data (hopefully from Windows, but I can try other OS if absolutely required) to see if all the files (and all their associated data and metadata blocks) can be read, and if not, find out which files or parts of files are unreadable (this is probably the tricky part--mapping blocks or bad metadata to files or parts of larger files), and then I can (from a report such a utility would generate) restore them from backup and/or make decisions on whether or not reformat and/or replace a disk drive. Would be nice if this utility also forced the drive into remapping bad blocks to good ones if the drive hasn't done this already for some reason (maybe unlikely--it's been a while since I've looked closesly at this, and I only know/knew how SCSI/FC drives did this in the past). Anybody have any recommended utilities for this? Maybe references where I can read/investigate more? I doubt that chkdsk and other built-in Windows things are this powerful/flexible; maybe I'm mistaken? My alternative is to simply read entire disk drives/filesystems and then go through the process of replacing files that can't be read and then maybe reformat an entire drive. A bit tedious, and it's hard to do this for every file system I have (as well as all the snapshot backups I keep). I'm mostly using FAT32 (for Mac OS, Linux, and other OS compatibility) and NTFS filesystems. Thanks for any help, Matt -- Remove the obvious text (including the dash) to email me. |
#2
|
|||
|
|||
For the FAT32/16 http://grc.com/spinrite.htm Spinrite 5. He is now =
working on Spinrite 6 for NTFS/FAT32/16. --=20 Just my 2=A2 worth Jeff __________in response to__________ "Matt" wrote in message = ... | Hello, |=20 | Do utilities exist to "scrub" for bad blocks/files/metadata on a | Windows file system? |=20 | More details: |=20 | While managing my personal storage (anywhere from 10-20GB storage | rignt now) and my associated backup drives, I'm finding that disk | drives and/or file systems are having problems reading from some file | systems. I suspect different root causes here, anything from damaged | file system(s) to bad blocks on disk drives. |=20 | I would like to be able "scrub" all my file systems data (hopefully | from Windows, but I can try other OS if absolutely required) to see if | all the files (and all their associated data and metadata blocks) can | be read, and if not, find out which files or parts of files are | unreadable (this is probably the tricky part--mapping blocks or bad | metadata to files or parts of larger files), and then I can (from a | report such a utility would generate) restore them from backup and/or | make decisions on whether or not reformat and/or replace a disk drive. | Would be nice if this utility also forced the drive into remapping bad | blocks to good ones if the drive hasn't done this already for some | reason (maybe unlikely--it's been a while since I've looked closesly | at this, and I only know/knew how SCSI/FC drives did this in the | past). |=20 | Anybody have any recommended utilities for this? Maybe references | where I can read/investigate more? |=20 | I doubt that chkdsk and other built-in Windows things are this | powerful/flexible; maybe I'm mistaken? My alternative is to simply | read entire disk drives/filesystems and then go through the process of | replacing files that can't be read and then maybe reformat an entire | drive. A bit tedious, and it's hard to do this for every file system | I have (as well as all the snapshot backups I keep). |=20 | I'm mostly using FAT32 (for Mac OS, Linux, and other OS compatibility) | and NTFS filesystems. |=20 | Thanks for any help, | Matt | -- | Remove the obvious text (including the dash) to email me. |
#3
|
|||
|
|||
Use chkdsk with the /r switch.
Or choose to do an error check of your hard drives and check for surface errors Or goto your hard drive manufacturer's website and download their diagnostics utility (if there are errors, you'll get an error number that you'll include when you exchange your hard drive, if it is still under warranty). Note that if the disk has physical flaws, any data occupying the space where there are flaws may be corrupted. Hopefully that isn't the case for you. NTFS, if it encounters bad sectors while performing disk activity, will automatically attempt to relocate the file. It might not always be successful depending on the state of the media itself. -- Jason Tsang - Microsoft MVP Find out about the MS MVP Program - http://mvp.support.microsoft.com/default.aspx "Matt" wrote in message ... Hello, Do utilities exist to "scrub" for bad blocks/files/metadata on a Windows file system? More details: While managing my personal storage (anywhere from 10-20GB storage rignt now) and my associated backup drives, I'm finding that disk drives and/or file systems are having problems reading from some file systems. I suspect different root causes here, anything from damaged file system(s) to bad blocks on disk drives. I would like to be able "scrub" all my file systems data (hopefully from Windows, but I can try other OS if absolutely required) to see if all the files (and all their associated data and metadata blocks) can be read, and if not, find out which files or parts of files are unreadable (this is probably the tricky part--mapping blocks or bad metadata to files or parts of larger files), and then I can (from a report such a utility would generate) restore them from backup and/or make decisions on whether or not reformat and/or replace a disk drive. Would be nice if this utility also forced the drive into remapping bad blocks to good ones if the drive hasn't done this already for some reason (maybe unlikely--it's been a while since I've looked closesly at this, and I only know/knew how SCSI/FC drives did this in the past). Anybody have any recommended utilities for this? Maybe references where I can read/investigate more? I doubt that chkdsk and other built-in Windows things are this powerful/flexible; maybe I'm mistaken? My alternative is to simply read entire disk drives/filesystems and then go through the process of replacing files that can't be read and then maybe reformat an entire drive. A bit tedious, and it's hard to do this for every file system I have (as well as all the snapshot backups I keep). I'm mostly using FAT32 (for Mac OS, Linux, and other OS compatibility) and NTFS filesystems. Thanks for any help, Matt -- Remove the obvious text (including the dash) to email me. |
#4
|
|||
|
|||
On Mon, 12 Jan 2004 20:53:14 -0500, "Jason Tsang"
wrote: Note that if the disk has physical flaws, any data occupying the space where there are flaws may be corrupted. Hopefully that isn't the case for you. Well, that's probably the key scenario I'm trying to address: A disk block goes bad after data is written to it. The question in my head is: which file is mapped to said block(s)? Maybe the utility (Spinrite) the other poster (Jeff) references can address this? NTFS, if it encounters bad sectors while performing disk activity, will automatically attempt to relocate the file. It might not always be successful depending on the state of the media itself. Interesting. Too bad I keep my bigger backup disks in FAT32 flavor to be Mac OS X compatible. Is OS X, and Linux for that matter, getting along better with NTFS nowadays? Matt -- Remove the obvious text (including the dash) to email me. |
#5
|
|||
|
|||
Spinrite is outdated. Don't bother wasting money on it.
You can get what you need from your hard drive manufacturer. If there are bad blocks on your hard drive and your hard drive is still under warranty, you can exchange it. -- Jason Tsang - Microsoft MVP Find out about the MS MVP Program - http://mvp.support.microsoft.com/default.aspx "Matt" wrote in message ... On Mon, 12 Jan 2004 20:53:14 -0500, "Jason Tsang" wrote: Note that if the disk has physical flaws, any data occupying the space where there are flaws may be corrupted. Hopefully that isn't the case for you. Well, that's probably the key scenario I'm trying to address: A disk block goes bad after data is written to it. The question in my head is: which file is mapped to said block(s)? Maybe the utility (Spinrite) the other poster (Jeff) references can address this? NTFS, if it encounters bad sectors while performing disk activity, will automatically attempt to relocate the file. It might not always be successful depending on the state of the media itself. Interesting. Too bad I keep my bigger backup disks in FAT32 flavor to be Mac OS X compatible. Is OS X, and Linux for that matter, getting along better with NTFS nowadays? Matt -- Remove the obvious text (including the dash) to email me. |
#6
|
|||
|
|||
On Mon, 12 Jan 2004 21:18:58 -0500, "Jason Tsang"
wrote: You can get what you need from your hard drive manufacturer. I think I need something that can tell me which bad block addresses are mapped to which files, parts of files, and metadata on the filesystem for FAT32. I suspect the hard drive manufacturer can not do this. If there are bad blocks on your hard drive and your hard drive is still under warranty, you can exchange it. Please understand: I'm not worried about my hardware or replacing the hardware or anything. I'm worried about the cost of not recovering *data*. I'd like to proactively "scrub" my filesystems to find those blocks that have gone bad after the file system wrote data/metadata to these blocks, then I'd like to find those files that are affected by these bad blocks, and then I'd like to replace these files from backup (hopefully). I'd like to do all this BEFORE I have data loss from one of my sources (primary or backup), because once this happens, I can't restore any bad-block data in the aforementioned scenario. Matt -- Remove the obvious text (including the dash) to email me. |
#7
|
|||
|
|||
Interesting. Too bad I keep my bigger backup disks in FAT32 flavor to
be Mac OS X compatible. Is OS X, and Linux for that matter, getting Note: FAT32 imposes a file size limit of 4GB, not so with NTFS. -- Maxim Shatskih, Windows DDK MVP StorageCraft Corporation http://www.storagecraft.com |
#8
|
|||
|
|||
As I wrote Spinrite is being updated to Spinrite 6. Spinrite 5 still =
works though on FAT32. Did you bother to go to the link I provided and = read the information? --=20 Just my 2=A2 worth Jeff __________in response to__________ "Matt" wrote in message = ... | On Mon, 12 Jan 2004 21:18:58 -0500, "Jason Tsang" | wrote: | You can get what you need from your hard drive manufacturer. |=20 | I think I need something that can tell me which bad block addresses | are mapped to which files, parts of files, and metadata on the | filesystem for FAT32. I suspect the hard drive manufacturer can not | do this. |=20 | If there are bad blocks on your hard drive and your hard drive is = still | under warranty, you can exchange it. |=20 | Please understand: |=20 | I'm not worried about my hardware or replacing the hardware or | anything. I'm worried about the cost of not recovering *data*.=20 |=20 | I'd like to proactively "scrub" my filesystems to find those blocks | that have gone bad after the file system wrote data/metadata to these | blocks, then I'd like to find those files that are affected by these | bad blocks, and then I'd like to replace these files from backup | (hopefully). I'd like to do all this BEFORE I have data loss from one | of my sources (primary or backup), because once this happens, I can't | restore any bad-block data in the aforementioned scenario. |=20 | Matt | -- | Remove the obvious text (including the dash) to email me. |
#9
|
|||
|
|||
On Wed, 14 Jan 2004 01:44:57 GMT, "mrtee"
wrote: As I wrote Spinrite is being updated to Spinrite 6. Spinrite 5 still works though on FAT32. Did you bother to go to the link I provided and read the information? Nope, not yet. But I plan to check it out. Thanks for the reminder. (My previous post was making sure I clarified the issue per previous posts...) Matt -- Remove the obvious text (including the dash) to email me. |
#10
|
|||
|
|||
On Tue, 13 Jan 2004 01:40:53 GMT, "mrtee"
wrote: For the FAT32/16 http://grc.com/spinrite.htm Spinrite 5. He is now working on Spinrite 6 for NTFS/FAT32/16. Software looks quite interesting and useful. I haven't yet found anything in web pages that says it will spit out a report of those files/metadata that are irrecoverable from a file system so that I can go rewrite said files from backups (or from primary if I'm reading the backup disks/copies). Will it do this? Will Spinrite 6 run from WinXP without having to reboot to DOS? Is there a means to trial/evaluate Spinrite 5 free of charge? Matt -- Remove the obvious text (including the dash) to email me. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Will Windows Power the Living Room? | Ablang | Homebuilt PC's | 32 | July 8th 04 05:34 AM |
Please help with new system - hangs when booting Windows 2000. | Kevin Lawton | Homebuilt PC's | 7 | April 14th 04 02:40 AM |
Norton AV 2002 small problem | Keith S. | Dell Computers | 7 | January 9th 04 06:04 PM |
Microsoft to force Windows updates? | Steve | Dell Computers | 114 | September 9th 03 02:11 AM |
Does Windows kill the "bootability" other secondary hard drives it finds with the same OS on? | Kb | General | 3 | September 5th 03 12:33 PM |