42
Linux server hangs on shutdown (lemmy.fish)
submitted 1 year ago by to c/linux@lemmy.ml
53 comments fedilink hide all child comments
 

I've had two server oses here: alma linux and debian(currently). On both of them, they will hang when I shut them down from cockpit, and they hang at the end of the shutdown.

Also, it takes an hour to a day to have this issue start. if it's restarted two times in a row quickly, it works perfectly fine for some reason.

What I've tried:

  • setting "acpi=off" and "acpi=force" kernel parameters in grub
  • removing my nvidia gpu(i was using nouveau drivers)
  • changing distros

nothing worked. here are some things that both distros had in common with eachother:

  • systemd
  • cockpit
  • libvirt & qemu
  • docker

does anyone have advice? nothing i've seen online has worked. thank you for suggestions

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 9 points 1 year ago (5 children)

Monitor output after shutting down:

I've given it 6 hours or so to shut down, so it's almost 100% a hang not a slow shutdown

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 5 points 1 year ago (2 children)

    I had this issue: failed to finalise remaining DM devices. Which led me to here https://github.com/systemd/systemd/issues/15004 and Skinner927 mentions your issue in that thread

    I'd try uninstalling nouveau completely and see if the issue persists for you

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 3 points 1 year ago (2 children)

    The xserver-xorg-video-nouveau package was not installed, how else would I remove nouveau?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    I don't have an Nvidia GPU so I don't have any experience with it but a quick search brought me to Nvidias website and the instructions seem to line up with users answers on other forums.

    Disable it here https://docs.nvidia.com/ai-enterprise/deployment/vmware/latest/nouveau.html or apparently installing Nvidias proprietary drivers automatically blacklists Nouveau.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    that's only the X11 "driver" for it. nouveau is built into the kernel, the way to "uninstall" it is to make it not get loaded, by blacklisting it

    https://wiki.archlinux.org/title/Nouveau

    but this does not seem to be the problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago (1 child)

    seems its a nvidia issue, i also have that issue, the gpu locks and i need to reboot while the VM with the nvidia passthrough freezes. i need a full reboot from baremetal machine to stop gpu using all his power stuck, don't let it be for hours being on or you will kill your hardware

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 3 points 1 year ago (1 child)

    I have removed my gpu and the issue is still present.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    yes sorry I read you after writting it, if you remove the GPU the log message is the same but without the GPU lockup line?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Yeah that seems like a mainboard issue.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    I've run arch linux for a year or so before converting it, and no issues with shutdown. what makes you think that's the cause?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    Because you tried two different OSes and the point where it hangs is the point where the OS sends an APM/ACPI command to reboot / power off. This is the last thing the OS does. So if that's not happening something is wrong with the hardware, BIOS, or BIOS settings.

    You could try the syslog (journalctl), but logging is probably already off at that point.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 1 year ago (1 child)

    yeah journalctl logs show nothing relevant. I have disabled acpi and forced it(acpi=force), but that didn't fix this. There are a lot of different combinations of acpi settings I could try:

    acpi=force noapic
nolapic
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off

    But I found these from a guy which they didn't work on so I'm reluctant to try them.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    did you check it /proc/cmdline if the params were taken into account? perhaps you edited the config but didn't update the initramfs

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    And I guess if you're in front of the computer, you could just press the reset button or unplug it at that point (after it sucessfully synchronized the disks). no need to let it sit, there is no harm or data to be lost at that point.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    Says reboot, are you issuing a reboot or a shutdown poweroff? Entering sleep state 5 shout be power off right?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    I click the reboot button on cockpit, which issues a shutdown --reboot command as root. I agree that sleep state S5 is powered off. From the acpi docs:

    A computer state where the computer consumes a minimal amount of power. No user mode or system mode code is run. This state requires a large latency in order to return to the Working state. The system’s context will not be preserved by the hardware. The system must be restarted to return to the Working state. It is not safe to disassemble the machine in this state.

    This likely means my system is failing to reach that s5/g2 state.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    do you know that use device mapper? what kind of device is /dev/dm-1 ?

    "dmsetup info" might help

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    sudo dmsetup info returns:

    Name:              raven--vg-root
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 0
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Name:              raven--vg-swap_1
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        2
Event number:      0
Major, minor:      254, 1
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •