meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
app:using_diagnostics [2024/01/29 00:16] – pdevineapp:using_diagnostics [2024/01/29 02:31] (current) – pdevine
Line 65: Line 65:
  
 ---- ----
-===== Troubleshooting ===== +===== Troubleshooting Drive Diagnostics ===== 
  
   * Always power down your drive before you disassemble or attempt to repair it by unplugging the Applesauce unit from USB power.   * Always power down your drive before you disassemble or attempt to repair it by unplugging the Applesauce unit from USB power.
Line 80: Line 80:
  
 {{ :app:write_protect_sensor.png?500 |}} {{ :app:write_protect_sensor.png?500 |}}
- 
-  * Verify that you have a **formatted** floppy of the correct density and correct type. If the floppy is not formatted, formatted for the wrong drive, or formatted at the wrong density, Applesauce can not verify that the drive is reading the disk correctly. If you do not have the correct kind of formatted disk, you can try setting the drive profile manually and then using the [[app:disk_writer|''Disk Writer'']] to create a formatted disk. Note also that Drive Profiler will overwrite tracks of your disk while performing initial testing, which may interfere with Check Drive read test, unless you use a reformat the disk or use a different formatted disk for testing. 
  
 == Reading 0 | Reading 1 == == Reading 0 | Reading 1 ==
Line 89: Line 87:
   * You might also see a yellow checkmark in either Reading box, as shown below. A red checkmark means that it can't find any sector structures. A yellow checkmark means that it does see sector structures, but it is also seeing a bunch of noise or bad sectors.   * You might also see a yellow checkmark in either Reading box, as shown below. A red checkmark means that it can't find any sector structures. A yellow checkmark means that it does see sector structures, but it is also seeing a bunch of noise or bad sectors.
 {{ :app:read_in_yellow.png?500 |}} {{ :app:read_in_yellow.png?500 |}}
 +
 +  * Verify that you have a **formatted** floppy of the correct density and correct type. If the floppy is not formatted, formatted for the wrong drive, or formatted at the wrong density, Applesauce can not verify that the drive is reading the disk correctly. If you do not have the correct kind of formatted disk, you can try setting the drive profile manually and then using the [[app:disk_writer|''Disk Writer'']] to create a formatted disk. Note also that Drive Profiler will overwrite tracks of your disk while performing initial testing, which may interfere with Check Drive read test, unless you use a reformat the disk or use a different formatted disk for testing.
  
   * **The most common cause of a read error is a dirty head.** Try running the Clean Head routine in Fast Imager with a cleaning disk, or manually clean the head after disassembling the drive. If you are using a 3.5" drive, never attempt to clean the heads manually. Only use a cleaning disk to clean the heads of a 3.5" drive. Attempting to manually clean a 3.5" drive heads risks knocking the heads out of alignment or damaging the springs holding the heads in position, these parts are more fragile than their 5" counterparts.   * **The most common cause of a read error is a dirty head.** Try running the Clean Head routine in Fast Imager with a cleaning disk, or manually clean the head after disassembling the drive. If you are using a 3.5" drive, never attempt to clean the heads manually. Only use a cleaning disk to clean the heads of a 3.5" drive. Attempting to manually clean a 3.5" drive heads risks knocking the heads out of alignment or damaging the springs holding the heads in position, these parts are more fragile than their 5" counterparts.
  
-  * If you happen to read a disk that contains a significant mold or a degraded disk surface, either the mold or the surface of the disk itself can get stuck to the read/write head. As the head scoots along the surface stuff builds up on it. When this occurs you'll frequently hear a screeching or grinding noise coming from the drive. Immediately take the disk out if you hear this! Once this build up has occurred, the drive will have read and write problems with all subsequent disks and can often cause bulldozing where the particles stuck to the drive head rip into the disk that caused the problems or future disks you try and read with the same drive. Dirty heads like this can destroy multiple disks if you don't clean off the built up material. Whenever you hear strange noises, stop, inspect the disk for mold or scratches along the disk surface, and try to clean the drive heads.+  * If you happen to read a disk that contains a significant mold or a degraded disk surface, either the mold or the surface of the disk itself can get stuck to the read/write head. As the head scoots along the surface of the disk stuff builds up on the head which is pressing into the disk surface. When this occurs you'll frequently hear a screeching or grinding noise coming from the drive. Immediately take the disk out if you hear this! Once this build up has occurred, the drive will have read and write problems with all subsequent disks and can often cause bulldozing where the particles stuck to the drive head rip into the disk that caused the problems or future disks you try and read with the same drive. Dirty heads like this can destroy multiple disks if you don't clean off the built up material. Whenever you hear strange noises, stop, inspect the disk for mold or scratches along the disk surface, and try to clean the drive heads.
  
   * If you are using a Disk ][ drive, the next most common cause of a read error is failure of the 74125 IC (same as 74LS125) on the Disk Analog Card inside the disk drive. The 74125 IC may also result in abnormal power consumption in a Disk ][. Occasionally 74125 IC failure results in the drive uncontrollably overwriting Track $00, which destroys disks. The next most common point of failure is the MC3470 IC, which is also on the Disk Analog Card. If can be useful to test these chips by substitution with replacement or known good ICs. The ULN2003 IC, which controls the stepper motor, may also occasionally fail, resulting in absent or abnormal head movement.    * If you are using a Disk ][ drive, the next most common cause of a read error is failure of the 74125 IC (same as 74LS125) on the Disk Analog Card inside the disk drive. The 74125 IC may also result in abnormal power consumption in a Disk ][. Occasionally 74125 IC failure results in the drive uncontrollably overwriting Track $00, which destroys disks. The next most common point of failure is the MC3470 IC, which is also on the Disk Analog Card. If can be useful to test these chips by substitution with replacement or known good ICs. The ULN2003 IC, which controls the stepper motor, may also occasionally fail, resulting in absent or abnormal head movement. 
Line 117: Line 117:
 ==== TODO ==== ==== TODO ====
  
-  * Explain what all of the measurements mean.+  <del>* Explain what all of the measurements mean.</del>
  <del> * Explain what all of the tests mean.</del>  <del> * Explain what all of the tests mean.</del>
-  * Better troubleshooting.+  <del>* Better troubleshooting.</del>
   * Spindle Test: other drive types   * Spindle Test: other drive types