KDE has broken, extra kernel?

kde
kernel

#1

Hi all,

today very strange thing happened with me. I am using the latest KDE 16.10.3, everything was running smooth and nice. today I decided to install kmail&korganizer&knotes.
I was able successfully to install and set up my these apps. During the synchronizing, my laptop started to freeze. which I though is ok, as it was the first run of kmail&korganizer and it occurred to me earlier as well.
but suddenly the system, froze completely, whatever I was doing it was not reacting. So I pressed power button (just once, not for a long time) and it shut down.

Now when I try to turn it on, it stacks on Plymouth screen. I cant switch tty’s there is no response.

I had Manjaro Cinnamon live media, so I booted it and was able to store local data. than I thought I can install another kernel, just to see does it matter or no?
I followed this instruction


but it fails to execute command N5.

anyway, I turned it off and started again and noticed that I have kernel3.10.104-1MANJARO x64 kernel installed alongside kernel44.

I have never installed it, now I am wondering how that appeared there? Previously I have not seen such thing.
and how can I fix my system?


#2

but it fails to execute command N5.

The command you mention is sudo mhwd-chroot /mnt. While I’m wondering where @Heart-Of-A-Lion got the info that the command needs a “/mnt”, not from https://wiki.manjaro.org/index.php/Restore_the_GRUB_Bootloader
Maybe try again with a more reliable guide, i.e. the Manjaro Wiki.
Or do you happen to have a untypical file system like btrfs so mhwd-chroot is failing? Then you need to chroot manually.

Second issue: To see when linux310 got installed on your system, look into /var/log/pacman.log on that system, you can do it from live USB, of course.


#3

in wiki, use mhwd-chroot ? now we have manjaro-chroot

et me, before chroot, i edit grub with option 3 (or 1)

linux /boot/vmlinuz-4.4-x86_64 root=UUID=978e3e81-8a06 rw 3

#4

Yeah, the command
manjaro-chroot -a
would likely do the job if you have a standard file system. https://github.com/manjaro/manjaro-tools#6-manjaro-chroot
But mhwd-chroot is a script which uses the command which you would us in manual chrooting, it should work reliably for ages, I would guess.


#5

thanks for the quick response,
I tried to follow the wiki and to restore grub, but it failed at grub-install /dev/sda, as for some reason it was choosing 32-bit system.
it was saying can’t open ‘/boot/grub/i386-pc/core.img’

well I was able to chroot using that command, before posting here, but still I was not able to install new kernel
I am running cinnamon with kernel48, and when chrooted I want to install 48 series to my system it says, that I cant reinstall my current kernel.

also I tried to turn on laptop again, on the plymount screen I pressed esc and it switched to shell where it was complaining about fsck, that disk is ok, but journel is not there, somewhat like this


#6

if you have Plymouth, I guess grub works well, the problem is elsewhere, display manager, video driver … read logs


#7

With such an imprecise kind of information I cannot help you. Please, post terminal outputs, file contents, photos of the boot error. You should have internet connection on the live USB.


#8

here is the screenshot, when I press Esc at plymounth screeen


#9

Never seen such a screen. Would use the search engine with exact wording of some error messages and see what it it gives.

Probably you will need to use your live USB to run fsck /dev/sda1.


#10

me either, I will try to do that now.
now I want to see log files in order to understand, when the second kernel was installed.
It is not possible that some app installed it as dependency, right?
I haven’t installed it for sue, and I dont understand how can it appear there


#11

Seems, when I was trzing to install virtual box, it also installed linux310 headers, but this is not kernel right?
than I removed it, but seems it somehow modified my grub. here is the log

