[SOLVED] pacman -Suy broke with "is not an ELF file

LittleSandra · 2024-01-15 11:15:33

Dear all

I just did

sudo pacman -Suy
yay -Suy
reboot

and then the OS wouldn't boot because I seg. faulted. I fixed this by rebuilding initfs.

Now all the packages that got updated gives this error

... is not an ELF file - it has the wrong magic bytes at the start

I can start Wayland and xterm, but that is about it. Pretty much everything else gives the above error.

Trying to update again, doesn't give any new packages.

Does anyone know what to do?

Hugs,
Sandra

Last edited by LittleSandra (2024-01-15 22:32:21)

V1del · 2024-01-15 13:08:16

Does pacman itself still work?

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

Post the output of that.

Last edited by V1del (2024-01-15 13:08:45)

LittleSandra · 2024-01-15 13:34:00

Yes, luckily pacman still works. Here is the output. It is ~1000 lines.

https://pastebin.com/F1NyQpW5

seth · 2024-01-15 14:27:23

There're certainly issues w/ avahi, lib32-mesa, bluez-libs, python-pydantic-core and qt5-base - further go, podman, rclone, shadow and visual-studio-code-bin
So you'll have to re-install those and also post your pacman.log

cat /var/log/pacman.log | curl -F 'file=@-' 0x0.st

And of course your "Suy" heresy got you into trouble, use "Syu" as the Great Taco intended.

LittleSandra · 2024-01-15 16:02:24

Wow! I can now start Chrome again I am so happy Thanks

Here is the output.
http://0x0.st/HUnF.txt

I have now made a bash alias for updating, so I will never make this mistake again!

Have I broken other packages?

Scimmia · 2024-01-15 16:07:40

-Syu and -Suy are the same thing, seth was making a joke.

Hard to say just why it happened, it shouldn't have. My only theory is that for some reason files didn't get flushed to disk when you shut down like they should have been. Too much and hit a timeout, maybe?

seth · 2024-01-15 16:48:28

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

The errors show up w/ the chroot update

[2024-01-15T11:00:08+0100] [PACMAN] Running 'pacman --sysroot /mnt/fs -Suy'

which was likely already a mitigational effort?
Eg qt5-base got updated 1h before

[2024-01-15T09:54:33+0100] [ALPM] upgraded qt5-base (5.15.11+kde+r148-1 -> 5.15.12+kde+r147-1)

sowhatever happened, happened during that hour.
Any ideas?

https://bbs.archlinux.org/viewtopic.php … 5#p2082235 - last paragraph. Don't be a creep

LittleSandra · 2024-01-15 22:36:37

seth wrote:

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Absolutely I was just waiting for your reply, as I wasn't all the packages had been fixed.

seth wrote:

The errors show up w/ the chroot update
[2024-01-15T11:00:08+0100] [PACMAN] Running 'pacman --sysroot /mnt/fs -Suy'
which was likely already a mitigational effort?

Yes

seth wrote:

Eg qt5-base got updated 1h before
[2024-01-15T09:54:33+0100] [ALPM] upgraded qt5-base (5.15.11+kde+r148-1 -> 5.15.12+kde+r147-1)
sowhatever happened, happened during that hour.
Any ideas?

No idea. My laptop usually have an update of +60 days, and it was really slow when I did the update. Perhaps I should have rebooted before the update?

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 5#p2082235 - last paragraph. Don't be a creep

Thanks.

seth · 2024-01-15 22:46:30

Was it also really slow to reboot and you used the power button?
You might also have run OOM, do you have an AMD GPU?

LittleSandra · 2024-01-15 23:48:47

Well, it seg. faulted when I rebooted, so I had to use the power button. So in a way "yes" to your question

I am not familiar with OOM. No AMD GPU. It is an ThinkPad T470s.

Last edited by LittleSandra (2024-01-16 00:14:05)

seth · 2024-01-16 08:36:49

"out of memory", but the powerbutton invocation sufficiently explains the status quo.
Avoid that at all costs, https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Do you remember what segfaulted?

LittleSandra · 2024-01-16 21:46:41

I didn't think to take a screenshot of the seg. fault I'll remember that for next time.

So all I have to do is

echo "kernel.sysrq = 16" > /etc/sysctl.d/99-sysctl.conf

and then I can use "Alt+SysRq+s" to sync all data to disk when the system have seg. fauled?

Or had you something else in mind?

seth · 2024-01-16 22:17:09

It depends on what the "segfault" actually is*, but if the kernel is still responsive, then yes.

*the kernel might have panicked or the failure might happen after the FS have been synced anyway.

Arch Linux

#1 2024-01-15 11:15:33

[SOLVED] pacman -Suy broke with "is not an ELF file

#2 2024-01-15 13:08:16

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#3 2024-01-15 13:34:00

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#4 2024-01-15 14:27:23

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#5 2024-01-15 16:02:24

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#6 2024-01-15 16:07:40

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#7 2024-01-15 16:48:28

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#8 2024-01-15 22:36:37

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#9 2024-01-15 22:46:30

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#10 2024-01-15 23:48:47

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#11 2024-01-16 08:36:49

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#12 2024-01-16 21:46:41

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

#13 2024-01-16 22:17:09

Re: [SOLVED] pacman -Suy broke with "is not an ELF file

Board footer