Your message dated Wed, 19 Jun 2019 22:03:17 +0200
with message-id <[email protected]>
and subject line Re: /cgroup entry in /etc/fstab obstructs boot in upgrade to
"stretch"
has caused the Debian Bug report #930199,
regarding /cgroup entry in /etc/fstab obstructs boot in upgrade to "stretch"
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.)
--
930199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930199
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cgroupsfs-mount
Version: 1.3
Upon installing "stretch" over a "jessie" system and rebooting, the boot
halts with the message:
----------------------------------------
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
----------------------------------------
then something like "Enter to continue". But hitting "Enter" just redisplays
the message.
With some hints from the travails of the Raspbian crowd, I found that the
message emanates from /lib/systemd/system/emergency.service, and the latter
part can be worked around temporarily by adding "--force" to "sulogin". That
permits me to log in, where journalctl shows errors (that I didn't write
down) related to "cgroup".
Raspbian users also were foiled by invalid entries in /etc/fstab. I found
this old entry:
----------------------------------------
none /cgroup group defaults 0 0
----------------------------------------
Commenting that out allowed the boot to complete.
I notice now some /var/log/syslog entries like:
----------------------------------------
systemd[1]: Cannot create mount unit for API file system /cgroup. Refusing.
----------------------------------------
which started before the failed reboot, and after I started installing
"stretch".
This system was originally loaded with "squeeze" or earlier. That line was
a leftover from long ago; /etc/fstab's mtime was Dec. 2010. I know it's
fashionable these days to blow away systems completely rather than upgrade.
:shrug:
I'm guessing here at the appropriate package/version; I imagine that the
package that installed this entry no longer exists.
--- End Message ---
--- Begin Message ---
Hi
On Sat, 8 Jun 2019 01:13:22 +0000 Mike <[email protected]> wrote:
> Package: cgroupsfs-mount
> Version: 1.3
>
> Upon installing "stretch" over a "jessie" system and rebooting, the boot
> halts with the message:
> ----------------------------------------
> You are in emergency mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
> try again to boot into default mode.
>
> Cannot open access to console, the root account is locked.
> See sulogin(8) man page for more details.
> ----------------------------------------
> then something like "Enter to continue". But hitting "Enter" just redisplays
> the message.
>
> With some hints from the travails of the Raspbian crowd, I found that the
> message emanates from /lib/systemd/system/emergency.service, and the latter
> part can be worked around temporarily by adding "--force" to "sulogin". That
> permits me to log in, where journalctl shows errors (that I didn't write
> down) related to "cgroup".
>
> Raspbian users also were foiled by invalid entries in /etc/fstab. I found
> this old entry:
> ----------------------------------------
> none /cgroup group defaults 0 0
> ----------------------------------------
> Commenting that out allowed the boot to complete.
>
> I notice now some /var/log/syslog entries like:
> ----------------------------------------
> systemd[1]: Cannot create mount unit for API file system /cgroup. Refusing.
> ----------------------------------------
> which started before the failed reboot, and after I started installing
> "stretch".
>
> This system was originally loaded with "squeeze" or earlier. That line was
> a leftover from long ago; /etc/fstab's mtime was Dec. 2010. I know it's
> fashionable these days to blow away systems completely rather than upgrade.
> :shrug:
>
>
> I'm guessing here at the appropriate package/version; I imagine that the
> package that installed this entry no longer exists.
The cgroup file system is supposed to be mounted at /sys/fs/cgroup.
If you have an entry in /etc/fstab which mounts it at /cgroup, the fstab
entry needs to be removed.
Doing that automatically in the maintainer scripts is ugly and given
that this is the first bug report in that regard after stretch has been
released 2 years ago, I don't think it's worth the effort.
systemd dropping you into the emergency shell is not nice, but the only
sensible thing to do at this point. As this gives you a chance to fixup
/etc/fstab and continue without risking to get an inconsistent system
state by mounting the cgroupfs over at /cgroup.
Hope that makes sense.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
