Greetings,

I know this may sound odd, but I would start by setting the grub environment to boot this instance into single user mode if you can.

Be aware that "systemd" is new and quite controversial, and in many ways is likely buggy. So the approach I would take once I was on the system as single user or with the quiesced boot drive NFS mounted to another system (This might be problematic in itself :^), I would figure out how to stop "udevd" from starting up. I would try looking for "udevd" depending on the tools at hand and available. Good possibilities include:

/sbin/udevd
/lib/systemd/systemd-udevd

That said, your mileage may vary.

Good luck and...

Kindest Regards,

Paul Flint

On Wed, 16 May 2018, Neale Ferguson wrote:

Date: Wed, 16 May 2018 16:30:32 +0000
From: Neale Ferguson <[email protected]>
Reply-To: Linux on 390 Port <[email protected]>
To: [email protected]
Subject: Re: Getting verbose output during boot

So the log is filling with:

systemd-udevd[468]: unable to receive ctrl connection: Function not implemented

On 5/16/18, 12:23, "Neale Ferguson" <[email protected]> wrote:

   Thanks Mark. Using debug=1 I see a number of these messages appearing every 
30-60 seconds or so:

   [   57.090377] systemd-journald[65]: 
/run/log/journal/43be8124b31c43fe9edc24238dc923cb/system.journal: Allocation 
limit reached,
   rotating.
   [   57.090394] systemd-journald[65]: Rotating...
   [   57.093786] systemd-journald[65]: Reserving 182663 entries in hash table.
   [   57.158239] systemd-journald[65]: Vacuuming...
   [   57.158320] systemd-journald[65]: Vacuuming done, freed 0B of archived 
journals on disk.
   [   57.158334] systemd-journald[65]: Retrying write.

   It seems like systemd is writing a heap of messages an wrapping. It'd be 
nice to see what gumpf is being logged. However, when the boot eventually fails 
we never drop into a shell and just get thousands of these messages:

   systemd[1]: Failed to accept private connection, ignoring: Function not 
implemented

   I guess if I can work out what messages are being logged then I'll find the 
underlying problem



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Kindest Regards,



☮ Paul Flint
(802) 479-2360 Home
(802) 595-9365 Cell

/************************************
Based upon email reliability concerns,
please send an acknowledgement in response to this note.

Paul Flint
17 Averill Street
Barre, VT
05641

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to