update failed

[gonczoll]

Since the last update on my rpi yesterday the pi doesn't boot anymore.
It's strange, because there are no announcements about any buggy updates.
Is there someone out there, who experienced something similar or is it a local failure, ie. SD is dead?
Thanks: László

[graysky]

Output?

[sheevaplugger]

I updated my ODROID HC2 today. It does not boot anymore, too.

I installed a fresh SD card. The same. Device is not reachable via network.

[sheevaplugger]

Maybe same issue there: viewtopic.php?f=65&t=16386 | OrangePI 3

[sheevaplugger]

System (odroid hc2) is running with another distro (fresh installed).

Last update (on archlinuxarm) is a week ago. I guess something broke during the week in the package repo.

[gonczoll]

@Graysky
What kind of output? As I already described it doesn't boot anymore.
No way to reach anything via ssh.
Probably the filesystem is totally broken.
I can try to read the sd with another computer, but what should I looking for?

[principia]

I updated my rpi3b today by ssh and it too seemed to have failed with no network access. I went to site and physically attached a monitor and keyboard and confirmed that the rpi was booting and operating correctly. However the ethernet network interface was down (ip link) although networkd was running without errors and the loopback interface was OK.

Using dmesg and grepping for etho gave a message that eth0 had been renamed to a predictable interface name hence the network configuration file that matched on "eth0" was never applied. So it looks like predictable naming is being belatedly applied to the rpi3b ethernet interface. This rpi3b was last updated in January 2023 so I suspect there has been a recent change in this area.

The archlinux network configuration wiki pages document the persistent name capability and how to manage it. I will mask the udev rule since for a remote headless embedded processor this will be easiest for me. Of course that has to be done from a physical connection because ssh is down!

[arch64]

Thanks to principia's message above I solved my issue. Ran into the same issue as the previous post. Had to mount the sd-card in another computer, install uboot-tools then add net.ifnames=0 to the "setenv bootargs" line in /boot/boot.txt. Then run the ./mkscr tool in /boot.

Turns out the issue is caused by the recent systemd update.

Once my Rpi worked I found multipe threads on this forum with the same issue:
https://archlinuxarm.org/forum/viewtopic.php?f=60&t=16350
https://archlinuxarm.org/forum/viewtopic.php?f=15&t=16245
https://archlinuxarm.org/forum/viewtopic.php?f=15&t=16382

[gonczoll]

Thank you for your help!
I also managed to solve the issue with your help and hints.
This is a really helpful forum with useful comments.
Here my solution: first I took the PI - an RPI3B - from the site which actually the electricity meter box and connected to a screen and keyboard. Then I grepped for 'eth0' the journalctl and found the message about renaming of eth0. For me it was a different name as mentioned in the post so it's strongly recommended to find it in the journal.
Then I created a new .network file in /etc/systemd/network with this name (new_name.network) and also edited the field 'NAME=new_name .
Reboot and now it works again.