Welcome to Friendica.Eskimo.Com

Home of Censorship Free Hosting

E-mail, Web Hosting, Linux Shell Accounts terminal or full remote desktops.

potentiallynotfelix via Linux

1 month ago

potentiallynotfelix
1 month ago

Linux server hangs on shutdown

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

in reply to potentiallynotfelix

catloaf

in reply to potentiallynotfelix 1 month ago

Hardware? Do they shut down properly if you do it from the console or ssh?

in reply to catloaf

potentiallynotfelix

in reply to catloaf 1 month ago

I will try to restart it using the reboot command.

The computer consists of:

i3-10100
16gb ddr4 ram
MSI h410m pro

in reply to potentiallynotfelix

catloaf

in reply to potentiallynotfelix 1 month ago

Interesting. BIOS update? Maybe check through all the settings, or do a factory reset on the BIOS? I have a similar board (H510 something) running proxmox and it works fine.

This entry was edited (1 month ago)

in reply to catloaf

potentiallynotfelix

in reply to catloaf 1 month ago

I would like to note that this may have been caused by a bios update, as it started sometime after it. i'll try another update now.

edit: already on the latest bios version.

This entry was edited (1 month ago)

in reply to potentiallynotfelix

Nanook

in reply to potentiallynotfelix 1 month ago

@potentiallynotfelix As a diagnostic, I would suggest trying shutting them down by ssh in and then using systemctl to shut them down, if that works then you know the issue is with cockpit. If it hangs even when systemd is asked to halt then I would consider reverting to the previous bios and see if the problem persists.

in reply to Nanook

potentiallynotfelix

in reply to Nanook 1 month ago

Ok. Cockpit uses the shutdown command to shut down[src], but systemctl poweroff might work. I will also attempt to revert bioses if msi supports it. thank you very much!

cockpit/pkg/lib/cockpit-components-shutdown.jsx at main · cockpit-project/cockpit

Cockpit is a web-based graphical interface for servers. - cockpit-project/cockpit

^GitHub

in reply to potentiallynotfelix

Nanook

in reply to potentiallynotfelix 1 month ago

@potentiallynotfelix Ok bet of luck. I've had all sorts of weird issues with systemd as of late, but not sure how many of those are inherent to systemd itself and how many are Ubuntu's config of same.

in reply to Nanook

potentiallynotfelix

in reply to Nanook 1 month ago

sudo systemctl reboot did the same. I'm starting to think this is bios related.

in reply to potentiallynotfelix

Nanook

in reply to potentiallynotfelix 1 month ago

@potentiallynotfelix Well flash to an older and see how it goes. I've seen some wired bios issues. I've got an i7=6850k machine on an Asus motherboard, and after I flashed to the latest bios, the USB power strobed on and off every few seconds so keyboard and mouse would work then not work then work then not work. I thought something was broken with hardware but then found others had the same issue with the most current BIOS, flashed to one release earlier and all good.

in reply to Nanook

potentiallynotfelix

in reply to Nanook 1 month ago

Flashing an older bios seemed to succeed! I gave it 14 hours or so before attempting a reboot, and if seemed to reboot without stalling. I'll give it a few more days now and try another, but that seemed to have fixed it.

in reply to potentiallynotfelix

Nanook

in reply to potentiallynotfelix 1 month ago

@potentiallynotfelix Ya gotta love it!

in reply to Nanook

potentiallynotfelix

in reply to Nanook 1 month ago

Thank you!

in reply to potentiallynotfelix

Nanook

in reply to potentiallynotfelix 1 month ago

@potentiallynotfelix You're most welcome!

Unknown parent

potentiallynotfelix

Unknown parent 1 month ago

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

in reply to potentiallynotfelix

AnEilifintChorcra

in reply to potentiallynotfelix 1 month ago

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

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

systemd-shutdown cannot finalize remaining DM devices, continuing · Issue #15004 · systemd/systemd

systemd version the issue has been seen with 244.3 Used distribution Arch Linux Expected behaviour you didn't see Computer shutdown on Reached Shutdown or Reached Reboot. Unexpected behaviour you s...

^GitHub

Unknown parent

AnEilifintChorcra

Unknown parent 1 month ago

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 docs.nvidia.com/ai-enterprise/… or apparently installing Nvidias proprietary drivers automatically blacklists Nouveau.