[opensuse] Leap 42 3 kernel update to 4.4.132 failed?
All, I had not seen this one before, upon zypper up -r update, the update to 4.4.132 failed with: (36/49) Installing: kernel-default-4.4.132-53.1.x86_64 .....................................................[error] Installation of kernel-default-4.4.132-53.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: warning: %post(kernel-default-4.4.132-53.1.x86_64) scriptlet failed, signal 2 Which left the box unbootable. Thankfully I still have the .126 kernel that was fine, so I booted 126 and reinstalled all kernel rpms, e.g. rpm -Uvh --replacepkgs --replacefiles (the list of noarch & x86_64 packages, devel packages and kernel sources. The install succeeded the 2nd time. What 'scriptlet' is it saying failed with signal 2? And what could cause such a failure? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-28 12:52, David C. Rankin wrote:
All,
I had not seen this one before, upon zypper up -r update, the update to 4.4.132 failed with:
(36/49) Installing: kernel-default-4.4.132-53.1.x86_64 .....................................................[error] Installation of kernel-default-4.4.132-53.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: warning: %post(kernel-default-4.4.132-53.1.x86_64) scriptlet failed, signal 2
Which left the box unbootable. Thankfully I still have the .126 kernel that was fine, so I booted 126 and reinstalled all kernel rpms, e.g.
rpm -Uvh --replacepkgs --replacefiles (the list of noarch & x86_64 packages, devel packages and kernel sources.
The install succeeded the 2nd time. What 'scriptlet' is it saying failed with signal 2? And what could cause such a failure?
Disk full? Shot in the dark, seems to be the most common problem. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Mon, May 28, 2018 at 1:10 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Disk full? Shot in the dark, seems to be the most common problem.
I have had that happen. IIRC, one does get a message that there is not enough disk space. But failure is typically not a good thing. I keep fighting with this on my laptop because Tumbleweed sometimes has tons of updates. It's not unusual to need many GB free on /. And the GBs do get eaten fast. And snapper is often not freeing disk space as one might expect. So I have to delete snapshots to get free space. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/28/2018 06:14 AM, Roger Oberholtzer wrote:
On Mon, May 28, 2018 at 1:10 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Disk full? Shot in the dark, seems to be the most common problem.
I have had that happen. IIRC, one does get a message that there is not enough disk space. But failure is typically not a good thing.
I keep fighting with this on my laptop because Tumbleweed sometimes has tons of updates. It's not unusual to need many GB free on /. And the GBs do get eaten fast. And snapper is often not freeing disk space as one might expect. So I have to delete snapshots to get free space.
Hmm... Not a chance it was a disk-full issue: $ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 1.9M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda2 40G 12G 27G 31% / tmpfs 1.9G 32K 1.9G 1% /tmp /dev/sda3 876G 2.2G 873G 1% /home tmpfs 383M 0 383M 0% /run/user/1000 27G free on / and 873G free on /home (both ext4)? Strange indeed. This is only an older laptop with a: AMD Turion(tm) 64 X2 Mobile Technology TL-58 I wonder if the associated firmware-update may have somewhat dubious behavior regarding older mobile chipsets? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R. -
David C. Rankin -
Roger Oberholtzer