Category:Troubleshooting

From PC-BSD Wiki
Revision as of 21:04, 22 August 2012 by Tigersharke (Talk | contribs)

Jump to: navigation, search

Contents

"You will not apply my precept," he said, shaking his head. "How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth? We know that he did not come through the door, the window, or the chimney. We also know that he could not have been concealed in the room, as there is no concealment possible. When, then, did he come?"
--Sherlock Holmes in The Sign of the Four, ch. 6 (1890)

The Checklist

Just as Sherlock Holmes would investigate a crime, there is a bit of deductive reasoning involved in solving computer and software problems. Therefore, the first things to verify are usually the most obvious and may seem like a waste of time, but its essential to eliminate them before continuing. This generic checklist should help in your search for the truth and development of a solution to the problem.

Hardware Software
  1. Power/data is available from source
  2. Power cords are attached on both ends
  3. Data cables are attached on both ends
  4. Data cables are connected to the proper ports
  5. Cables are proper for situation
  6. Cables are clean and undamaged
  7. Power switches are in on position
  8. There is a physical indication of on and/or ready state
  9. Device is configured to accept connections, send/receive data
  10. Device temperature is within its tolerances
  11. Plugs, ports, and/or mechanisms are clean and undamaged
  12. Media matches requirements of device
  13. Necessary materials are sufficient for task
  14. Fuse or breaker has not been tripped/blown
  15. There is no unusual visible, audible, or tactile noise/effect
  16. Device(s) are capable of desired action
  1. Download was complete and successful
  2. Checksum matches that provided by the download site
  3. Software/driver is installed/loaded
  4. Software/driver recognizes existence of device(s)
  5. User has authority/access to perform action(s)
  6. Internal device settings/BIOS optimal for situation
  7. File/directory has proper permission settings
  8. Firewall is set to permit service or port traffic
  9. Service/daemon/software is enabled/running
  10. Service/daemon/software is configured or initiated properly
  11. Software exists, is present, and is current
  12. Software is executed with necessary authority/access
  13. Software has not failed silently or thrown errors
  14. Dependencies are installed and proper version
  15. Configuration/data files are readable/writable
  16. Configuration file has no typo or format flaw
  17. Software/driver is capable of desired result
  18. Software works as expected in GUI, cli, or both

Specific Areas

Additional Resources

Pages in category ‘Troubleshooting’

The following 68 pages are in this category, out of 68 total.

B

D

I

I cont.

L

N

P

P cont.

S

T

U