Many errors during pacman -Syu, install may be corrupt.

LinearView88 · 2024-07-21 19:22:52

I just tried to upgrade my system and ran into some odd issues with pacman -Syu. Specifically, the command hung during my dkms install for nvidia. I killed that command, and the rest of the update proceeded in an unexpected way, as seen below:

:: Running post-transaction hooks...
( 1/19) Creating system user accounts...
( 2/19) Registering binary formats...
( 3/19) Reloading system manager configuration...
( 4/19) Reloading user manager configuration...
( 5/19) Creating temporary files...
( 6/19) Arming ConditionNeedsUpdate...
corrupted size vs. prev_size
error: command terminated by signal 6: Aborted
( 7/19) Updating the MIME type database...
( 8/19) Updating module dependencies...
( 9/19) Install DKMS modules
==> dkms install --no-depmod nvidia/555.58.02 -k 6.9.10-arch1-1
^C
Interrupt signal received
error: command terminated by signal 2: Interrupt
(10/19) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img
==> Starting build: '6.6.40-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: '6.6.40-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
double free or corruption (!prev)
/usr/bin/mkinitcpio: line 692: 20873 Aborted                 (core dumped) MKINITCPIO_PROCESS_PRESET="$preset_name" "$0" "${preset_cmd[@]}"
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.9.10-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.9.10-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
error: command failed to execute correctly
(11/19) Reloading system bus configuration...
(12/19) Warn about old perl modules
(13/19) Updating fontconfig cache...
(14/19) Updating 32-bit fontconfig cache...
(15/19) Probing GDK-Pixbuf loader modules...
(16/19) Compiling GSettings XML schema files...
(17/19) Updating icon theme caches...
(18/19) Updating the info directory file...
malloc_consolidate(): invalid chunk size
error: command terminated by signal 6: Aborted
(19/19) Updating the desktop file MIME type cache...
corrupted size vs. prev_size
error: command terminated by signal 6: Aborted

I'm afraid to reboot right now, and I'm not sure how to go about fixing what's likely to be wrong, or even what's currently wrong.

EDIT:

ran pacman -S nvidia-dkms, and this time the command completed. Kind of.

warning: nvidia-dkms-555.58.02-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) nvidia-dkms-555.58.02-1

