Choose style:

Author Topic: Boot Problems after updates  (Read 1186 times)

0 Members and 1 Guest are viewing this topic.

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 25082
  • Karma: 2774
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 8R, 9, and 9R
Re: Boot Problems after updates
« Reply #15 on: April 06, 2017, 07:04:27 pm »
Okay It looks like you've run out of room for new kernels  .. gimme a sec and I'll tell you how to fix this.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 25082
  • Karma: 2774
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 8R, 9, and 9R
Re: Boot Problems after updates
« Reply #16 on: April 06, 2017, 07:17:34 pm »
Okay, open a terminal and run:
Code: [Select]
sudo apt-get remove --purge linux-headers-4.4.0-24 linux-headers-4.4.0-24-generic linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic linux-headers-4.4.0-34 linux-headers-4.4.0-34-generic linux-headers-4.4.0-43 linux-headers-4.4.0-43-generic linux-headers-4.4.0-47 linux-headers-4.4.0-47-generic linux-image-4.4.0-24-generic linux-image-4.4.0-31-generic linux-image-4.4.0-34-generic linux-image-4.4.0-43-generic linux-image-4.4.0-47-generic linux-image-extra-4.4.0-24-generic linux-image-extra-4.4.0-31-generic linux-image-extra-4.4.0-34-generic linux-image-extra-4.4.0-43-generic linux-image-extra-4.4.0-47-generic linux-signed-image-4.4.0-24-generic linux-signed-image-4.4.0-31-generic linux-signed-image-4.4.0-34-generic linux-signed-image-4.4.0-43-generic linux-signed-image-4.4.0-47-generic
(make sure you get all that command, it's rather long)

then
Code: [Select]
sudo apt-get -f install
did those commands finish without error ?
« Last Edit: April 06, 2017, 07:20:35 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline andrew01777

  • nOOb
  • *
  • Posts: 12
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Re: Boot Problems after updates
« Reply #17 on: April 06, 2017, 07:41:04 pm »
i just followed them instructions , rebooted the laptop and it went straight into os. ill be honest, i dont understand what we just did or how you fixed it but thanks so much!!!!!!!

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 25082
  • Karma: 2774
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 8R, 9, and 9R
Re: Boot Problems after updates
« Reply #18 on: April 06, 2017, 07:50:30 pm »
Not finished yet

Can you now post the output from:
Code: [Select]
dpkg -l | grep 4.4.0
and
Code: [Select]
dpkg -l | grep 4.8.0
and
Code: [Select]
dpkg -l | grep hwe-16.04
and
Code: [Select]
uname -a
« Last Edit: April 06, 2017, 07:53:14 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4808
  • Karma: 1012
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 8 Respin-2 (64-bit)
Re: Boot Problems after updates
« Reply #19 on: April 06, 2017, 07:59:23 pm »
Hi andrew01777, How's it going?  For future reference, could you please remember to encapsulate terminal outputs with the Insert, Code # function.  For extra long outputs, please use the Spoiler, Sp function.  Chromium Browser and Google Chrome users, please don't combine the functions.  Only use one or the other  ;).  These preserve the original format of the output.  This makes it easier for future visitors to relate to their own issues.  These functions are found in the forum editor, above the,  :-[ Embarrassed and  the :'( Cry emoticon respectively.  Use the Preview button to see how it'll look in the forum.  This time, I've done it for you - many thanks  ;).

What you've just done, is remove all the redundant old kernel, bar the penultimate one.  This is always your backup kernel, if the current one gives you issues.  Kernels are not automatically removed in Linux.  That's always left to the user to do.  You'd acquired a good collection of old kernels  ;D.  They'd filled up the /boot partition.  So no more could be added.  This is why you were getting errors.  It was time for some routine housekeeping.  If you want advice on how to do this on a regular basis, just ask and someone will explain how to do it.  It really simple and only takes a couple of minutes to do  ;).
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.