1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • boot fails very early with a systemd-service message about failing to l

    From [email protected]@21:1/5 to All on Sat Feb 1 17:50:01 2025
    I get the message right after the boot sequence declares the / drive
    clean. The subject message repeats 3 times then the system boot stops.
    It still responds to the keyboard but there is no system to log into.

    When I go into the system in a chroot after booting with systemrescue, I
    find that journalctl simply reports the systemrescue messages. Do I have
    to do something special to get the chroot system's messages?

    Maybe I need another cup of coffee to jumpstart my brain, but I'm at a
    bit of a loss as to how to get my system back up. :(

    Any advice?

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gary Dale@21:1/5 to [email protected] on Sat Feb 1 18:40:01 2025
    On 2025-02-01 11:29, [email protected] wrote:
    I get the message right after the boot sequence declares the / drive
    clean. The subject message repeats 3 times then the system boot stops.
    It still responds to the keyboard but there is no system to log into.

    When I go into the system in a chroot after booting with systemrescue,
    I find that journalctl simply reports the systemrescue messages. Do I
    have to do something special to get the chroot system's messages?

    Maybe I need another cup of coffee to jumpstart my brain, but I'm at a
    bit of a loss as to how to get my system back up.  :(

    Any advice?

    Thanks.


    Never mind. The system eventually came up - after some 20 minutes. It
    currently seem to be running OK.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew M.A. Cater@21:1/5 to [email protected] on Sat Feb 1 19:00:01 2025
    On Sat, Feb 01, 2025 at 10:07:49AM -0700, [email protected] wrote:
    On 2025-02-01 09:29, [email protected] wrote:

    BTW: the same happens with the previous kernel. Also, this is a
    Debian/Buster server running on AMD64 hardware. I've fsck'd the partition
    and it's fine.

    I rebooted today after installing the latest updates - which included a new linux-image.


    Do you mean Buster ie Debian 10 ?

    When you say systemrescue - do you mean a systemrescue live image that is
    not from Debian for example the one from https://www.system-rescue.org/ ?

    I'd suggest maybe using a Debian netinst image in rescue mode and
    chroot-ing into the target partition, perhaps or using a Debian live
    image to access the filesystem.

    All the very best, as ever,

    Andrew Cater
    ([email protected])

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From [email protected]@21:1/5 to [email protected] on Sat Feb 1 18:30:02 2025
    On 2025-02-01 09:29, [email protected] wrote:
    I get the message right after the boot sequence declares the / drive
    clean. The subject message repeats 3 times then the system boot stops.
    It still responds to the keyboard but there is no system to log into.

    When I go into the system in a chroot after booting with systemrescue,
    I find that journalctl simply reports the systemrescue messages. Do I
    have to do something special to get the chroot system's messages?

    Maybe I need another cup of coffee to jumpstart my brain, but I'm at a
    bit of a loss as to how to get my system back up. :(

    Any advice?

    Thanks.

    BTW: the same happens with the previous kernel. Also, this is a
    Debian/Buster server running on AMD64 hardware. I've fsck'd the
    partition and it's fine.

    I rebooted today after installing the latest updates - which included a
    new linux-image.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gary Dale@21:1/5 to Andrew M.A. Cater on Sat Feb 1 20:40:02 2025
    On 2025-02-01 12:39, Andrew M.A. Cater wrote:
    On Sat, Feb 01, 2025 at 10:07:49AM -0700, [email protected] wrote:
    On 2025-02-01 09:29, [email protected] wrote:

    BTW: the same happens with the previous kernel. Also, this is a
    Debian/Buster server running on AMD64 hardware. I've fsck'd the partition
    and it's fine.

    I rebooted today after installing the latest updates - which included a new >> linux-image.

    Do you mean Buster ie Debian 10 ?

    When you say systemrescue - do you mean a systemrescue live image that is
    not from Debian for example the one from https://www.system-rescue.org/ ?

    I'd suggest maybe using a Debian netinst image in rescue mode and
    chroot-ing into the target partition, perhaps or using a Debian live
    image to access the filesystem.

    All the very best, as ever,

    Andrew Cater
    ([email protected])

    Sorry - I meant Debian/Bookworm (Debian 12). My mental faculties are
    going downhill rapidly.  ;)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)