Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developer:hardware_storage_error_detection [2016/09/06 00:32] henri |
developer:hardware_storage_error_detection [2016/09/06 00:37] henri [Notes specific to using badblocks on a mac OS X system.] |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * [[http://e2fsprogs.sourceforge.net|badblocks]] (*NIX command line tool - part of the e2fsprogs project) | * [[http://e2fsprogs.sourceforge.net|badblocks]] (*NIX command line tool - part of the e2fsprogs project) | ||
| - | \\ \\ | + | \\ |
| ===== Notes specific to using badblocks on a mac OS X system. ===== | ===== Notes specific to using badblocks on a mac OS X system. ===== | ||
| OS X specifies the disks within **///dev//** as two different kinds. The first kind (example : **///dev/disk1//**) is a buffered device. The problem with working with a buffered device is in some situations it may be slower, than having direct access to the device. This brings us to the second kind of disk device in OS X a raw disk (example : **///dev/rdisk1//**). Accessing the raw disk will be faster for some operations. In particular when using badblock you will tend to see an improvement by using the raw device rather than the buffered device. | OS X specifies the disks within **///dev//** as two different kinds. The first kind (example : **///dev/disk1//**) is a buffered device. The problem with working with a buffered device is in some situations it may be slower, than having direct access to the device. This brings us to the second kind of disk device in OS X a raw disk (example : **///dev/rdisk1//**). Accessing the raw disk will be faster for some operations. In particular when using badblock you will tend to see an improvement by using the raw device rather than the buffered device. | ||
| Line 19: | Line 19: | ||
| Example of usage : | Example of usage : | ||
| - Ensure any disk and/or partition(s) on which you are going to check for bad blocks are unmounted | - Ensure any disk and/or partition(s) on which you are going to check for bad blocks are unmounted | ||
| - | - Set the PWD to the the newley installed sbin directory. You may need to select the correct version for | + | - Set the PWD to the the newley installed sbin directory. You may need to select the correct version for your install. |
| - | your install. | + | |
| - ''$ cd /usr/local/Cellar/e2fsprogs/1.42.13/sbin'' | - ''$ cd /usr/local/Cellar/e2fsprogs/1.42.13/sbin'' | ||
| - Run bad blocks on your disk device. The -s flag will show progress. Further usage information is available from the man page. | - Run bad blocks on your disk device. The -s flag will show progress. Further usage information is available from the man page. | ||