[SOLVED] Stuck into a single-user mode on Ubuntu 20.04 Kernel 5.4

[TKingu]

Hi guys.

I'm on Odroid xu4 with Ubuntu 20.04 and kernel 5.4.

I flashed the S.O. without any modification and I went into a single user mode by:

systemctl set-default rescue.target

At the reboot, inside the user-mode it gave me the Log:

systemd[1]: Failed to start LSB : executed by init(8) upon entering runlevel 1 (single)..

And then it stuck. The board seems like freezed. My keyboard doesn't work anymore, altought the cursor continue to blink like it waits for an input.

Anyone has the same problem? Many thanks.

[TKingu]

Did you flash ubuntu-20.04-5.4-mate-odroid-xu4-20210113.img.xz image with Etcher?
Already a few thousands users downloaded the image and there is no such report yet.
We also couldn't reproduce the issue.

BTW, do you use an eMMC? or microSD card?

[TKingu]

Hi,

many thanks for the reply.

Did you flash ubuntu-20.04-5.4-mate-odroid-xu4-20210113.img.xz image with Etcher?
Already a few thousands users downloaded the image and there is no such report yet.
We also couldn't reproduce the issue.

Yes, I flashed that OS. I didn't use Etcher, but dd, anyway I don't think that is the problem. I always used dd to flash the S.O images and I never had a problem. I tried also the multi-user mode and it works fine, the only problem is with the single-user mode.

BTW, do you use an eMMC? or microSD card?

I'm using an SD card.

[odroid]

I probably didn't understand what is the single-user mode and I think you are the first user who tried that.
I will check that with my colleague and get back to you early next week since it is Friday evening here.

[TKingu]

I probably didn't understand what is the single-user mode and I think you are the first user who tried that.

Maybe you know it with different names. The single user mode is the runlevel 1, also named rescue mode. The way to enter is by the command:

systemctl set-default rescue.target

And then reboot. This will reboot the system in single-user mode.

My apologies if I misspoke.

I will check that with my colleague and get back to you early next week since it is Friday evening here.

Thanks a lot mate, really appreciate it!

[TKingu]

You can try playing with boot.ini to select different console options.
If you have the UART Kit you may have the console there now.

setenv bootrootfs "console=tty1 console=ttySAC2,115200n8

You can remove console=ttySAC2..... since its for the uart kit and see if it helps.
If it doesn't change console=tty1 to console=tty0
It may help as well.

[TKingu]

Hi mdrjr,

Many thanks for your reply.
I followed your suggestion, it didn't work, but thank to that I have new information.

In the journal log i discovered these lines that could be really interesting

init : invalid option -- 't'
system-journald.service: Main process exited, code=killed, status=9/KILL
system-journald.service: Failed with result 'signal'

After that some stuff about network and nothing more.
The error that I posted before there is also inside this log, but after this there are some other stuff where things seems continue to work.
I'm not an expert, but seems that init program has a wrong parameter, could be?

[TKingu]

Took me a while but I figured it out.

You need to edit /etc/init.d/single

You'll see on do_start()
exec init -t1 S
change to
exec init S

Maybe someone at Ubuntu forgot to update it to match systemd. No idea.

[TKingu]

Took me a while but I figured it out.

You need to edit /etc/init.d/single

You'll see on do_start()
exec init -t1 S
change to
exec init S

Maybe someone at Ubuntu forgot to update it to match systemd. No idea.

It works!!! Thanks mate, you're my saviour!

[mdrjr]

You are welcome