Couldn't ssh in after update

[technosf]

Interestingly, couldn't get the serial port to accept input - got the root console output, but its just hanging. Getty? Going to have to go the chroot route.

[technosf]

May have found the issue. Looks like some dep issues after an upgrade - from the startup console:
$this->bbcode_second_pass_code('', '
Welcome to Arch Linux ARM!
[ 15.823108] systemd[1]: Set hostname to <scout.brewup.com>.
[ 15.954036] systemd[1]: Cannot add dependency systemd-journald.service to sysinit.target, ignoring: File exists
[ 16.013980] systemd[1]: Cannot add dependency systemd-journald.socket to sockets.target, ignoring: File exists
[ 16.024206] systemd[1]: Cannot add dependency systemd-journald-dev-log.socket to sockets.target, ignoring: File exists
[ 16.035063] systemd[1]: Cannot add dependency systemd-udevd-control.socket to sockets.target, ignoring: File exists
[ 16.045636] systemd[1]: Cannot add dependency systemd-udevd-kernel.socket to sockets.target, ignoring: File exists
[ 16.056116] systemd[1]: Cannot add dependency systemd-journald-audit.socket to sockets.target, ignoring: File exists
[ 16.090561] systemd[1]: Cannot add dependency remote-fs.target.bak to multi-user.target, ignoring: Invalid argument
[ 16.102065] systemd[1]: Cannot add dependency systemd-user-sessions.service to multi-user.target, ignoring: File exists
[ 16.113418] systemd[1]: Cannot add dependency dbus.service to multi-user.target, ignoring: File exists
[ 16.129759] systemd[1]: Cannot add dependency org.freedesktop.login1.busname to busnames.target, ignoring: File exists
[ 16.183504] systemd[1]: display-manager.service: Cannot add dependency job, ignoring: Unit display-manager.service failed to load: No such file or directory.
')

Some indication here: https://bbs.archlinux.org/viewtopic.php?id=175892

I guess it's time (after I back up my configs) to reimage the disk and put those configs into an scm, an also tryout the mainline uboot.

[Kabbone]

$this->bbcode_second_pass_quote('technosf', 'M')ay have found the issue. Looks like some dep issues after an upgrade - from the startup console:
$this->bbcode_second_pass_code('', '
Welcome to Arch Linux ARM!
[ 15.823108] systemd[1]: Set hostname to <scout.brewup.com>.
[ 15.954036] systemd[1]: Cannot add dependency systemd-journald.service to sysinit.target, ignoring: File exists
[ 16.013980] systemd[1]: Cannot add dependency systemd-journald.socket to sockets.target, ignoring: File exists
[ 16.024206] systemd[1]: Cannot add dependency systemd-journald-dev-log.socket to sockets.target, ignoring: File exists
[ 16.035063] systemd[1]: Cannot add dependency systemd-udevd-control.socket to sockets.target, ignoring: File exists
[ 16.045636] systemd[1]: Cannot add dependency systemd-udevd-kernel.socket to sockets.target, ignoring: File exists
[ 16.056116] systemd[1]: Cannot add dependency systemd-journald-audit.socket to sockets.target, ignoring: File exists
[ 16.090561] systemd[1]: Cannot add dependency remote-fs.target.bak to multi-user.target, ignoring: Invalid argument
[ 16.102065] systemd[1]: Cannot add dependency systemd-user-sessions.service to multi-user.target, ignoring: File exists
[ 16.113418] systemd[1]: Cannot add dependency dbus.service to multi-user.target, ignoring: File exists
[ 16.129759] systemd[1]: Cannot add dependency org.freedesktop.login1.busname to busnames.target, ignoring: File exists
[ 16.183504] systemd[1]: display-manager.service: Cannot add dependency job, ignoring: Unit display-manager.service failed to load: No such file or directory.
')

[sdelgran]

Confirmed here too even after a fresh install on Goflex Net. Basic system with no other package installed yet. Everything is fine (tried several reboot) until I perform a full system upgrade. Like you, I boiled it down to systemd upgrading to 227. I receive the same dependency error messages.

In my case:
- No ipv4 assigned to eth0.
- Can login (serial console) as root only. Upon login I receive the message "System is booting up. See pam_nologin(8)" 3 times.
- Can login with user after I start systemd-user-sessions.service (which indeed shows as stopped).
- systemctl --failed --all returns 0 loaded units listed.

[mwNas]

Came across this:

http://unix.stackexchange.com/questions ... ile-exists

It means the systemd service files for all of listed tools/packages are missing. You need to find toolname.dervice file and place it into /lib/systemd/system.

In poor words, your systemd service commands are not going to work for the tools that the systems warns during the boot. I suggest you to backup your data and perform a clean install since upgrade messed up.

[Kabbone]

$this->bbcode_second_pass_quote('mwNas', 'C')ame across this:

http://unix.stackexchange.com/questions ... ile-exists

It means the systemd service files for all of listed tools/packages are missing. You need to find toolname.dervice file and place it into /lib/systemd/system.

In poor words, your systemd service commands are not going to work for the tools that the systems warns during the boot. I suggest you to backup your data and perform a clean install since upgrade messed up.

[moonman]

3 kirkwoods devices here. No problem at on the 2. I can't touch the 3rd as it is in use by BFQ developers.
Will test with a clean install

[RubenSilveira]

I can confirm the same behaviour (dependency issue) on my kirkwood installation.

Downgrading systemd, systemd-sysvcompat and libsystemd to 226-3.1 solved it.

Procedure was executed on a qemu'ed chroot, as in my particular setup (QNAP TS-212) rootfs lies on an USB stick.

[moonman]

Yeah fresh install causes the problem. I haven't reinstalled in years. Could be as simple as a config file.

[Djabx]

Hi everyone,

I'm a beginner on alarm on my Pi.

I've install this image:
http://downloads.raspberrypi.org/arch/i ... 22.img.zip

Everything works well until I dit: $this->bbcode_second_pass_code('', 'pacman -Syu')
Now I can't login anymore.

I presume I will have to plugin a screen and a keyboard to get trough this.