Home server becomes unresponsive after indeterminate time











up vote
0
down vote

favorite












I've been having an issue with a home server of mine (mostly used for plex) becoming unresponsive after steadily decreasing amounts of time.



I originally noticed the issue a few months ago but put off dealing with it as it was only occurring around once every two weeks. In the last week however the issue has increased in frequency to the point where it locks up every few hours.



I was originally running ubuntu 17.10, then upgraded to 18.04 with the issue occurring consistently for each operating system. After spending days poring over the logs and being unable to find anything of substance and at my wits end I decided to start from scratch with a minimal install of Centos 7. On this I just installed docker then ran plex as a containerised service, this seemed to be working fine during the install, yet, sure enough, come that evening the server had become unresponsive again.



I then suspected that maybe there was an issue with the memory so I ran a memory test which returned a clean bill of health and ran fsck's on all the devices disks which returned no issues



The nature of this 'unresponsiveness' is that there is no output to the connected monitor and no response from any keyboard or mouse input. Additionally any ssh sessions currently active on the machine will freeze and become unresponsive.



One odd thing is that the machine will, at least in the early stages of its 'unresponsiveness', respond to pings and any new ssh sessions I attempt to open will just hang as if waiting for a response. However, after some time this behaviour ceases and the device simply appears to not exist on the network.



The whole time this is happening the device appears to be operating fine with all fans, leds etc. operating apparently normally.



Any help with this would be greatly appreciated as I am somewhat at a loss as to how to proceed.



The Components of my computer are as follows:



Motherboard: GIGABYTE GA-AB350M-Gaming 3
CPU: AMD Ryzen 5 1600 Desktop CPU
GPU: MSI NVIDIA GeForce GTX 1060 GAMING X 6 GB GDDR5
RAM: Corsair CMK16GX4M2B3000C15 Vengeance LPX 16 GB (2 x 8 GB) DDR4 3000 MHz
SSD: Crucial CT512MX100SSD1 512GB MX100 SATA
PSU: EVGA 650 W G2 GOLD 80+ Modular PC Power Supply Unit
Additional Storage: 2 x Seagate 4 TB BarraCuda 3.5 Inch 5400 RPM Internal Hard Drive









share|improve this question







New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
    – GabrielaGarcia
    Nov 15 at 12:09










  • It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
    – tannart
    Nov 15 at 12:54






  • 1




    Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
    – GabrielaGarcia
    Nov 15 at 12:59










  • I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
    – tannart
    Nov 15 at 13:31










  • The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
    – GabrielaGarcia
    Nov 15 at 14:13















up vote
0
down vote

favorite












I've been having an issue with a home server of mine (mostly used for plex) becoming unresponsive after steadily decreasing amounts of time.



I originally noticed the issue a few months ago but put off dealing with it as it was only occurring around once every two weeks. In the last week however the issue has increased in frequency to the point where it locks up every few hours.



I was originally running ubuntu 17.10, then upgraded to 18.04 with the issue occurring consistently for each operating system. After spending days poring over the logs and being unable to find anything of substance and at my wits end I decided to start from scratch with a minimal install of Centos 7. On this I just installed docker then ran plex as a containerised service, this seemed to be working fine during the install, yet, sure enough, come that evening the server had become unresponsive again.



I then suspected that maybe there was an issue with the memory so I ran a memory test which returned a clean bill of health and ran fsck's on all the devices disks which returned no issues



The nature of this 'unresponsiveness' is that there is no output to the connected monitor and no response from any keyboard or mouse input. Additionally any ssh sessions currently active on the machine will freeze and become unresponsive.



One odd thing is that the machine will, at least in the early stages of its 'unresponsiveness', respond to pings and any new ssh sessions I attempt to open will just hang as if waiting for a response. However, after some time this behaviour ceases and the device simply appears to not exist on the network.



The whole time this is happening the device appears to be operating fine with all fans, leds etc. operating apparently normally.



Any help with this would be greatly appreciated as I am somewhat at a loss as to how to proceed.



The Components of my computer are as follows:



