1

I have freshly installed Ubuntu Server 16.04.3. I had previously been using some edition of version 14, and it always booted to a text login screen. I was expecting the same from 16.04.3, and in on-line demos that's exactly what I see happening.

It essentially gets to a black screen with no login prompt and only the following text at top:

/dev/md0: clean, 60884/117891072 files, 759991/471562752 blocks

I do have (software) RAID10 configured. This is my first time configuring anything other than RAID0.

I noticed that I am able to ssh into the machine remotely and use it that way. I also discovered that by typing Ctrl-Alt-1 I can get to a (colourful) terminal and login that way. I've seen some other people ask about boot/log-in issues, but most seem to involve boot loops or completely blank screens. This doesn't seem to be what I'm experiencing.

So my problem doesn't seem to indicate the server isn't booted correctly. It just doesn't present the login screen to the local terminal automatically after booting. Is this expected?

Additional information:

Relevant contents of /var/log/auth.log

systemd-logind[825]: New seat seat0.
systemd-logind[825]: Watching system buttons on /dev/input/event1 (Power Button)
systemd-logind[825]: Watching system buttons on /dev/input/event0 (Power Button)
sshd[968]: Server listening on 0.0.0.0 port 22.
sshd[968]: Server listening on :: port 22.
CRON[1290]: pam_unix(cron:session): session opened for user root by (uid=0)
CRON[1290]: pam_unix(cron:session): session closed for user root
7
  • You installed a server it doesn't come with a GUI, if you need it you have install that! Sep 28, 2017 at 19:55
  • 1
    I'm not expecting a GUI, nor do I want one. I'm expecting a CLI login prompt, much like you'd get with SSH. Basically I was anticipating the same default behaviour as with Ubuntu 14.04 server.
    – LancerDL
    Sep 28, 2017 at 20:11
  • Inspect /var/log/auth.log if there's an auth issue.
    – Redbob
    Sep 28, 2017 at 21:58
  • I didn't see an issue there, or at least none that I recognize. Seems like it was just waiting for events. >>systemd-logind[825]: New seat seat0. >>systemd-logind[825]: Watching system buttons on /dev/input/event1 (Power Button) >>systemd-logind[825]: Watching system buttons on /dev/input/event0 (Power Button) >>sshd[968]: Server listening on 0.0.0.0 port 22. >>sshd[968]: Server listening on :: port 22. >>CRON[1290]: pam_unix(cron:session): session opened for user root by (uid=0) >>CRON[1290]: pam_unix(cron:session): session closed for user root
    – LancerDL
    Sep 29, 2017 at 2:02
  • 2
    Make sure TTY isn't screwing you. Press CTRL + ALT + F1 and you might see the login prompt. Read more here: askubuntu.com/questions/761031/… Dec 29, 2017 at 1:05

0

Browse other questions tagged or ask your own question.