Stuck after upgrading

[WarheadsSE]

At this point, either of those should have all necessary features of systemd 213, if this is the problem here.

[chemist69]

I can confirm the issue.
After updating on Sun, 8-Jun-2014, I was stuck with an unbootable system which only displayed "Welcome to Arch Linux ARM"

[WarheadsSE]

Instead of the NEXT person chiming in "me tooo!!!11", perhaps someone can manage to get a serial console OF THE ACTUAL MESSAGE OF FAILURE.

[sano2]

After applying the workaround Fruckiwacki posted here I was able to "successfully" boot kernel 3.12.xx, and noticed one specific failure: $this->bbcode_second_pass_code('', '[Failed] systemd(?): Loading kernel modules')
(I am typing this from memory as journalctl shows no entries between 2014-03-21 and now, so it might not be literal, but it was something along that line)

Before the workaround, the only thing I would see was the aforementioned "Welcome to Arch Linux ARM", with a cursor two or three lines below that stopped blinking after some seconds.
I did not try to get to another console, because
1) my crappy USB keyboard doesn't let me enter Ctrl-Alt-Fx (I should get a new one, I know)
2) I know enough about the boot process to realize there will be no TTY at this stage.

EDIT: Style; and I forgot to mention that ssh didn't work either.

[jonandermb]

Installing linux-raspberrypi-latest fixed it for me

[baseline]

I'm not sure what I've done differently to you guys but I've not had any luck with the workaround in this thread.

I backed up my boot partition from the sd card (/ is on an external usb hdd, sda1)
I downloaded the install image from this site
I copied the image to the sd card with dd
I mounted the sd card and edited cmdline to root=/dev/sda1

And when plugging the Pi back in I get kernel panic - unable to mount root fs on unknown block.

Unplugged Pi, mounted SD card, changed cmdline back to root=/dev/mmcblk0p2 and got same error.

I'm thoroughly confused, any tips?

[sdjf]

Take a look at the partition table on your hdd, remembering that boot and root are two different partitons. You could do an ls, parted, gparted or parted on the hdd to see where the boot and root partitions went. that assumes your main box is Linux, if it is another OS, I don't know.

EDIT: with parted and similar tools, you will be examining the device rather than specific partitions. Example would be:

parted /dev/sda
And issue command "p".
If that is not helpful, you can also check the following, but if dd was done properly, the above should yield better results, as the following will only tell you contents of partition 1 and not partition 2:

parted /dev/sda1

Chances are your root partition is in /dev/sda2 rather than /dev/sda1 if you dd'd everything to the hdd