blob: 62ad5938cf0ca5f9f81f9a610a7352b877f709f9 [file] [log] [blame]
Alistair Delvabeaee832021-02-24 11:27:23 -08001'\" t
Yi Kong39bbd962022-01-09 19:41:38 +08002.TH mbadblocks 1 "08Jan22" mtools-4.0.37
Alistair Delvabeaee832021-02-24 11:27:23 -08003.SH Name
4mbadblocks - tests a floppy disk, and marks the bad blocks in the FAT
5'\" t
6.de TQ
7.br
8.ns
9.TP \\$1
10..
11
12.tr \(is'
13.tr \(if`
14.tr \(pd"
15
16.SH Note\ of\ warning
17This manpage has been automatically generated from mtools's texinfo
18documentation, and may not be entirely accurate or complete. See the
19end of this man page for details.
20.PP
21.SH Description
22.PP
23The \fR\&\f(CWmbadblocks\fR command is used to mark some clusters on an
24MS-DOS filesystem bad. It has the following syntax:
25.PP
26\&\fR\&\f(CWmbadblocks\fR [\fR\&\f(CW-s\fR \fIsectorlist\fR|\fR\&\f(CW-c\fR \fIclusterlist\fR|-w] \fIdrive\fR\fR\&\f(CW:\fR
27.PP
28If no command line flags are supplied, \fR\&\f(CWMbadblocks\fR scans an
29MS-DOS filesystem for bad blocks by simply trying to read them and
30flag them if read fails. All blocks that are unused are scanned, and
31if detected bad are marked as such in the FAT.
32.PP
33This command is intended to be used right after \fR\&\f(CWmformat\fR. It is
34not intended to salvage data from bad disks.
35.PP
36.SH Command\ line\ options
37.TP
38\&\fR\&\f(CWc\ \fIfile\fR\&\f(CW\fR\
39Use a list of bad clusters, rather than scanning for bad clusters
40itself.
41.TP
42\&\fR\&\f(CWs\ \fIfile\fR\&\f(CW\fR\
43Use a list of bad sectors (counted from beginning of filesystem),
44rather than trying for bad clusters itself.
45.TP
46\&\fR\&\f(CWw\fR\
47Write a random pattern to each cluster, then read it back and flag
48cluster as bad if mismatch. Only free clusters are tested in such a
49way, so any file data is preserved.
50.PP
51.SH Bugs
52\&\fR\&\f(CWMbadblocks\fR should (but doesn't yet :-( ) also try to salvage bad
53blocks which are in use by reading them repeatedly, and then mark them
54bad.
55.PP
56.SH See\ Also
57Mtools' texinfo doc
58.SH Viewing\ the\ texi\ doc
59This manpage has been automatically generated from mtools's texinfo
60documentation. However, this process is only approximative, and some
61items, such as crossreferences, footnotes and indices are lost in this
62translation process. Indeed, these items have no appropriate
63representation in the manpage format. Moreover, not all information has
64been translated into the manpage version. Thus I strongly advise you to
65use the original texinfo doc. See the end of this manpage for
66instructions how to view the texinfo doc.
67.TP
68* \ \
69To generate a printable copy from the texinfo doc, run the following
70commands:
71
72.nf
73.ft 3
74.in +0.3i
75 ./configure; make dvi; dvips mtools.dvi
76.fi
77.in -0.3i
78.ft R
79.PP
80
81\&\fR
82.TP
83* \ \
84To generate a html copy, run:
85
86.nf
87.ft 3
88.in +0.3i
89 ./configure; make html
90.fi
91.in -0.3i
92.ft R
93.PP
94
95\&\fRA premade html can be found at
96\&\fR\&\f(CW\(ifhttp://www.gnu.org/software/mtools/manual/mtools.html\(is\fR
97.TP
98* \ \
99To generate an info copy (browsable using emacs' info mode), run:
100
101.nf
102.ft 3
103.in +0.3i
104 ./configure; make info
105.fi
106.in -0.3i
107.ft R
108.PP
109
110\&\fR
111.PP
112The texinfo doc looks most pretty when printed or as html. Indeed, in
113the info version certain examples are difficult to read due to the
114quoting conventions used in info.
115.PP