I recently acuired a secondhand NUC8I5BEH and installed proxmox on it. But it randomly is unreachable from my LAN. There are no errors in syslog. When I connect a monitor there is no signal. So the NUC seems crashed. The fan is spinning and the LAN lights are on. It’s not viewable on my unifi controller and it’s not pingable. Where can I start looking for the problem?

  • Bitswap@lemmy.worldEnglish
    8·
    5 months ago

    Try adding a HDMI dummy plug. Older Intel NUC’s (8th gen and earlier) have an issue that’s fixed (but always seems to come back…) where they don’t like functioning headlessly (without a display connected.)

    Edit: Also, make sure your BIOS is uptodate.

    • Guadin@k.fe.derate.meOP
      2·
      5 months ago

      Hmm, this does sound like it makes sense. I got the feeling that as soon as I removed the monitor it would stop working in a couple of minutes. But I thought that couldn’t be. Thanks for the tip! Going to see if that helps and I’m going to update the BIOS.

  • some_guy@lemmy.sdf.org
    2·
    5 months ago

    Try following some of the advice in this thread. Hardware tests if the BIOS supports it. Maybe try underclocking or undervolting the CPU is BIOS supports that. If you can pull a RAM chip and test with just one, then test the chips individually in each slot, that’d be something worth trying. I’m shooting from the hip, but these are things that could help isolate a possible hardware issue.

  • Lem453@lemmy.caEnglish
    2·
    5 months ago

    First thing I would do is boot a live Ubuntu image from a USB. Make sure the hardware all works as expected.

      • LifeBandit666@feddit.ukEnglish
        2·
        5 months ago

        Try a live Proxmox USB, it’s what I did when my machine went unresponsive. Allowed me to look through the logs of the OS when it hadn’t booted to find out what went wrong.

        For me it was that I had put my USB HDDs in via Fstab and one had died, which made Proxmox unbootable until I hashtagged the lines out in fstab.

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    5 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    LXC Linux Containers
    NUC Next Unit of Computing brand of Intel small computers
    NVMe Non-Volatile Memory Express interface for mass storage

    [Thread #800 for this sub, first seen 12th Jun 2024, 06:55] [FAQ] [Full list] [Contact] [Source code]

  • PassingThrough@lemmy.worldEnglish
    1·
    5 months ago

    Plug it into a monitor or TV and keep an eye on the console.

    I have an older NUC that will not cooperate with certain brands of NVMe drive under PVE…the issue sounds like yours where it would work for an arbitrary amount of time before crashing the file system, attempting to remount read-only and rendering the system inert and unable to handle changes like plugging a monitor in later, yet it would still be “on”.

    • Guadin@k.fe.derate.meOP
      2·
      5 months ago

      Thanks, going to do this as well. I had it on a monitor for a while and all looked fine while logged in on the console. Would be a bummer though if this would be true.

  • skysurfer@lemmy.worldEnglish
    1·
    5 months ago

    Any chance you are using a Thunderbolt device such as a network adapter or external drives? I had the issue on a NUC 10 where it would randomly drop the TB devices every few weeks and occasionally appear to be frozen. The latest firmware update finally took care of it.