Your message dated Sun, 28 Jul 2013 22:29:48 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-systemd-maintainers] Bug#717892: systemd 204: Boot
rescue (single) mode hangs
has caused the Debian Bug report #717892,
regarding systemd 204: Boot rescue (single) mode hangs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
717892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717892
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-2
Severity: normal
After upgrading systemd from v.44 to v.204, attempting to boot systemd in
rescue (single) mode results in boot hanging at
systemd-fsck:/dev/sda5: clean, 143925/13746176 files,8735537/54956341.
System blocks with no further output or disk activity.The system still
appears to be running and ctrl-alt-delete triggers a clean reboot.
/dev/sda5 and sda6 seem to block booting in rescue mode only, not in
multi-user mode.
My fstab file:
---
/dev/sda1 / ext4 errors=remount-ro 0 1
/dev/sda5 /home ext4 defaults 0 1
/dev/sda6 swap swap defaults 0 0
tmpfs /var/log tmpfs defaults,noexec,noatime,mode=0755 0 0
---
I found a work around to make systemd booting in rescue mode by adding
'defaults,comment=systemd.automount' to /dev/sda5 and removing the swap
disk from fstab.
To get the swap disk working I added /sbin/swapon /dev/sda6 to rc.local.
There was no such issue with version 44!
-- System Information:
Debian Release: Jessie/Sid
Architecture: amd64 (x86_64)
Kernel: Linux debian 3.10-1-amd64 #1 SMP Debian 3.10.1-1 (2013-07-16)
--- End Message ---
--- Begin Message ---
Hi Jos,
Jos van Wolput <[email protected]> writes:
> Issue fixed by reinstalling all systemd and udev packages in new
> /lib/sysemd and /lib/udev directories.
> The previous upgrade had been done on the existing 44 version.
> This bug can be closed.
I am not entirely sure what happened here, but it sounds like you did
not upgrade all the packages properly when you experienced the hanging
boot.
In case this happens again, the list of installed packages and their
versions (which reportbug automatically creates and appends to the
bugreport normally) would be helpful :).
Closing as requested now.
--
Best regards,
Michael
--- End Message ---
