What do you do if a computer hardware component fails during a critical system upgrade?

If a piece of computer hardware fails during an upgrade you should do the following in my experience: 1. Definitely stop the upgrade immediately and determine which hardware component has failed. 2. Isolate the failed component by shutting down the system and disconnecting the failed component if possible to prevent further damage. 3. Notify Managers, Team Members, vendors and end-users about the hardware failure and potential impact on the upgrade timeline and system availability. 4. Check to see if you have a backup hardware component available or if the system is under warranty to install new component. 5. Resume with the upgrade. 6. Monitor the system to make sure everything is working correctly. 7. Document incident for Future

* If a piece of computer hardware fails during an upgrade process. The unit needs to be powered down and replaced with a spare in order to minimize the downtime. * It's important to assess the damage hardware piece. Before doing any type of assessment make sure that you have a spare part for the damaged one. Or you're going to down a certain amount of time before you get the replacement part.

first I prepare a mitigation plan. I.e. I did a hardware upgrade to 3 SAP HANA Systems this year, but previously I prepared a plan that replicates the databases and a checklist to start the secondary copy if primary fails. After testing the plan in a sandbox machine, I did the hardware upgrade to the 3 servers.

Primeira coisa a ser feita é encerrar a atualiza??o, depois avaliar a extens?o dos danos causados, depois de identificar a causa, entrar em contato com um especialista para se ter orienta??o da melhor forma de contornar e tratar a falha.

I perform a rollback, generally the hardware has a configuration that when there is a failure it automatically returns to the previous configurations, a good example is the motherboard bios

* When trying to isolate an issue it can become easy or complex depending on the problem at hand. * When isolating the problem is key to see whether it's a physical or software problem. Again, going to through the necessary steps is important in any type of troubleshooting technique.

Isolating the issue was one of the first steps I spoke of in "Assess Damage". Identifying the symptom. For example, if VPN was used recently, and not being used currently and the desktop PC is unable to access the internet, the first step would be to reset Firewall to default. VPN applications change firewall settings. Another example to rule out software would be to boot the system in Safe Mode.

I once had a computer not boot because of a wired mouse. Yes, the mouse. It was a PS/2 connector and it was shorted out. Don’t discard any potential failure modes. Think in terms of FMEA (Failure Mode and Effects Analysis). Unplug all non-essential hardware, including the upgraded components and try again with the last known good hardware configuration. Document your steps along the way. This could be a troubleshooting guide later, also, you’ll want to provide detailed troubleshooting information to any hardware vendor if you need to contact them.

Must check the version hardware before doing upgrade. Because sometime for old computer cannot be upgrade with the new components

En cas d'urgence, aidez les autres en partageant vos connaissances, expériences et solutions pour résoudre les problèmes informatiques

* The manual for the hardware component is a good reference to use. Especially, when you're not too familiar with the product. * The manual will have certain troubleshooting tips to do when trying the resolve the issue. It can be certain flashes of LED light and sounds.

Consult the product manual if the device is proprietary or if error codes are given via beeps, led flashes, or via a combination of lit and unlit leds that may be present on the particular device. Contact the vendor for hardware support or guidance if none of the above apply.

Manuals are the first stop. Likely the manufacturer website has diagnostic software that you can use or even an online troubleshooting platform. Reddit and YouTube are goldmines of information as well, but don’t blindly trust everything you read/watch. Use your better judgment.

Of course need to read the specs of the computer when we want to upgrade. Because if not we can wrong buy the components so it is won't work

When taking help: Be specific on the issue as you are seaking help from an professional don't confuse him with various questions and try to elaborate the steps you took to solve the problem

* When you are seeking for additional help assistance contacting the manufacturer's customer service is a good idea. * The merchant from where you purchased it from is more familiar with their own product and generally can help resolve the issue quicker.

Critical system hardware used in an upgrade are typically new and from major manufactures (Dell, HP, etc). It is important to have a warrantee on new hardware with a rapid replacement guarantee, typically this is 4 hours. Not having such warrantee's is something I personally would consider negligent of the client purchasing the hardware. The most critical component of a major systems upgrade is backups! It cannot be stressed enough that good reliable & tested backups are your key to success.

If you've done all that you know to do, the next step is to contact the manufacturer for technical support. Online communities are great as well, but no ones knows the system better than the manufacturer. For example, there could be multiple systemboard revisions and on a particular revision board, they changed the manufacturer of a particular chip on that board or utilized a completely different chip altogether; which could require a different troubleshooting approach to resolve.

Always try the manufacturer first. It’s best for warranty purposes. Make sure that you’ve provided detailed troubleshooting information to them and follow their process, even if you already did it before on your own. It’s frustrating, but they have procedures to follow.

* Testing the components within the hardware is key. * Especially, if it's physical piece such as physical RAM, hard drive. motherboard, etc. * Most of the time you can swap out the bad hardware piece and replace it with a new one.

For critical hardware you likely have some form of redundancy whenever possible. At this point you need to remember what the mission is. To keep the hardware up and running. Perform your tests and if you get a working configuration, stop troubleshooting. Get the hardware back online and regroup. Perform a proper FMEA (Failure Mode and Effects Analysis) and come back with a new plan. This might mean forgoing the upgrade altogether, and sometimes, that’s OK. Don’t lose mind of the business need. Sometimes we get caught up in fixing mode and we lose sight of downtime and the actual purpose of the upgrade, increasing efficiency. Downtime for troubleshooting is not efficient.

Troubleshooting 101 - isolate the issues. I’ve seen many techs who change multiple things at a time when troubleshooting only to find they can never isolate the exact issue. Slow down, use reasoning to eliminate possibilities and then run down the logical troubleshooting steps. Slow down and think!

It is important to check the type of the components. To prevent failure when upgrading. Example like the type of ram, maximum capacity the motherboard can read for the RAM

Keep in mind that many manufacturers have support for the devices you are managing. Always reach out to see if they can overnight parts to you. I have also experienced where if you are a high enough level customer the manufacturer may allow you to keep critical spare parts on hand. Having these spare parts on hand can be life changing depending on the hardware.

Always give notice of the issue to your colleagues and upper management at the very moment of the failure to cover any trouble it could generate