Stuck on Bad Kernel? (4.15.18-12)

Discussion in 'Proxmox VE: Installation and configuration' started by ferociousmilkyway, Apr 25, 2019.

  1. ferociousmilkyway

    ferociousmilkyway New Member

    Joined:
    Aug 2, 2018
    Messages:
    25
    Likes Received:
    1
    Hello,

    Today in (my non-pve subscription repo) I saw two kernels 4.15.18-12 & -13. I clicked update and rebooted and it dropped into initramfs. I manually edited grub boot parameters via the boot menu back to -11 and booted, but now I'm unsure how to get (permanently) onto the correct kernel (is 4.15.18-13 the correct version)?

    I tried to look around first before bothering people here in the forum, but I'm not experienced on the this topic yet. Any help appreciated, otherwise I'm sure I'll eventually figure it out.

    Thanks for Proxmox!
     
  2. ferociousmilkyway

    ferociousmilkyway New Member

    Joined:
    Aug 2, 2018
    Messages:
    25
    Likes Received:
    1
  3. t.lamprecht

    t.lamprecht Proxmox Staff Member
    Staff Member

    Joined:
    Jul 28, 2015
    Messages:
    1,177
    Likes Received:
    155
    Glad you solved it, but this should not happen, the newest (by version) kernel is booted per default..

    What's in your /var/log/apt/history.log for the respective update?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. ferociousmilkyway

    ferociousmilkyway New Member

    Joined:
    Aug 2, 2018
    Messages:
    25
    Likes Received:
    1
    Start-Date: 2019-04-14 05:07:11
    Commandline: apt-get dist-upgrade
    Upgrade: libssh2-1:amd64 (1.7.0-1, 1.7.0-1+deb9u1)
    End-Date: 2019-04-14 05:07:11

    Start-Date: 2019-04-24 10:25:42
    Commandline: apt-get dist-upgrade
    Install: pve-kernel-4.15.18-13-pve:amd64 (4.15.18-37, automatic)
    Upgrade: proxmox-widget-toolkit:amd64 (1.0-25, 1.0-26), pve-firewall:amd64 (3.0-19, 3.0-20), pve-kernel-4.15.18-12-pve:amd64 (4.15.18-35, 4.15.18-36), pve-manager:amd64 (5.4-3, 5.4-4), libpve-common-perl:amd64 (5.0-50, 5.0-51), pve-kernel-4.15:amd64 (5.3-3, 5.4-1)
    Error: Sub-process /usr/bin/dpkg returned an error code (2)
    End-Date: 2019-04-24 10:25:58

    Start-Date: 2019-04-24 20:33:18
    Commandline: apt purge pve-kernel-4.15.18-12-pve
    Purge: pve-kernel-4.15.18-12-pve:amd64 (4.15.18-36)
    End-Date: 2019-04-24 20:33:57
     
  5. t.lamprecht

    t.lamprecht Proxmox Staff Member
    Staff Member

    Joined:
    Jul 28, 2015
    Messages:
    1,177
    Likes Received:
    155
    The upgrade did not go well, it seems, maybe a write error to a disk, or some other error? I'd look into syslog and take a quick look over your disk SMART stats, e.e., wearout (visible through WebUI).
    Also
    Code:
    less /var/log/apt/term.log
    could be used to possibly get more out of the "Error: Sub-process /usr/bin/dpkg returned an error code (2)" message and see what the real issue was.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. ferociousmilkyway

    ferociousmilkyway New Member

    Joined:
    Aug 2, 2018
    Messages:
    25
    Likes Received:
    1
    Thank you for the tip, I'll look into it. Unfortunately the disks are attached to a low-grade raid controller that doesn't pass SMART. I'll let this serve as a warning I may have a failing drive and run some backups.
     
  7. Paspao

    Paspao Member

    Joined:
    Aug 1, 2017
    Messages:
    37
    Likes Received:
    1
    Hello,

    I don't know if it is related but I see a difference on kernel updates available on CLI and GUI.

    CLI shows:

    Code:
    pve-kernel-4.15/stable 5.4-1 all [upgradable from: 5.3-3]
    pve-kernel-4.15.18-12-pve/stable 4.15.18-36 amd64 [upgradable from: 4.15.18-35]
    GUI shows:
    https://www.dropbox.com/s/q2oyaeywn6lorx0/proxmox-kernel.png?dl=0

    Is this normal behaviour?

    Thanks.
    P.
     
  8. t.lamprecht

    t.lamprecht Proxmox Staff Member
    Staff Member

    Joined:
    Jul 28, 2015
    Messages:
    1,177
    Likes Received:
    155
    Yes, from what I can tell yes.

    The thing is, new kernel ABI bumps get installed as new package, i.e., it's not counted as upgrade but as new install. E.g., on a test system here I see:
    Code:
    # apt dist-upgrade
    ...
    The following NEW packages will be installed:
      pve-kernel-4.15.18-13-pve
    The following packages will be upgraded:
      pve-kernel-4.15 pve-kernel-4.15.18-12-pve
    2 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    
    The WebUI puts those together, the CLI splits it. "apt list --upgradable" does not shows the new installed one which gets pulled in by the upgrade of our so called meta-package "pve-kernel-4.15"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    Paspao likes this.
  9. Paspao

    Paspao Member

    Joined:
    Aug 1, 2017
    Messages:
    37
    Likes Received:
    1
    Thank you ;-)
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice