Little NUC not powering off with Linux?

Feek · 14 Nov 2024 at 21:48

Both Debian and Ubuntu 24.04 are doing the same. I issue a shutdown and my little NUC thing doesn't power off if it's been switched on for any longer than a few hours.

Here's the most recent entries from journalctl -b -1 -r

The OS stops, it just doesn't power off.

Code:

Nov 14 21:38:28 nuc systemd-journald[325]: Journal stopped
Nov 14 21:38:28 nuc systemd-journald[325]: Received SIGTERM from PID 1 (systemd-shutdow).
Nov 14 21:38:28 nuc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Nov 14 21:38:28 nuc systemd-shutdown[1]: Syncing filesystems and block devices.
Nov 14 21:38:28 nuc systemd[1]: Shutting down.
Nov 14 21:38:28 nuc systemd[1]: Reached target poweroff.target - System Power Off.
Nov 14 21:38:28 nuc systemd[1]: Finished systemd-poweroff.service - System Power Off.
Nov 14 21:38:28 nuc systemd[1]: systemd-poweroff.service: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: Reached target final.target - Late Shutdown Services.
Nov 14 21:38:28 nuc systemd[1]: Reached target shutdown.target - System Shutdown.
Nov 14 21:38:28 nuc systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Nov 14 21:38:28 nuc systemd[1]: lvm2-monitor.service: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
Nov 14 21:38:28 nuc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: multipathd.service: Consumed 7.774s CPU time.
Nov 14 21:38:28 nuc systemd[1]: Stopped multipathd.service - Device-Mapper Multipath Device Controller.
Nov 14 21:38:28 nuc systemd[1]: multipathd.service: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: Reached target umount.target - Unmount All Filesystems.
Nov 14 21:38:28 nuc systemd[1]: Deactivated swap swap.img.swap - /swap.img.
Nov 14 21:38:28 nuc systemd[1]: swap.img.swap: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: Stopped systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
Nov 14 21:38:28 nuc systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
Nov 14 21:38:28 nuc systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.

If I then pull the power, plug it back in, switch it on and then shutdown straight away, it works and the entries are identical to those above.

Anyone got any suggestions please? Could this be something in the bios?

I'm running headless with nothing plugged into it apart from power and ethernet.

Ta.

Throrik · 14 Nov 2024 at 22:03

There have been issues, exactly like this in NUCs due to the BIOS version they shipped with being fairly out of date - generally a BIOS upgrade should resolve it.

Feek · 14 Nov 2024 at 22:47

The BIOS is dated 2020. Can I find an updated BIOS for an Intel NUC7i3BNH? Nope, I can't even find downloads for this model.

Throrik · 14 Nov 2024 at 22:58

Feek said:
The BIOS is dated 2020. Can I find an updated BIOS for an Intel NUC7i3BNH? Nope, I can't even find downloads for this model.

NUC7I3BNH - Support

www.asus.com

Try that. Annoying as Asus now do the NUC lineup, so everything has gone over there, but it's disorganised.

Feek · 15 Nov 2024 at 08:48

Ahh thanks, I did find the Asus stuff but wasn’t sure if it was valid. ~~It’s going to be a couple of days until I can try.~~

/edit - I had a few minutes spare, so I've just done it. I'm not going to be near it for a couple of days so I'll leave it on and try and shut it down when I get back, thanks

Feek · 17 Nov 2024 at 18:43

Same thing after getting home this evening, but there were a handful of Ubuntu updates which I've applied so I'll see how it goes. Unfortunately, it's not going to be much use to me like this if it doesn't shutdown or restart cleanly.

Throrik · 17 Nov 2024 at 18:54

There are some mentions of changing settings on some of the CIR settings in the BIOS, but it's fairly dead-ended. Lots of suggestions around Intel Management Engine and/or Graphics Drivers, but they seem to be focused around Windows.

When you do a sudo reboot now from a SSH session, does it boot you out of the session, or does it keep you connected? If not, does it allow you to reconnect?

Feek · 23 Nov 2024 at 14:25

Throrik said:
When you do a sudo reboot now from a SSH session, does it boot you out of the session, or does it keep you connected? If not, does it allow you to reconnect?

There's always going to be a few days delay in me replying because if I reboot it, I can then shutdown straight away, it seems to need to be running for a while for the shutdown to fail.

The reboot actually seems to be working now, I've just rebooted it after about four days uptime and it was fine.

Clutching at straws, I've got a dummy HDMI plug coming today that emulates a monitor being connected. It's just something else to try.

Throrik · 23 Nov 2024 at 14:38

Feek said:
There's always going to be a few days delay in me replying because if I reboot it, I can then shutdown straight away, it seems to need to be running for a while for the shutdown to fail.

The reboot actually seems to be working now, I've just rebooted it after about four days uptime and it was fine.

Clutching at straws, I've got a dummy HDMI plug coming today that emulates a monitor being connected. It's just something else to try.

Do you know if you have the acpi package installed? Wondering if there are any errors in dmesg around that.

Bash:

sudo dmesg | grep -i "acpi"

Glad it seems to be working slightly better though, certainly a strange one, but they're always the fun ones to investigate when they're not mission critical.

Feek · 23 Nov 2024 at 20:42

Throrik said:
Do you know if you have the acpi package installed? Wondering if there are any errors in dmesg around that.

Here you go.

Code:

[    0.000000] BIOS-e820: [mem 0x0000000070fab000-0x0000000070fabfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007a56b000-0x000000007a5e7fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007a5e8000-0x000000007aa01fff] ACPI NVS
[    0.012296] ACPI: Early table checksum verification disabled
[    0.012300] ACPI: RSDP 0x00000000000F05B0 000024 (v02 INTEL )
[    0.012306] ACPI: XSDT 0x000000007A5840B8 0000EC (v01 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012314] ACPI: FACP 0x000000007A5B0D48 000114 (v06 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012322] ACPI: DSDT 0x000000007A584230 02CB15 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012327] ACPI: FACS 0x000000007AA01F80 000040
[    0.012331] ACPI: APIC 0x000000007A5B0E60 000084 (v03 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012336] ACPI: FPDT 0x000000007A5B0EE8 000044 (v01 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012340] ACPI: FIDT 0x000000007A5B0F30 00009C (v01 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012344] ACPI: MCFG 0x000000007A5B0FD0 00003C (v01 INTEL  NUC7i3BN 0000005D MSFT 00000097)
[    0.012349] ACPI: SSDT 0x000000007A5B1010 000359 (v01 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012354] ACPI: SSDT 0x000000007A5B1370 003163 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012358] ACPI: HPET 0x000000007A5B44D8 000038 (v01 INTEL  NUC7i3BN 0000005D MSFT 0000005F)
[    0.012363] ACPI: SSDT 0x000000007A5B4510 0009E3 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012367] ACPI: UEFI 0x000000007A5B4EF8 000048 (v01 INTEL  NUC7i3BN 0000005D      01000013)
[    0.012372] ACPI: SSDT 0x000000007A5B4F40 0017AE (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012376] ACPI: LPIT 0x000000007A5B66F0 000094 (v01 INTEL  NUC7i3BN 0000005D MSFT 0000005F)
[    0.012381] ACPI: WDAT 0x000000007A5B6788 000134 (v01 INTEL  NUC7i3BN 0000005D MSFT 0000005F)
[    0.012385] ACPI: SSDT 0x000000007A5B68C0 000141 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012390] ACPI: SSDT 0x000000007A5B6A08 00029F (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012395] ACPI: SSDT 0x000000007A5B6CA8 003002 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012399] ACPI: SSDT 0x000000007A5B9CB0 0000DB (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012404] ACPI: SSDT 0x000000007A5B9D90 0002E9 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012408] ACPI: DBGP 0x000000007A5BA080 000034 (v01 INTEL  NUC7i3BN 0000005D MSFT 0000005F)
[    0.012413] ACPI: DBG2 0x000000007A5BA0B8 000054 (v00 INTEL  NUC7i3BN 0000005D MSFT 0000005F)
[    0.012417] ACPI: SSDT 0x000000007A5BA110 0012E5 (v02 INTEL  NUC7i3BN 0000005D INTL 20160422)
[    0.012422] ACPI: DMAR 0x000000007A5BB3F8 0000A8 (v01 INTEL  NUC7i3BN 0000005D INTL 00000001)
[    0.012426] ACPI: NHLT 0x000000007A5BB4A0 00002D (v00 INTEL  NUC7i3BN 0000005D      01000013)
[    0.012431] ACPI: TPM2 0x000000007A5BB4D0 000034 (v04 INTEL  NUC7i3BN 0000005D AMI  00000000)
[    0.012435] ACPI: WSMT 0x000000007A5BB508 000028 (v01 INTEL  NUC7i3BN 0000005D AMI  00010013)
[    0.012439] ACPI: Reserving FACP table memory at [mem 0x7a5b0d48-0x7a5b0e5b]
[    0.012441] ACPI: Reserving DSDT table memory at [mem 0x7a584230-0x7a5b0d44]
[    0.012442] ACPI: Reserving FACS table memory at [mem 0x7aa01f80-0x7aa01fbf]
[    0.012444] ACPI: Reserving APIC table memory at [mem 0x7a5b0e60-0x7a5b0ee3]
[    0.012445] ACPI: Reserving FPDT table memory at [mem 0x7a5b0ee8-0x7a5b0f2b]
[    0.012446] ACPI: Reserving FIDT table memory at [mem 0x7a5b0f30-0x7a5b0fcb]
[    0.012447] ACPI: Reserving MCFG table memory at [mem 0x7a5b0fd0-0x7a5b100b]
[    0.012448] ACPI: Reserving SSDT table memory at [mem 0x7a5b1010-0x7a5b1368]
[    0.012449] ACPI: Reserving SSDT table memory at [mem 0x7a5b1370-0x7a5b44d2]
[    0.012451] ACPI: Reserving HPET table memory at [mem 0x7a5b44d8-0x7a5b450f]
[    0.012452] ACPI: Reserving SSDT table memory at [mem 0x7a5b4510-0x7a5b4ef2]
[    0.012453] ACPI: Reserving UEFI table memory at [mem 0x7a5b4ef8-0x7a5b4f3f]
[    0.012454] ACPI: Reserving SSDT table memory at [mem 0x7a5b4f40-0x7a5b66ed]
[    0.012456] ACPI: Reserving LPIT table memory at [mem 0x7a5b66f0-0x7a5b6783]
[    0.012457] ACPI: Reserving WDAT table memory at [mem 0x7a5b6788-0x7a5b68bb]
[    0.012458] ACPI: Reserving SSDT table memory at [mem 0x7a5b68c0-0x7a5b6a00]
[    0.012459] ACPI: Reserving SSDT table memory at [mem 0x7a5b6a08-0x7a5b6ca6]
[    0.012460] ACPI: Reserving SSDT table memory at [mem 0x7a5b6ca8-0x7a5b9ca9]
[    0.012462] ACPI: Reserving SSDT table memory at [mem 0x7a5b9cb0-0x7a5b9d8a]
[    0.012463] ACPI: Reserving SSDT table memory at [mem 0x7a5b9d90-0x7a5ba078]
[    0.012464] ACPI: Reserving DBGP table memory at [mem 0x7a5ba080-0x7a5ba0b3]
[    0.012465] ACPI: Reserving DBG2 table memory at [mem 0x7a5ba0b8-0x7a5ba10b]
[    0.012466] ACPI: Reserving SSDT table memory at [mem 0x7a5ba110-0x7a5bb3f4]
[    0.012468] ACPI: Reserving DMAR table memory at [mem 0x7a5bb3f8-0x7a5bb49f]
[    0.012469] ACPI: Reserving NHLT table memory at [mem 0x7a5bb4a0-0x7a5bb4cc]
[    0.012470] ACPI: Reserving TPM2 table memory at [mem 0x7a5bb4d0-0x7a5bb503]
[    0.012471] ACPI: Reserving WSMT table memory at [mem 0x7a5bb508-0x7a5bb52f]
[    0.037219] ACPI: PM-Timer IO Port: 0x1808
[    0.037229] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.037231] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.037233] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.037234] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.037265] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.037267] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.037273] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.037274] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.110906] ACPI: Core revision 20230628
[    0.127949] ACPI: PM: Registering ACPI NVS region [mem 0x70fab000-0x70fabfff] (4096 bytes)
[    0.127958] ACPI: PM: Registering ACPI NVS region [mem 0x7a5e8000-0x7aa01fff] (4300800 bytes)
[    0.130137] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.130137] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.131135] ACPI: Added _OSI(Module Device)
[    0.131142] ACPI: Added _OSI(Processor Device)
[    0.131148] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.131153] ACPI: Added _OSI(Processor Aggregator Device)
[    0.195995] ACPI: 11 ACPI AML tables successfully acquired and loaded
[    0.208378] ACPI: Dynamic OEM Table Load:
[    0.208393] ACPI: SSDT 0xFFFF933E017C5000 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
[    0.210730] ACPI: Dynamic OEM Table Load:
[    0.210742] ACPI: SSDT 0xFFFF933E01CA5000 000651 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
[    0.214155] ACPI: Dynamic OEM Table Load:
[    0.214170] ACPI: SSDT 0xFFFF933E01CA8000 000D14 (v02 PmRef  ApIst    00003000 INTL 20160422)
[    0.217751] ACPI: Dynamic OEM Table Load:
[    0.217762] ACPI: SSDT 0xFFFF933E017C4000 000317 (v02 PmRef  ApHwp    00003000 INTL 20160422)
[    0.220090] ACPI: Dynamic OEM Table Load:
[    0.220105] ACPI: SSDT 0xFFFF933E017C4C00 00030A (v02 PmRef  ApCst    00003000 INTL 20160422)
[    0.225386] ACPI: _OSC evaluated successfully for all CPUs
[    0.225542] ACPI: EC: EC started
[    0.225546] ACPI: EC: interrupt blocked
[    0.228507] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.228514] ACPI: \_SB_.PCI0.LPCB.H_EC: Boot DSDT EC used to handle transactions
[    0.228520] ACPI: Interpreter enabled
[    0.228583] ACPI: PM: (supports S0 S3 S4 S5)
[    0.228588] ACPI: Using IOAPIC for interrupt routing
[    0.231615] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.233447] ACPI: Enabled 7 GPEs in block 00 to 7F
[    0.247089] ACPI: \_SB_.PCI0.RP06.PXSX.WRST: New power resource
[    0.286241] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[    0.286257] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
[    0.286443] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME AER]
[    0.286775] acpi PNP0A08:00: _OSC: OS now controls [PCIeCapability LTR DPC]
[    0.286782] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.304217] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
[    0.304317] ACPI: PCI: Interrupt link LNKB configured for IRQ 10
[    0.304412] ACPI: PCI: Interrupt link LNKC configured for IRQ 11
[    0.304508] ACPI: PCI: Interrupt link LNKD configured for IRQ 11
[    0.304604] ACPI: PCI: Interrupt link LNKE configured for IRQ 11
[    0.304700] ACPI: PCI: Interrupt link LNKF configured for IRQ 11
[    0.304797] ACPI: PCI: Interrupt link LNKG configured for IRQ 11
[    0.304894] ACPI: PCI: Interrupt link LNKH configured for IRQ 11
[    0.310188] ACPI: EC: interrupt unblocked
[    0.310194] ACPI: EC: event unblocked
[    0.310202] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.310206] ACPI: EC: GPE=0x14
[    0.310210] ACPI: \_SB_.PCI0.LPCB.H_EC: Boot DSDT EC initialization complete
[    0.310217] ACPI: \_SB_.PCI0.LPCB.H_EC: EC: Used to handle transactions and events
[    0.310321] ACPI: bus type USB registered
[    0.311343] PCI: Using ACPI for IRQ routing
[    0.336154] pnp: PnP ACPI init
[    0.342498] pnp: PnP ACPI: found 9 devices
[    0.348835] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.404226] ACPI: button: Sleep Button [SLPB]
[    0.404300] ACPI: button: Power Button [PWRB]
[    0.404408] ACPI: button: Power Button [PWRF]
[    0.404846] ACPI: thermal: [Firmware Bug]: No valid trip points!
[    0.408380] hpet_acpi_add: no address or irqs in _CRS
[    0.424158] ACPI: bus type drm_connector registered
[    1.406443] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
[    1.407653] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
[    1.449264] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
[    1.450406] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
[    5.326435] ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)

