Difference between revisions of "Basic Hardware Troubleshooting"
Jump to navigation
Jump to search
Basic Hardware Troubleshooting
Hard Drive Problems or Perceived Failures:
Drew Harrell (talk | contribs) |
John Wolfe (talk | contribs) |
||
| Line 3: | Line 3: | ||
This guide is intended to provide the Ipitomy Technician with a guideline for troubleshooting common PBX hardware issues. It covers some of the most common issues upon installation of new PBX hardware. | This guide is intended to provide the Ipitomy Technician with a guideline for troubleshooting common PBX hardware issues. It covers some of the most common issues upon installation of new PBX hardware. | ||
| − | #One of the most common problems when first setting up a PBX is a License issue. this is typically exhibited in powering on and being brought in the Web Administration to a Licensing Page. If this happens, you should confirm that the PBX is connected to a Network with Internet connectivity, and additionally that the PBX can navigate this internet connection with the connection settings which have been configured. The PBX upon first booting, verifies its license with the servers here at Ipitomy. | + | #One of the most common problems when first setting up a PBX is a License issue. this is typically exhibited in powering on and being brought in the Web Administration to a Licensing Page. If this happens, you should confirm that the PBX is connected to a Network with Internet connectivity, and additionally that the PBX can navigate this internet connection with the connection settings which have been configured. The PBX upon first booting, verifies its license with the servers here at Ipitomy. |
| − | #Another common issue when first un-boxing a PBX and setting it up is that it will not power up. The least likely problem when this happens is faulty hardware as hardware is exhaustively tested before shipment. More likely is that a component in the PBX has been loosened from the transit in shipping. If this occurs, simply open the case and re-seat the following<br/><br/>RAM Memory Power and Data connection to Hard Drive Data Connection from hard drive on motherboard And PCI cards installed on the system Riser and Extender cards on System.<br/><br/>In 99% of cases this will correct any issue you might have. | + | #Another common issue when first un-boxing a PBX and setting it up is that it will not power up. The least likely problem when this happens is faulty hardware as hardware is exhaustively tested before shipment. More likely is that a component in the PBX has been loosened from the transit in shipping. If this occurs, simply open the case and re-seat the following<br/><br/>RAM Memory Power and Data connection to Hard Drive Data Connection from hard drive on motherboard And PCI cards installed on the system Riser and Extender cards on System.<br/><br/>In 99% of cases this will correct any issue you might have. |
#We have noted that occasionally systems might exhibit what may be referred to as IRQ issues. Or external peripheral issues. These are commonly exhibited by a non responsive system, and or, a system in which peripheral card are not working though they appear to be fine. Or also a loss of Web Admin connectivity. If you run into any of the previously named issues, you should:<br/><br/>Remove all Keyboards, USB devices, and Monitors. And then reboot. If this step corrects your issue it is possible that one of the removed devices is bad and is causing IRQ conflicts. Typically this is a Keyboard or USB device issue. Try a different Keyboard or USB device. Or leave them disconnected.<br/><br/>Another way for this to occur is bad power issues all cards are not recognized, or the system will not keep a proper time. Try is to power the system off for at least 5 minutes without power connected (disconnect from power outlet). Make sure that any visible LEDs have turned off before reconnecting to the power outlet. This often will clear the issue. | #We have noted that occasionally systems might exhibit what may be referred to as IRQ issues. Or external peripheral issues. These are commonly exhibited by a non responsive system, and or, a system in which peripheral card are not working though they appear to be fine. Or also a loss of Web Admin connectivity. If you run into any of the previously named issues, you should:<br/><br/>Remove all Keyboards, USB devices, and Monitors. And then reboot. If this step corrects your issue it is possible that one of the removed devices is bad and is causing IRQ conflicts. Typically this is a Keyboard or USB device issue. Try a different Keyboard or USB device. Or leave them disconnected.<br/><br/>Another way for this to occur is bad power issues all cards are not recognized, or the system will not keep a proper time. Try is to power the system off for at least 5 minutes without power connected (disconnect from power outlet). Make sure that any visible LEDs have turned off before reconnecting to the power outlet. This often will clear the issue. | ||
| Line 16: | Line 16: | ||
As long as you have a backup of the system, the above process will allow you to restore the Boot sector and software of a Hard Drive and reload. Then it is simply a matter of restoring your backup. If the drive is actually in a failure state, you can also simply purchase a new drive and reload it using this same process. | As long as you have a backup of the system, the above process will allow you to restore the Boot sector and software of a Hard Drive and reload. Then it is simply a matter of restoring your backup. If the drive is actually in a failure state, you can also simply purchase a new drive and reload it using this same process. | ||
| + | |||
| + | |||
| + | |||
| + | Generally Hard Drive failures fall into two categories. The first is recognized by attaching a monitor and keyboard to the system. If you note that the system has performed a Hard Disk check, but is reporting to press Control + D to drop to a Shell, then it would be neccesary at this point to run a recovery dongle repair. The instructions for the creation and repair may be found by following this link. | ||
| + | |||
| + | [http://wiki.ipitomy.com/wiki/USB_Recovery_Dongle http://wiki.ipitomy.com/wiki/USB_Recovery_Dongle] | ||
| + | |||
| + | |||
| + | |||
| + | This dongle allows for an easy run of FSCK to repair the drive errors. | ||
| + | |||
| + | |||
| + | |||
| + | The second failure which is common is when the FSCK finds errors it cannot repair. If this occurs the frst thing to try is to run the Install Dongle which is described in the link above. Failing this would mean you would need to possibly replace the drive. At this point you should also contact Ipitomy Support so that a support technician may go over the issue with you. | ||
Revision as of 12:04, 1 July 2014
Basic Hardware Troubleshooting
This guide is intended to provide the Ipitomy Technician with a guideline for troubleshooting common PBX hardware issues. It covers some of the most common issues upon installation of new PBX hardware.
- One of the most common problems when first setting up a PBX is a License issue. this is typically exhibited in powering on and being brought in the Web Administration to a Licensing Page. If this happens, you should confirm that the PBX is connected to a Network with Internet connectivity, and additionally that the PBX can navigate this internet connection with the connection settings which have been configured. The PBX upon first booting, verifies its license with the servers here at Ipitomy.
- Another common issue when first un-boxing a PBX and setting it up is that it will not power up. The least likely problem when this happens is faulty hardware as hardware is exhaustively tested before shipment. More likely is that a component in the PBX has been loosened from the transit in shipping. If this occurs, simply open the case and re-seat the following
RAM Memory Power and Data connection to Hard Drive Data Connection from hard drive on motherboard And PCI cards installed on the system Riser and Extender cards on System.
In 99% of cases this will correct any issue you might have. - We have noted that occasionally systems might exhibit what may be referred to as IRQ issues. Or external peripheral issues. These are commonly exhibited by a non responsive system, and or, a system in which peripheral card are not working though they appear to be fine. Or also a loss of Web Admin connectivity. If you run into any of the previously named issues, you should:
Remove all Keyboards, USB devices, and Monitors. And then reboot. If this step corrects your issue it is possible that one of the removed devices is bad and is causing IRQ conflicts. Typically this is a Keyboard or USB device issue. Try a different Keyboard or USB device. Or leave them disconnected.
Another way for this to occur is bad power issues all cards are not recognized, or the system will not keep a proper time. Try is to power the system off for at least 5 minutes without power connected (disconnect from power outlet). Make sure that any visible LEDs have turned off before reconnecting to the power outlet. This often will clear the issue.
Hard Drive Problems or Perceived Failures:
A common problem which is encountered in systems, is Power interruptions which cause Boot Sector corruption of Hard Drives. If you encounter an issue where the system will not boot fully and you think you may possibly have a Hard Disk Failure, you should attempt a reinstall of the software using the USB Install Recovery option.
http://wiki.ipitomy.com/wiki/USB_Install_Dongle
As long as you have a backup of the system, the above process will allow you to restore the Boot sector and software of a Hard Drive and reload. Then it is simply a matter of restoring your backup. If the drive is actually in a failure state, you can also simply purchase a new drive and reload it using this same process.
Generally Hard Drive failures fall into two categories. The first is recognized by attaching a monitor and keyboard to the system. If you note that the system has performed a Hard Disk check, but is reporting to press Control + D to drop to a Shell, then it would be neccesary at this point to run a recovery dongle repair. The instructions for the creation and repair may be found by following this link.
http://wiki.ipitomy.com/wiki/USB_Recovery_Dongle
This dongle allows for an easy run of FSCK to repair the drive errors.
The second failure which is common is when the FSCK finds errors it cannot repair. If this occurs the frst thing to try is to run the Install Dongle which is described in the link above. Failing this would mean you would need to possibly replace the drive. At this point you should also contact Ipitomy Support so that a support technician may go over the issue with you.