Twice last week I had to remove and re-install two pieces of hardware!
First it was a USB 3.2 case mounted interface. One of the ports stopped working and dmesg suggested is was a "bad cable?" I powered down, pulled the USB motherboard connector and re-inserted it. On powerup, all worked as before.
Then a few days later, I walked into my office and the screens were black and unresponsive. A hard reset revealed a BIOS code (via mobo mounted LCD) that meant "no graphics device found". This started my heart beating faster! My video card is water cooled and not exactly easy to get to without draining the water system. I feared days of work to even find out if it was OK or not. Fortunately, when I opened the case, I was able to release the video card from it's slot enough and re-seat it. Again, powerup worked normally.
The above reminds my of the "olden days" of computing when excessive heat often caused random malfunctions. Almost anytime you had what looked to be was a mechanical failure, taking everything out and re-installing was the first trouble-shooting step required. This PC build is almost exactly 4 years old.
First it was a USB 3.2 case mounted interface. One of the ports stopped working and dmesg suggested is was a "bad cable?" I powered down, pulled the USB motherboard connector and re-inserted it. On powerup, all worked as before.
Then a few days later, I walked into my office and the screens were black and unresponsive. A hard reset revealed a BIOS code (via mobo mounted LCD) that meant "no graphics device found". This started my heart beating faster! My video card is water cooled and not exactly easy to get to without draining the water system. I feared days of work to even find out if it was OK or not. Fortunately, when I opened the case, I was able to release the video card from it's slot enough and re-seat it. Again, powerup worked normally.
The above reminds my of the "olden days" of computing when excessive heat often caused random malfunctions. Almost anytime you had what looked to be was a mechanical failure, taking everything out and re-installing was the first trouble-shooting step required. This PC build is almost exactly 4 years old.
I'm getting old and forgetful at times though. 
Comment