16 Mar
2018
16 Mar
'18
3:57 p.m.
Hi Thierry, Thank you for your reply.
On Friday 16 March 2018 15:22:28 Thierry de Coulon wrote:
On Friday 16 March 2018 15.13:31 Baron wrote:
Yes systemd is on this machine. I haven't made any changes to either
of the HDD on this machine. To be honest I wouldn't know what the
UUID's were originally, if they had changed.
The thing that bothers me most is that when this occurs, the only way
I can get back to a working system is to go through the root log in
process. It is as if the machine records that the start job has not
finished, preventing me from bypassing it.
Question: Where could I find how this process is triggered ?
Thanks:
Re Previous post: I'm going to have to get another backup device.
58Gb is too much for DVD's.
--
Best Regards:
Baron
Hi Guys,
(...)
Problem: On boot up, maybe every second or third
time, I get a
black screen with "[*** ] Start job running - ~0.XX seconds.
1:30."
This has, I'm pretty sure, to do with systemd. I got that several
time and yes, when you don't know about it it's quite difficult to
solve.
Most often it has to do with some partition having changed UUID.
Did you modify your partition layout, or simply reformat one?
I've seen such messages linked to nfs shares too.
Anyway, the first thing is to identify what the job is running for,
then we should be able to debug.
Thierry