badblk(1M) badblk(1M)NAME badblk - sets or updates bad block information SYNOPSIS badblk [-r] /dev/rdsk/c?d?s? [blkno]... ARGUMENTS blkno Specifies one or more block numbers separated by blanks. If you invoke badblk without specifying block numbers, it will search the whole device for bad blocks and print the block numbers of any that are found. /dev/rdsk/c?d?s? Specifies controller, drive, and slice numbers, respectively. Replace ? with the appropriate numbers. -r Does not attempt to block any bad blocks, but instead will report those that are found. DESCRIPTION badblk sets or updates bad block information for disk partitions. The badblk command first attempts to alter a bad block by hardware sparing. In the event that hardware sparing fails and the device supports alternate bad blocking, badblk will attempt to alternate block the bad block. Hardware sparing may fail if the device does not support hardware sparing or if the device's capacity for hardware sparing has been exceeded. EXAMPLES The command: badblk /dev/rdsk/c0d0s31 does a full read-verify on the whole disk associated with controller zero, drive zero. Note that the raw device must be specified. The command: badblk /dev/rdsk/c0d0s0 does a full read-verify on partition zero (usually the root partition) of the disk associated with controller zero, drive zero. NOTES The badblk command uses very simple tests to determine whether or not a block is bad. The alternate block map information can be accessed and modified through the dp(1M) utility. January 1992 1
badblk(1M) badblk(1M)The badblk command does not work on floppy disks. FILES /usr/bin/badblk Executable file SEE ALSO dp(1M) altblk(4) in A/UX Programmer's Reference 2 January 1992