[Chromebook XE303C12] Systemd doesn't boot after upgrade

[PariahVi]

I managed to get a USB drive to work after tinkering a lot with it and eventually having to call programs from their address on the USB drive . All in all, I got the install USB stick to work long enough for me to arch-chroot into mmcblk0p3, wget the archived systemd-212-* tar.gz file and downgrade systemd Now everything works and the chromebook isn't a paperweight. Teaches me to upgrade my init system without making sure it works for others first. Time to mark systemd as "Do not upgrade" in pacman .

[WarheadsSE]

Checking the news/site might have helped. Unfortunately, this is due to the kernel tree in use, not systemd.

[cianof]

Rolled back by following the instructions provided in this thread. Many thanks.

What's the best way to find out when it is safe to upgrade again?

[vacant]

I've configured pacman to ignore systemd so every time I update I get a warning about my version and the current version of systemd being ignored. When I see a later version than 213-5 being offered in the "ignore" message, I'll upgrade. Maybe before if the kernel updates?

It's always "safe" to upgrade. Arch is rolling release, quite cutting edge. So I do keep backups and I do keep a bootable usb stick and I do know how to implement both

[obywatel3vity]

Hi

Please let me know when systemd or kernel in repo will be valid against:

$this->bbcode_second_pass_quote('', '[')code]Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory[/code]

[WarheadsSE]

Holy Crap old kernel.

[obywatel3vity]

Holy is my patience ;D

Any clues? I'm a little afraid to:

$this->bbcode_second_pass_code('', 'pacman -Suy')

cause if I still meet error on boot i'm sentenced to diassemble my stuff (lot's of wires) and carry it to plug HDMI
and backup usb hdd with fsarchiver.

How long should I?:
$this->bbcode_second_pass_code('', 'pacman -Suy --ignore systemd libsystemd')

We are w8ing for new kernel...

[WarheadsSE]

systemd was fixed ... (we disabled the xattrs) Stop ignoring it.

Also, the Pi kernel doesn't HAVE this problem. So this isn't even our issue. Where the hell is that kernel from?

[doragasu1]

Thanks @WarheadsSE!

[psychoacoustic]

Hi @WarheadsSE, thanks for fixing it! Since I don't have a secondary Arch boot on hand, is there a way I can disable xattrs by manually editing a file (mounting my arch SD card on an Ubuntu desktop)? (followed by a pacman -Suy of course to bring it back to "stock" of course)

Cheers!