| Author |
Message |
kenyee
|
|
Post subject:
 Posted: 05.09.2014, 23:05
|
|
Joined: 2010-09-29
Posts: 100
Status: Offline
|
|
Sorry...that was a great description from me 
Did a d-u yesterday and haven't done one for a month. Mysql.servivice and rsyslog.service both fail initscript during the d-u keeps putting me in the emergency console.
It's weird that the emergency console kicks in during the d-u.
I had to reboot because a lot of devices were shut down by the d-u and I'm back to d-u emergency console hell.
Will probably try installing mysql next. |
|
|
| |
|
|
|
 |
|
kenyee
|
|
|
Post subject:
Posted: 06.09.2014, 01:30
|
|
Joined: 2010-09-29
Posts: 100
Status: Offline
|
|
| Recovered by uninstalling any package it complained about |
|
|
| |
|
|
|
|
|
kenyee
|
|
|
Post subject:
Posted: 06.09.2014, 16:16
|
|
Joined: 2010-09-29
Posts: 100
Status: Offline
|
|
So for anyone else that runs into this, if any service fails to start during a d-u, it will start an emergency console that is half tied into the command line. Your root password won't work because the command line eats the first character. Hit ctrl-d until it says you are logged out, then log into the real emergency console. Then you can apt remove any services that cause this to happen.
Yes, I think this is a bug in the systemd start stuff... the emergency console should be disabled during the d-u IMHO.
I think I had to remove and reinstall mysql, acpid, nginx, postgresql, sand, mythtv. And nut also had to be reinstalled.
Also, do "mount -fav" to make sure everything in your fstab mounts cleanly so you don't get stuck in the emergency console on the next boot... |
|
|
| |
|
|
|
|
|
|
|
|
