Hi!
Michael Biebl bi...@debian.org writes:
Am 03.04.2015 um 23:00 schrieb Christoph Egger:
Christoph Egger christ...@christoph-egger.org writes:
Michael Biebl bi...@debian.org writes:
I assume the f2fs-tools package is installed?
What output (and return code) do you get, if you run
Am 03.04.2015 um 23:00 schrieb Christoph Egger:
Christoph Egger christ...@christoph-egger.org writes:
Michael Biebl bi...@debian.org writes:
I assume the f2fs-tools package is installed?
What output (and return code) do you get, if you run
fsck.f2fs
Michael Biebl bi...@debian.org writes:
I assume the f2fs-tools package is installed?
What output (and return code) do you get, if you run
fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53
from a rescue media?
# fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53
Christoph Egger christ...@christoph-egger.org writes:
Michael Biebl bi...@debian.org writes:
I assume the f2fs-tools package is installed?
What output (and return code) do you get, if you run
fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53
from a rescue media?
# fsck.f2fs
Am 01.04.2015 um 14:55 schrieb Christoph Egger:
Hi!
Michael Biebl bi...@debian.org writes:
Could you blacklist the ipmi_si driver, just to be sure?
Will do in the evening.
That aside, I wonder if it's related to the use of f2fs for /
[ 12.306905] systemd-fsck[171]: Executing:
Am 31.03.2015 um 17:45 schrieb Christoph Egger:
Package: systemd
Version: 215-14
Severity: important
Hi!
This system boots only in rescue mode (and sometimes with
break=premount mount rootfs +Ctrl-D) but never normally. I have a
full bootlog in debug mode attached.
Hi Christoph,
[
Am 31.03.2015 um 19:07 schrieb Michael Biebl:
Am 31.03.2015 um 17:45 schrieb Christoph Egger:
Package: systemd
Version: 215-14
Severity: important
Hi!
This system boots only in rescue mode (and sometimes with
break=premount mount rootfs +Ctrl-D) but never normally. I have a
full bootlog