You are not logged in.

#1 2015-12-05 13:57:50

mabra
Member
From: Brühl
Registered: 2015-10-05
Posts: 22

System reboot fails, because shutdown hungs

Hello !

Something, looks like ZFS,  prevents my system to reboot, because
the shutdown hungs. The last messages on the console are this:

Reached target Shutdown.
systemd-journald: Failed to send WATCHDOG=1 notification message: Connection refused
systemd-journald: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
systemd-journald: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

This looks never ending.

After boot, the journal has only this:

systemd[1]: Mounting Arbitrary Executable File Formats File System...
systemd-journald[2931]: File /var/log/journal/37a5917f80134d5e903eff8fb40ef3a6/system.journal corrupted or uncleanly shut down, renaming and replacing.

The situation starts with dd'ing zeros into a ZVOL device, which cannot properly stopped.
According to a later message on the console, one can disable the message.
But wil this finally boot then ?

I am helpless, never seen somethings like this before.
Would luckier, if someone can give me a tip. Although,
there is mentioned a watchdog, I have no clue about.
Its visible in journal after systemstart, where it is mentioned
being disabled in BIOS. Indeed, in the BIOS is "something
like this" [and disable by me ;-) ]. Will this help ?

Thanks anyway,
Manfred

Offline

#2 2015-12-07 04:41:14

boban_dj
Member
Registered: 2015-03-17
Posts: 150

Re: System reboot fails, because shutdown hungs

Hi Manfred,
'Transport endpoint is not connected' has to do with some filesystem not unmounting properly. Find the service that is trying to unmount, restart or disable this and try again.

Offline

#3 2015-12-07 04:59:58

mabra
Member
From: Brühl
Registered: 2015-10-05
Posts: 22

Re: System reboot fails, because shutdown hungs

Hi!

Thanks, first.
Have you seen the 'connection refused' message before ? Unlikely, that this will be from filesystems,
this is typical socket message. Additionally, this happened, after all filesystems were explicitely
unmounted by the shutdown, so accessing a filesystem, after it was unmounted looks like some
other strangeness.

Regards,
Manfred

boban_dj wrote:

Hi Manfred,
'Transport endpoint is not connected' has to do with some filesystem not unmounting properly. Find the service that is trying to unmount, restart or disable this and try again.

Offline

#4 2017-06-25 07:18:25

miles969
Member
Registered: 2013-02-03
Posts: 23

Re: System reboot fails, because shutdown hungs

hi,

have you had any luck fixing this?

ive been having the same, particularly nasty shutdown/reboot issue. im using btrfs instead of zfs, but i assume the cause may be a similar one. after the shutdown target has been reached, i get these messages (including the preceding "connection refused") ad infinitum. cold shutdown/reboot is required.
i tried btrfs balance and btrfs scrub on the root filesystem, but no luck.
i tried this change to coredump.conf, also to no avail.
ive disabled all network mounts in fstab, still no dice.
i will try disabling conky (possibly related, as stated in other threads with this issue) and report back.

regards,
m

Offline

#5 2017-06-25 14:10:22

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: System reboot fails, because shutdown hungs

Please note that it has been 2 years since the OP was to the boards, and while the symptom might look similar, the cause could be completely different. You should open a new thread and provide your own excerpts from the log/journal.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Offline

Board footer

Powered by FluxBB