Smashed my system again
Why did apt-get want to auto-remove 83?
In fact, why did you run auto-remove at all?
Personally, if I'd seen that, I would check & possibly manually remove a couple of older kernels!
In future, if you run autoremove, then I would answer N to the proceed question and run
sudo apt-get purge list-of-packages,
where you only remove packages that look safe to remove.
The line that said
Why not try reinstalling grub as it suggests?
(Actually sudo update-grub, followed by a reboot) might be sufficient
This should recreate the links to boot from your existing kernels.
If it doesn't work, you could still use your present method to boot the machine.
In fact, why did you run auto-remove at all?
Personally, if I'd seen that, I would check & possibly manually remove a couple of older kernels!
In future, if you run autoremove, then I would answer N to the proceed question and run
sudo apt-get purge list-of-packages,
where you only remove packages that look safe to remove.
The line that said
should have been an extra alert.
Quote
Why not try reinstalling grub as it suggests?
(Actually sudo update-grub, followed by a reboot) might be sufficient
This should recreate the links to boot from your existing kernels.
If it doesn't work, you could still use your present method to boot the machine.
I removed 83 because it was corrupted when the computer froze and I had to hit the power button mid upgrade. After which I was stuck at the grub menu command line, I don't really know a lot about grub commands so tried chroot from the livecd, mounted my file system and tried updating from there. It suggested 83 wasn't configured and to auto remove which I did. After the reboot I could get back in to a working system with kernel 79.
I was hoping now the offending kernel was removed I could simply go back through the update process and get back to the latest but no update is available. Didn't want to delete any earlier kernels in case I couldn't get back to a working machine. I'm sure I've been here before as well
I was hoping now the offending kernel was removed I could simply go back through the update process and get back to the latest but no update is available. Didn't want to delete any earlier kernels in case I couldn't get back to a working machine. I'm sure I've been here before as well
So its working now?
The new kernel should be sitting in the repositories.
You could try running a copy of your OS in a VM & try to break it...
The new kernel should be sitting in the repositories.
You could try running a copy of your OS in a VM & try to break it...
Quote So its working now?
The new kernel should be sitting in the repositories.
Yeah back working. So it's ok to download again from say synaptic even though its not showing in any updates? I read somewhere before that doing it that way manually rather than the update process can lock you at that version.
Quote You could try running a copy of your OS in a VM & try to break it...
I've broke enough today thanks, ever had one of them days? Today was mine.
Still running on 79
83 not showing as an option to upgrade or in the grub list.
In Synaptic showing has installed, tried mark for re-installation which it goes through the procedure. Reboot and still on 79. Do you think I should mark it for complete removal then check for updates again?
uname -r
3.13.0-79-generic
neil@neil-Excel:~$ sudo update-grub
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-3.13.0-79-generic
Found initrd image: /boot/initrd.img-3.13.0-79-generic
Found linux image: /boot/vmlinuz-3.13.0-77-generic
Found initrd image: /boot/initrd.img-3.13.0-77-generic
Found linux image: /boot/vmlinuz-3.13.0-76-generic
Found initrd image: /boot/initrd.img-3.13.0-76-generic
Found linux image: /boot/vmlinuz-3.13.0-74-generic
Found initrd image: /boot/initrd.img-3.13.0-74-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
neil@neil-Excel:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
83 not showing as an option to upgrade or in the grub list.
In Synaptic showing has installed, tried mark for re-installation which it goes through the procedure. Reboot and still on 79. Do you think I should mark it for complete removal then check for updates again?
It's ok,
did the trick. Can't believe I managed to rescue this system from a freeze during kernel installation. There's hope for me yet
sudo apt-get install linux-generic
did the trick. Can't believe I managed to rescue this system from a freeze during kernel installation. There's hope for me yet
Regarding your comment about pinning your kernel?
Haven't a clue about pinning...
But I've never pinned a package in my life - I once messed up a kernel trying to install some video drivers,
so I just ran on a slightly older kernel for a few months.
Eventually, a new kernel came along & it installed perfectly.
Haven't a clue about pinning...
But I've never pinned a package in my life - I once messed up a kernel trying to install some video drivers,
so I just ran on a slightly older kernel for a few months.
Eventually, a new kernel came along & it installed perfectly.
Quote Regarding your comment about pinning your kernel?
Haven't a clue about pinning...
Not sure what you mean, did I mention pinning? I guess maybe the next update that came out with an updated kernel it maybe would have offered it up. Wasn't sure if it needed to be incremental or not.
Quote from: AverageWhiteBloke
When I saw that I looked and couldn't find where you had mentioned pinning !
I can only assume pinning refers to the ability to force Linux packages to be a particular version, and therefore prevent updates from changing them.
I have used that functionality in the past, when the old BBC iPlayer needed a specific out-of-date version of Adobe-Air, so I used "synaptic" to force a particular version so I didn't accidentally break it when running updates.
Sounds like a case of let sleeping dogs lie.