1. Computing & Technology

Linux System Administrator's Guide

From

each I/O error it finds; these will go to the console or, if syslog is being used, to the file /var/log/messages . fdformat itself won't tell where the error is (one usually doesn't care, floppies are cheap enough that a bad one is automatically thrown away).


   

 	$ fdformat /dev/fd0H1440
 	Double-sided, 80 tracks, 18 sec/track. Total capacity 
 	1440 KB.
 	Formatting ... done
 	Verifying ... read: Unknown error
 	$
 	 

The badblocks command can be used to search any disk or partition for bad blocks (including a floppy). It does not format the disk, so it can be used to check even existing filesystems. The example below checks a 3.5 inch floppy with two bad blocks.


   

 	$ badblocks /dev/fd0H1440 1440
 	718
 	719
 	$
 	 

badblocks outputs the block numbers of the bad blocks it finds. Most filesystems can avoid such bad blocks. They maintain a list of known bad blocks, which is initialized when the filesystem is made, and can be modified later. The initial search for bad blocks can be done by the mkfs command (which initializes the filesystem), but later checks should be done with badblocks and the new blocks should be added with fsck . We'll describe mkfs and fsck later.

Many modern disks automatically notice bad blocks, and attempt to fix them by using a special, reserved good block instead. This is invisible to the operating system. This feature should be documented in the disk's manual, if you're curious if it is happening. Even such disks can fail, if the number of bad blocks grows too large, although chances are that by then the disk will be so rotten as to be unusable.


   Prev    Home    Next
   Tapes    Up    Partitions


©2012 About.com. All rights reserved.

A part of The New York Times Company.