cancel
Showing results for 
Search instead for 
Did you mean: 

Smashed my system again

Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Smashed my system again

Just wondering if this means anything?
Quote
neil@neil-Excel:~$ sudo apt-get autoremove
[sudo] password for neil:
Reading package lists... Done
Building dependency tree     
Reading state information... Done
The following packages will be REMOVED
  linux-image-3.13.0-83-generic linux-image-extra-3.13.0-83-generic
0 to upgrade, 0 to newly install, 2 to remove and 0 not to upgrade.
2 not fully installed or removed.
After this operation, 147 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 325530 files and directories currently installed.)
Removing linux-image-extra-3.13.0-83-generic (3.13.0-83.127) ...
depmod: FATAL: could not load /boot/System.map-3.13.0-83-generic: No such file or directory
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-83-generic
grep: /boot/config-3.13.0-83-generic: No such file or directory
depmod: WARNING: could not open /tmp/mkinitramfs_2OYGV7/lib/modules/3.13.0-83-generic/modules.order: No such file or directory
depmod: WARNING: could not open /tmp/mkinitramfs_2OYGV7/lib/modules/3.13.0-83-generic/modules.builtin: No such file or directory
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
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
Removing linux-image-3.13.0-83-generic (3.13.0-83.127) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-83-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-83-generic /boot/vmlinuz-3.13.0-83-generic
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
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]
neil@neil-Excel:~$

Computer froze while updating and had a broken kernel. Managed to chroot with a live CD and boot into the previous kernel and this is the error I get. Daren’t reboot right now with it mentioning grub in case I can't back into a working system.
12 REPLIES
Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

Managed to get booted again after a bit of fixing. The broken kernel was. 83 which I removed but now when I check for updates it says none available and I'm still on .79 any reason for this?
VileReynard
Seasoned Pro
Posts: 10,649
Thanks: 206
Fixes: 9
Registered: 01-09-2007

Re: 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
Quote
2 not fully installed or removed.
should have been an extra alert.  Cool
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.

Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

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  Grin
VileReynard
Seasoned Pro
Posts: 10,649
Thanks: 206
Fixes: 9
Registered: 01-09-2007

Re: Smashed my system again

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...

Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

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...

Grin I've broke enough today thanks, ever had one of them days? Today was mine.
Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

Still running on 79
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?
Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

It's ok,
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  Grin
VileReynard
Seasoned Pro
Posts: 10,649
Thanks: 206
Fixes: 9
Registered: 01-09-2007

Re: Smashed my system again

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.

Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

Quote
Regarding your comment about pinning your kernel?
Haven't a clue about pinning...

Huh 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.
Community Veteran
Posts: 5,472
Thanks: 288
Fixes: 4
Registered: 11-08-2007

Re: Smashed my system again

Quote from: AverageWhiteBloke
Huh Not sure what you mean, did I mention pinning?

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.
Community Veteran
Posts: 1,122
Thanks: 6
Registered: 28-08-2007

Re: Smashed my system again

Reading Back through the posts I think it was a reference to...
Quote
I read somewhere before that doing it that way manually rather than the update process can lock you at that version.

I read somewhere when looking for answers to this problem that if you load a kernel from anywhere other the updates it will lock you at that kernel. I think it was more to do with unreleased kernels though which I guess you would have to force the installation and possibly locking it.
All good though things are working again regardless.
VileReynard
Seasoned Pro
Posts: 10,649
Thanks: 206
Fixes: 9
Registered: 01-09-2007

Re: Smashed my system again

Sounds like a case of let sleeping dogs lie.