Total Installed Size:  68.91 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                                                   [-------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                 [-------------------------------------------------------------------] 100%
(1/1) loading package files                                                                                      [-------------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                                [-------------------------------------------------------------------] 100%
(1/1) checking available disk space                                                                              [-------------------------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove nvidia/555.58.02
:: Processing package changes...
(1/1) reinstalling nvidia-dkms                                                                                   [-------------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Install DKMS modules
==> dkms install --no-depmod nvidia/555.58.02 -k 6.9.10-arch1-1
Error! Bad return status for module build on kernel: 6.9.10-arch1-1 (x86_64)
Consult /var/lib/dkms/nvidia/555.58.02/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/555.58.02 -k 6.9.10-arch1-1' exited 10
==> dkms install --no-depmod nvidia/555.58.02 -k 6.6.40-1-lts
Error! Bad return status for module build on kernel: 6.6.40-1-lts (x86_64)
Consult /var/lib/dkms/nvidia/555.58.02/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/555.58.02 -k 6.6.40-1-lts' exited 10
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img
==> Starting build: '6.6.40-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: '6.6.40-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.9.10-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.9.10-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

Many of my graphical programs are crashing after a few minutes of use.

Last edited by LinearView88 (2024-07-22 01:22:00)

gromit · 2024-07-21 20:09:48

Consult /var/lib/dkms/nvidia/555.58.02/build/make.log for more information.

So whats in there then?

LinearView88 · 2024-07-21 20:14:40

https://0x0.st/XpcD.log

seth · 2024-07-21 20:46:03

If you're running

dkms install --no-depmod nvidia/555.58.02 -k 6.9.10-arch1-1

by itself?
Sidebar: you've the main and the LTS kernel and are using the 555xx drivers - why are you not just using the pre-built modules?

LinearView88 · 2024-07-21 20:57:01

Command is running incredibly slowly. We'll see where it goes.

I'm not too proud to say that I font know and I don't know how to switch. I created this setup through archinstall and then modified it, but I have little memory of how.

Most graphical programs still crashing or functioning oddly, including firefox and libreoffice. Firefox does not work but reopens as a background process when killed. Things are barely usable.

LinearView88 · 2024-07-21 21:15:23

Still sitting on the make invocation with dots filling up the terminal. Not feeling optimistic about this one.

seth · 2024-07-21 21:26:06

Depending on how much of a potatoe you're running, this can take a while - does some cc process charge your CPU?
You can just remove nvidia-dkms and install nvidia and nvidia-lts instead

LinearView88 · 2024-07-21 21:33:52

The strange thing is I'm not even using a potato.

Had to force a restart, and now simply running pacman -R nvidia-dkms results Ina double free or corruption error. Same with any other pacman command. Startx also fails with no screens found.

Time to chroot with a live USB?

Last edited by LinearView88 (2024-07-21 21:36:59)

seth · 2024-07-21 21:37:32

Don't even chroot, from the iso, after mounting your system into /mnt

LC_ALL=C pacman --root=/mnt -Qkk | grep -v ', 0 altered files'

But startx fails because you've no nvidia kernel module, so the the nvidia drivers won't work and nouveau is blocked by them, so the modestting driver also doesn't work.

But there's something else broken with this system.

LinearView88 · 2024-07-21 21:52:44

https://0x0.st/XpT9.log

Hopefully this is correct.

seth · 2024-07-21 21:57:06

Yes, but doesn't look suspicious at all.
You can try to install nvidia and nvidia dkms from the iso (either chrooting into the system or using --sysroot /mnt) but that doesn't explain your compilation issues

LinearView88 · 2024-07-21 22:03:18

Thanks. Installed nvidia and nvidia-lts after chrooting. Anything else I should try or look at while I'm in my live ISO? Something I could reinstall to potentially address compilation errors?

seth · 2024-07-21 22:21:31

First see whether the issues remain at all.

LinearView88 · 2024-07-21 22:34:42

I'm writing this from my machine instead of from mobile, so that's good news! Everything seems fine now. My X server is working, and I'm able to install and uninstall packages with pacman without running into corruptions. Wildly unsure what caused the initial issues, but they seem to be solved now. Cautiously marking this thread as solved.

Thanks again, Seth! Have a good one.

LinearView88 · 2024-07-21 22:45:20

Of course not ten minutes after I post this firefox crashes, then systemd crashes along with a coredump. Should I post that here or make a new thread?

seth · 2024-07-21 22:51:32

The thread started w/ compilation errors and those are probably not gone.
Post the backtraces/system journal here.
FF + nvidia + wayland is currently on the record, https://bbs.archlinux.org/viewtopic.php?id=297903 / https://bbs.archlinux.org/viewtopic.php?id=297835

Otherwise, have you already run memtest86+ ?

There're ongoing issues w/ the nvidia drivers > 545xx seemingly corrupting the kernel space, but that would require to build https://aur.archlinux.org/packages/nvidia-535xx-dkms …

LinearView88 · 2024-07-21 23:06:55

Https://0x0.st/XpAA.log

I'm not on Wayland, but based on what I saw on those threads I wouldn't be surprised if its an Nvidia/Firefox bug. The behavior sounds similar.

I've never run memtest86+ before; I'm not exactly sure what it is. Based on what I saw on the wiki, it seems like a CPU testing tool you can boot to?

seth · 2024-07-22 06:13:46

https://0x0.st/XpAA.log
https://wiki.archlinux.org/title/Stress … MemTest86+

Crashes somewhere deeeeep in xul, no signs of nvidia involvement.
https://wiki.archlinux.org/title/Debuginfod

https://wiki.archlinux.org/title/Firefo … shoot_Mode ?

LinearView88 · 2024-07-22 17:11:14

Going to take a look again later today. Could also be related to this, since I have egl-wayland?

https://bbs.archlinux.org/viewtopic.php … 0#p2184720

Current Firefox behavior is odd. Tabs crash, and occasionally full browser crashes. When the browser crashes, Firefox refuses to be killed. Regardless of the message used to kill it, it restarts in the background and prevents the system from shutting down cleanly. Thought it might be an add-on that's chasing it to loop like this but no real idea. Sigh.

seth · 2024-07-22 20:49:51

Did you try to downgrade mesa and egl-wayland and does that prevent the crashes?
https://bbs.archlinux.org/viewtopic.php … 5#p2185215

LinearView88 · 2024-07-22 21:50:58

Yeah. Was hopeful, but the downgrade didn't work.

LinearView88 · 2024-07-25 02:08:28

Well, the good news is I think I've nailed down a root cause. The bad news is what that cause is.

Ran Memtest86+. It threw multiple tens of thousands of errors. Before I contact my vendor (Given that this is a very new system, I'm guessing it was sold to me in this condition) am I safe in assuming that this is a hardware problem of some sort?

seth · 2024-07-25 06:33:30

Do you overclock the RAM or use XMP?
Don't - select the most conservative timings and clocks for the RAM and see whether it stabilizes.

gromit · 2024-07-25 09:30:01

Also did you make sure that your ram sticks are properly in place? A friend of mine had that once

LinearView88 · 2024-07-25 11:33:52

Nope, never even tried to overclock. This is a laptop, so I've never touched the RAM inside it. I suppose it could be misaligned of seated badly, but I'm not sure how to fix that or ascertain if it is happening.

Last edited by LinearView88 (2024-07-25 13:54:36)

Arch Linux

#1 2024-07-21 19:22:52

Many errors during pacman -Syu, install may be corrupt.

#2 2024-07-21 20:09:48

Re: Many errors during pacman -Syu, install may be corrupt.

#3 2024-07-21 20:14:40

Re: Many errors during pacman -Syu, install may be corrupt.

#4 2024-07-21 20:46:03

Re: Many errors during pacman -Syu, install may be corrupt.

#5 2024-07-21 20:57:01

Re: Many errors during pacman -Syu, install may be corrupt.

#6 2024-07-21 21:15:23

Re: Many errors during pacman -Syu, install may be corrupt.

#7 2024-07-21 21:26:06

Re: Many errors during pacman -Syu, install may be corrupt.

#8 2024-07-21 21:33:52

Re: Many errors during pacman -Syu, install may be corrupt.

#9 2024-07-21 21:37:32

Re: Many errors during pacman -Syu, install may be corrupt.

#10 2024-07-21 21:52:44

Re: Many errors during pacman -Syu, install may be corrupt.

#11 2024-07-21 21:57:06

Re: Many errors during pacman -Syu, install may be corrupt.

#12 2024-07-21 22:03:18

Re: Many errors during pacman -Syu, install may be corrupt.

#13 2024-07-21 22:21:31

Re: Many errors during pacman -Syu, install may be corrupt.

#14 2024-07-21 22:34:42

Re: Many errors during pacman -Syu, install may be corrupt.

#15 2024-07-21 22:45:20

Re: Many errors during pacman -Syu, install may be corrupt.

#16 2024-07-21 22:51:32

Re: Many errors during pacman -Syu, install may be corrupt.

#17 2024-07-21 23:06:55

Re: Many errors during pacman -Syu, install may be corrupt.

#18 2024-07-22 06:13:46

Re: Many errors during pacman -Syu, install may be corrupt.

#19 2024-07-22 17:11:14

Re: Many errors during pacman -Syu, install may be corrupt.

#20 2024-07-22 20:49:51

Re: Many errors during pacman -Syu, install may be corrupt.

#21 2024-07-22 21:50:58

Re: Many errors during pacman -Syu, install may be corrupt.

#22 2024-07-25 02:08:28

Re: Many errors during pacman -Syu, install may be corrupt.

#23 2024-07-25 06:33:30

Re: Many errors during pacman -Syu, install may be corrupt.

#24 2024-07-25 09:30:01

Re: Many errors during pacman -Syu, install may be corrupt.

#25 2024-07-25 11:33:52

Re: Many errors during pacman -Syu, install may be corrupt.

Board footer