Hi,
Sorry for my delay. I couldn't see the screenshot (I'm blind), so I
waited for the update so test actually. Indeed the boot messages seem
more relevant and give more info. I will test tonight to simulate the
problem I experienced to see if logs are more helpful. But right, boot
display changes are helpful.
I let you informed about my test tonight.
Regards,
Le 17/11/2014 14:24, intrigeri a écrit :
Hi Jean-Philippe,
Michael Biebl wrote (28 Sep 2014 08:37:49 GMT) :
If /dev/sdc2 is not vital to boot your system, you should mark it as
"nofail" in /etc/fstab.
That will be addressed via #756903 and friends, so let's focus on the
other parts of this bug report.
Am 28.09.2014 um 03:31 schrieb Jean-Philippe MENGUAL:
2. The bug itself: I was unable to understand why my system falled in emergency.
Nothing in the journal, or at least nothing which is relevant. Unable to detect
the origin of the problem, except my imagination.
v215 will automatically switch to verbose mode when it a unit triggers a
timeout or fails to start.
See the attached screenshot.
In timeout1.png, systemd is waiting for the device to show up.
In timeout2.png you see that it reached the timeout and then drops you
into emergency shell (timeout3.png).
Does that address your issues?
Ping?
Cheers,
--
intrigeri
--
Jean-Philippe MENGUAL
accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels
Mail: te...@accelibreinfo.eu
Site Web: http://www.accelibreinfo.eu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
