Skip to content

Commit a545fbf

Browse files
committed
Document format of errors and what to do with errors - fixes #12
1 parent 55dd68c commit a545fbf

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

README.md

+27
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,33 @@ The default running time for stressdisk is 24h which is a sensible
106106
minimum. However if you want to run it for longer then use `-duration
107107
48h` for instance.
108108

109+
Errors
110+
------
111+
112+
If stressdisk finds an error it will print lines like this:
113+
114+
2019/03/07 10:55:09 0AA00000: 2D, A1 diff 8C
115+
116+
The fields are `offset`, `file1 value`, `file 2 value` and the diff
117+
which is `file1_value XOR file2_value` all in hexadecimal. The diff
118+
will be a binary number for a single bit error so `01`, `02`, `04`,
119+
`08`, `10`, `20`, `40`, `80`.
120+
121+
This may give some insight into the problem (eg a single bit flipped),
122+
or errors starting 4k boundaries, but may not.
123+
124+
However, the actual errors aren't that important, you shouldn't get
125+
**any**. If you do then:
126+
127+
1. run [memtest86](https://www.memtest86.com/) on the machine for 48 hours to check for RAM problems, if this passes then
128+
2. try the stressdisk test on another machine if you can, if this fails then
129+
3. discard or return the media
130+
131+
If you didn't get to step 3. then you'll need to play with the
132+
hardware of the machine, replace the RAM etc. Stressdisk errors are
133+
*usually* caused by bad media, but not always. Bad RAM is a fairly
134+
likely cause of stressdisk errors too.
135+
109136
Testing Flash
110137
-------------
111138

0 commit comments

Comments
 (0)