On Fri, Jul 18, 2014 at 06:18:28PM +0200, Bas Wijnen wrote:
When booting into single user mode, things worked as expected. I was
unable to remount the fs read-only; the logs you requested are attached.
(The mei_me messages have always been there, also with sysv init; I
don't think they are
On Sat, Jul 19, 2014 at 10:27:48PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Jul 18, 2014 at 06:18:28PM +0200, Bas Wijnen wrote:
When booting into single user mode, things worked as expected. I was
unable to remount the fs read-only; the logs you requested are attached.
(The mei_me
Am 13.07.2014 22:17, schrieb Bas Wijnen:
On Sat, Jul 12, 2014 at 12:59:04AM +0200, Michael Biebl wrote:
Am 12.07.2014 00:34, schrieb Bas Wijnen:
When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /
Now, and I'm guessing this is a change on the part of systemd,
Am 14.07.2014 15:10, schrieb Michael Biebl:
I'd be fine with stopping all services, but I'm not familiar with how to
do that either. If this is the solution, please add that instruction to
the message. But would services which prevent the disk from being
remounted read-only be started before
Am 14.07.2014 16:00, schrieb Michael Biebl:
emergency.target only has Requires/After=emergency.service, so I'd
expect fewer services to be running then in rescue.target since isolate
should stop all other services.
Apparently the documentation doesn't match the code:
mbiebl_ hm, so the
On Sat, Jul 12, 2014 at 12:59:04AM +0200, Michael Biebl wrote:
Am 12.07.2014 00:34, schrieb Bas Wijnen:
When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /
Now, and I'm guessing this is a change on the part of systemd, that
first command (remount
On Thu, Jul 10, 2014 at 06:40:47PM +0200, Michael Biebl wrote:
Am 10.07.2014 05:03, schrieb Bas Wijnen:
My suggested solution is to document the method for remounting the root
filesystem read-only (or the method for getting help on the commands that do
such things) in the error message
Am 12.07.2014 00:34, schrieb Bas Wijnen:
When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /
Now, and I'm guessing this is a change on the part of systemd, that
first command (remount read-only) fails with the message that the file
system is busy. Having no
Am 10.07.2014 05:03, schrieb Bas Wijnen:
My suggested solution is to document the method for remounting the root
filesystem read-only (or the method for getting help on the commands that do
such things) in the error message that says fsck must be run manually, or
perhaps whenever a shell is
Package: systemd-sysv
Version: 204-14
Severity: critical
Justification: impossible to boot system
(The severity seems inflated, but it didn't fit any of the lower RC levels and
it should be RC IMO. It is also pretty easy to fix, I hope, so I'd suggest
doing that instead of worrying about the
10 matches
Mail list logo