Motherboard: GIGABYTE GA-AB350M-Gaming 3
CPU: AMD Ryzen 5 1600 Desktop CPU
GPU: MSI NVIDIA GeForce GTX 1060 GAMING X 6 GB GDDR5
RAM: Corsair CMK16GX4M2B3000C15 Vengeance LPX 16 GB (2 x 8 GB) DDR4 3000 MHz
SSD: Crucial CT512MX100SSD1 512GB MX100 SATA
PSU: EVGA 650 W G2 GOLD 80+ Modular PC Power Supply Unit
Additional Storage: 2 x Seagate 4 TB BarraCuda 3.5 Inch 5400 RPM Internal Hard Drive









share|improve this question







New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
    – GabrielaGarcia
    Nov 15 at 12:09










  • It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
    – tannart
    Nov 15 at 12:54






  • 1




    Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
    – GabrielaGarcia
    Nov 15 at 12:59










  • I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
    – tannart
    Nov 15 at 13:31










  • The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
    – GabrielaGarcia
    Nov 15 at 14:13













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I've been having an issue with a home server of mine (mostly used for plex) becoming unresponsive after steadily decreasing amounts of time.



I originally noticed the issue a few months ago but put off dealing with it as it was only occurring around once every two weeks. In the last week however the issue has increased in frequency to the point where it locks up every few hours.



I was originally running ubuntu 17.10, then upgraded to 18.04 with the issue occurring consistently for each operating system. After spending days poring over the logs and being unable to find anything of substance and at my wits end I decided to start from scratch with a minimal install of Centos 7. On this I just installed docker then ran plex as a containerised service, this seemed to be working fine during the install, yet, sure enough, come that evening the server had become unresponsive again.



I then suspected that maybe there was an issue with the memory so I ran a memory test which returned a clean bill of health and ran fsck's on all the devices disks which returned no issues



The nature of this 'unresponsiveness' is that there is no output to the connected monitor and no response from any keyboard or mouse input. Additionally any ssh sessions currently active on the machine will freeze and become unresponsive.



One odd thing is that the machine will, at least in the early stages of its 'unresponsiveness', respond to pings and any new ssh sessions I attempt to open will just hang as if waiting for a response. However, after some time this behaviour ceases and the device simply appears to not exist on the network.



The whole time this is happening the device appears to be operating fine with all fans, leds etc. operating apparently normally.



Any help with this would be greatly appreciated as I am somewhat at a loss as to how to proceed.



The Components of my computer are as follows:



Motherboard: GIGABYTE GA-AB350M-Gaming 3
CPU: AMD Ryzen 5 1600 Desktop CPU
GPU: MSI NVIDIA GeForce GTX 1060 GAMING X 6 GB GDDR5
RAM: Corsair CMK16GX4M2B3000C15 Vengeance LPX 16 GB (2 x 8 GB) DDR4 3000 MHz
SSD: Crucial CT512MX100SSD1 512GB MX100 SATA
PSU: EVGA 650 W G2 GOLD 80+ Modular PC Power Supply Unit
Additional Storage: 2 x Seagate 4 TB BarraCuda 3.5 Inch 5400 RPM Internal Hard Drive









share|improve this question







New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I've been having an issue with a home server of mine (mostly used for plex) becoming unresponsive after steadily decreasing amounts of time.



I originally noticed the issue a few months ago but put off dealing with it as it was only occurring around once every two weeks. In the last week however the issue has increased in frequency to the point where it locks up every few hours.



I was originally running ubuntu 17.10, then upgraded to 18.04 with the issue occurring consistently for each operating system. After spending days poring over the logs and being unable to find anything of substance and at my wits end I decided to start from scratch with a minimal install of Centos 7. On this I just installed docker then ran plex as a containerised service, this seemed to be working fine during the install, yet, sure enough, come that evening the server had become unresponsive again.



I then suspected that maybe there was an issue with the memory so I ran a memory test which returned a clean bill of health and ran fsck's on all the devices disks which returned no issues



The nature of this 'unresponsiveness' is that there is no output to the connected monitor and no response from any keyboard or mouse input. Additionally any ssh sessions currently active on the machine will freeze and become unresponsive.



One odd thing is that the machine will, at least in the early stages of its 'unresponsiveness', respond to pings and any new ssh sessions I attempt to open will just hang as if waiting for a response. However, after some time this behaviour ceases and the device simply appears to not exist on the network.



The whole time this is happening the device appears to be operating fine with all fans, leds etc. operating apparently normally.



Any help with this would be greatly appreciated as I am somewhat at a loss as to how to proceed.



The Components of my computer are as follows:



Motherboard: GIGABYTE GA-AB350M-Gaming 3
CPU: AMD Ryzen 5 1600 Desktop CPU
GPU: MSI NVIDIA GeForce GTX 1060 GAMING X 6 GB GDDR5
RAM: Corsair CMK16GX4M2B3000C15 Vengeance LPX 16 GB (2 x 8 GB) DDR4 3000 MHz
SSD: Crucial CT512MX100SSD1 512GB MX100 SATA
PSU: EVGA 650 W G2 GOLD 80+ Modular PC Power Supply Unit
Additional Storage: 2 x Seagate 4 TB BarraCuda 3.5 Inch 5400 RPM Internal Hard Drive






linux ubuntu centos hardware-failure






share|improve this question







New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 15 at 10:07









tannart

11




11




New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
    – GabrielaGarcia
    Nov 15 at 12:09










  • It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
    – tannart
    Nov 15 at 12:54






  • 1




    Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
    – GabrielaGarcia
    Nov 15 at 12:59










  • I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
    – tannart
    Nov 15 at 13:31










  • The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
    – GabrielaGarcia
    Nov 15 at 14:13


















  • So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
    – GabrielaGarcia
    Nov 15 at 12:09










  • It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
    – tannart
    Nov 15 at 12:54






  • 1




    Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
    – GabrielaGarcia
    Nov 15 at 12:59










  • I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
    – tannart
    Nov 15 at 13:31










  • The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
    – GabrielaGarcia
    Nov 15 at 14:13
















So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
– GabrielaGarcia
Nov 15 at 12:09




So you have gaming rig just sitting there in the network as a media server? Something that a Raspberry Pi or similar or even an Android box could do perfectly?
– GabrielaGarcia
Nov 15 at 12:09












It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
– tannart
Nov 15 at 12:54




It used to be my gaming rig but I just haven't been interested in gaming for a while. I use it for a few other things in addition to plex which require more large-scale processing power and I'll probably start gaming on it again at some point in the future, providing I can fix this issue of course.
– tannart
Nov 15 at 12:54




1




1




Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
– GabrielaGarcia
Nov 15 at 12:59




Such issues are very hard to troubleshoot. Other than recommending the usual stuff - update BIOS/UEFI and drivers - I can't think of anything else. And knowing the same happens with a minimal Linux it could be hardware problems very hard to pinpoint.
– GabrielaGarcia
Nov 15 at 12:59












I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
– tannart
Nov 15 at 13:31




I haven't actually tried updating the bios so maybe I'll give that a shot, Then I guess I'll see how long I can keep a usb booted distro running for to rule out anything related to the hard drive. Not sure how I can diagnose an issue with the motherboard or psu short of buying another and swapping them out. Thanks for the suggestion.
– tannart
Nov 15 at 13:31












The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
– GabrielaGarcia
Nov 15 at 14:13




The devices I suggested for the purpose in the first comment also require 1/20 of the electricity power you're using with this one. Something that perhaps you should factor in.
– GabrielaGarcia
Nov 15 at 14:13










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










So as per GabrielGarcia's suggestion I flashed the BIOS with the most recent version and that seems to have resolved the issue.






share|improve this answer








New contributor




tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });






    tannart is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375617%2fhome-server-becomes-unresponsive-after-indeterminate-time%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    So as per GabrielGarcia's suggestion I flashed the BIOS with the most recent version and that seems to have resolved the issue.






    share|improve this answer








    New contributor




    tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote



      accepted










      So as per GabrielGarcia's suggestion I flashed the BIOS with the most recent version and that seems to have resolved the issue.






      share|improve this answer








      New contributor




      tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        So as per GabrielGarcia's suggestion I flashed the BIOS with the most recent version and that seems to have resolved the issue.






        share|improve this answer








        New contributor




        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        So as per GabrielGarcia's suggestion I flashed the BIOS with the most recent version and that seems to have resolved the issue.







        share|improve this answer








        New contributor




        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 2 days ago









        tannart

        11




        11




        New contributor




        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        tannart is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






















            tannart is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            tannart is a new contributor. Be nice, and check out our Code of Conduct.













            tannart is a new contributor. Be nice, and check out our Code of Conduct.












            tannart is a new contributor. Be nice, and check out our Code of Conduct.















             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375617%2fhome-server-becomes-unresponsive-after-indeterminate-time%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