[2016-12-11 11:04] [ALPM] installed linux310 (3.10.104-1)
[2016-12-11 11:04] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2016-12-11 11:04] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux310.preset: 'default'
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-3.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-3.10-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Starting build: 3.10.104-1-MANJARO
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [plymouth]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-3.10-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux310.preset: 'fallback'
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-3.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-3.10-x86_64-fallback.img -S autodetect
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Starting build: 3.10.104-1-MANJARO
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [plymouth]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-12-11 11:04] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-3.10-x86_64-fallback.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-12-11 11:04] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found Intel Microcode image
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.4-x86_64
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd image: /boot/initramfs-4.4-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.4-x86_64-fallback.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-3.10-x86_64
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd image: /boot/initramfs-3.10-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-3.10-x86_64-fallback.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2016-12-11 11:04] [ALPM-SCRIPTLET] done
[2016-12-11 11:04] [ALPM] installed linux310-virtualbox-host-modules (5.1.10-1)
[2016-12-11 11:04] [ALPM-SCRIPTLET] ===> You must load vboxdrv module before starting VirtualBox:
[2016-12-11 11:04] [ALPM-SCRIPTLET] ===> # modprobe vboxdrv
[2016-12-11 11:04] [ALPM] installed virtualbox (5.1.10-1)
[2016-12-11 11:04] [ALPM] installed libvncserver (0.9.10-4)
[2016-12-11 11:04] [ALPM] installed virtualbox-ext-vnc (5.1.10-1)
[2016-12-11 11:04] [ALPM-SCRIPTLET] 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[2016-12-11 11:04] [ALPM] installed virtualbox-sdk (5.1.10-1)
[2016-12-11 11:04] [ALPM] transaction completed
[2016-12-11 11:04] [ALPM] running '99-grub.hook'...
[2016-12-11 11:04] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found Intel Microcode image
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.4-x86_64
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd image: /boot/initramfs-4.4-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.4-x86_64-fallback.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-3.10-x86_64
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd image: /boot/initramfs-3.10-x86_64.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-3.10-x86_64-fallback.img
[2016-12-11 11:04] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2016-12-11 11:04] [ALPM-SCRIPTLET] done
[2016-12-11 11:04] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-12-11 11:04] [ALPM] running 'update-desktop-database.hook'...
[2016-12-11 11:04] [ALPM] running 'update-mime-database.hook'...
[2016-12-11 11:04] [ALPM-SCRIPTLET] Unknown media type in type 'all/all'
[2016-12-11 11:04] [ALPM-SCRIPTLET] Unknown media type in type 'all/allfiles'
[2016-12-11 11:19] [PACMAN] Running 'pacman -R --noconfirm libvncserver linux310-virtualbox-host-modules virtualbox-ext-vnc virtualbox'
[2016-12-11 11:19] [ALPM] transaction started
[2016-12-11 11:19] [ALPM-SCRIPTLET] 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[2016-12-11 11:19] [ALPM] removed virtualbox-ext-vnc (5.1.10-1)
[2016-12-11 11:19] [ALPM] removed virtualbox (5.1.10-1)
[2016-12-11 11:19] [ALPM] removed linux310-virtualbox-host-modules (5.1.10-1)
[2016-12-11 11:19] [ALPM] removed libvncserver (0.9.10-4)
[2016-12-11 11:19] [ALPM] transaction completed

and the last log before crushing

[2016-12-15 16:46] [PACMAN] Running 'pacman -S --noconfirm extra/kdepim-addons extra/korganizer extra/kmail extra/knotes'
[2016-12-15 16:46] [ALPM] transaction started
[2016-12-15 16:46] [ALPM] installed akonadi-mime (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed akonadi-search (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kmbox (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kldap (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libkdepim (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed mailimporter (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kimap (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed pimcommon (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed grantleetheme (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kdepim-apps-libs (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kmailtransport (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libgravatar (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed akonadi-notes (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kidentitymanagement (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed messagelib (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed mailcommon (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kcalutils (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed akonadi-calendar (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed calendarsupport (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kdgantt2 (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed eventviews (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed incidenceeditor (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libktnef (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libkgapi (5.3.1-1)
[2016-12-15 16:46] [ALPM] installed kdepim-addons (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libkolabxml (1.1.6-2)
[2016-12-15 16:46] [ALPM] installed libkolab (1.0.2-2)
[2016-12-15 16:46] [ALPM] installed kross (5.28.0-1)
[2016-12-15 16:46] [ALPM] installed kalarmcal (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kde-syndication (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kdepim-runtime (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kdepim-common (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kontactinterface (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed korganizer (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed libksieve (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed kmail (16.08.3-1)
[2016-12-15 16:46] [ALPM] installed knotes (16.08.3-1)
[2016-12-15 16:46] [ALPM] transaction completed
[2016-12-15 16:46] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-12-15 16:46] [ALPM] running 'update-desktop-database.hook'...
[2016-12-15 16:46] [ALPM] running 'update-mime-database.hook'...
[2016-12-15 16:46] [ALPM-SCRIPTLET] Unknown media type in type 'all/all'
[2016-12-15 16:46] [ALPM-SCRIPTLET] Unknown media type in type 'all/allfiles'

Virtualbox has host modules for kernel 310 instead of a current running kernel
#12

I don’t use Virtual Box, but I guess, if you want to run virtualbox you need to boot the kernel for which you have the virtualbox kernel modules installed. But this is unrelated to your current boot problem.

Now you need to run fsck for the right partition. Find out with blkid or lsblk -f which partition you want to check.


#13

shell I do it from live enviroment? or from the screen I post above?
and if from live enviroment? should it be chrooted?


#14

I’m not the Arch Wiki, :wink: but I will look for you how to use fsck.


#15

sorry, I thought you know, I can do web searching as well :slight_smile: thanks


#16

You can do both ways, but with live CD is maybe easier.

But I think the problem could be not fsck, but a failed creation of initramfs. To repair this I would recommend to boot with the live USB, chroot the installed system with one of the working methods, run
# mkinitcpio -p linux44
and reboot.
You can try installing another kernel while in the chroot
# mhwd-kernel -i linux49
It is not necessary, but will do no harm (unless you have a separate /boot partition which could get full).


#17

I tried this, but it didnt change anything.

when I am trying to install new kernel, it says

mhwd-kernel -i linux49
error: could not open file /var/lib/pacman/local/btrfs-progs-4.8.2-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/ca-certificates-mozilla-3.27.1-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/calibre-2.73.0-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/cherrytree-0.37.5-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/coreutils-8.25-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/curl-7.51.0-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/dbus-1.10.12-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/device-mapper-2.02.167-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/exfat-utils-1.2.4-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/gnutls-3.4.16-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/krb5-1.13.4-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/libsystemd-232-4/desc: No such file or directory
error: could not open file /var/lib/pacman/local/linux44-4.4.36-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/lvm2-2.02.167-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/lz4-131-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/ncurses-6.0+20161112-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/nss-3.27.1-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/openvpn-2.3.13-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/python2-html5lib-0.9999999-2/desc: No such file or directory
error: could not open file /var/lib/pacman/local/readline-7.0-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/rpcbind-0.2.3-3/desc: No such file or directory
error: could not open file /var/lib/pacman/local/systemd-232-4/desc: No such file or directory
error: could not open file /var/lib/pacman/local/systemd-sysvcompat-232-4/desc: No such file or directory
:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update multilib (unable to lock database)
error: failed to synchronize any databases
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
  if you're sure a package manager is not already
  running, you can remove /var/lib/pacman/db.lck
The following packages are out of date, please update your system first: btrfs-progs ca-certificates-mozilla calibre cherrytree coreutils curl dbus device-mapper exfat-utils gnutls krb5 libsystemd linux44 lvm2 lz4 ncurses nss openvpn python2-html5lib readline rpcbind systemd systemd-sysvcompat 
Do you want to continue anyway? [y/N] N

and when I say y
it fails, than I run

pacman -Syyu

which again results in

  if you're sure a package manager is not already
  running, you can remove /var/lib/pacman/db.lck

I tried

rm /var/lib/pacman/db.lck
sudo rm /var/lib/pacman/db.lck
rm: cannot remove '/var/lib/pacman/db.lck': No such file or directory


Not able to boot KDE after update (Dec. 11 or 12)
#18

well, I guess I need to reinstall the system…


#19

it maybe better. and about why kernel 3.10 got installed. it’s because you installed virtualbox without choosing the host module for all your installed kernel. then octopi choosed to install the host module for kernel 3.10 to solve dependencies… and then installed kernel 3.10.
next time you install virtual box. also install linuxXX-virtualbox-host-modules for all the kernel you have installed.
like this the dependencies are met and octopi won’t choose to install the module for kernel 3.10.
see


#20

https://bugs.archlinux.org/task/11767#comment33404

I would try this from chroot just for the lulz before reinstalling.