Throrik · 24 Nov 2024 at 06:34

There's nothing super-obvious in there, but I admit I'm not the leading expert for reading ACPI dmesg stuff. I've read a few cases where it's still be linked to ACPI despite no warnings, but that's a rabbit hole and a half where you can modify kernel parameters and/or grub to force ACPI, but if your system is working to a decent degree it might not necessarily be worth it.

Manbatius · 24 Nov 2024 at 07:36

Heh, fair play for trying to fix it, my plex based Intel n3060 has done this for years. Numerous linux distributions through that time and the previous motherboard did the same.
I suppose it does not bother me as its mainly always on, when there is an update.... it does not restart is only time it bother me.

Feek · 25 Nov 2024 at 15:51

Feek said:
Clutching at straws, I've got a dummy HDMI plug coming today that emulates a monitor being connected. It's just something else to try.

This made no difference, I'm not really surprised.

Manbatius said:
I suppose it does not bother me as its mainly always on, when there is an update.... it does not restart is only time it bother me.

It does bother me

Throrik · 25 Nov 2024 at 16:34

Do me a favour and try a "poweroff -f" that will give us more indication of if it's kernel of systemd.

Getting a bit more into the weeds, dependent on if your SSH connection dies or not, you might need a monitor but if you run:

Bash:

sudo systemctl start debug-shell
sudo shutdown now

Then, when it doesn't shutdown hit Ctrl+Alt+F9 and run:

Bash:

systemctl list-jobs
dmesg

Both separate commands, but send an output of both if you can.