[SOLVED] Backbox 4.1 > 4.2 update support

Started by wafflez, May 09, 2015, 10:44:15 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions

wafflez

May 09, 2015, 10:44:15 PM Last Edit: January 18, 2016, 09:28:49 PM by ZEROF
Hey,

I fucked up updating backbox 4.1 I get this when trying to upgrade.

Code Select

penis@volcano:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
 linux-image-3.13.0-51-generic
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]



Then,

Code Select

Do you want to continue? [Y/n] y
Setting up linux-image-3.16.0-37-generic (3.16.0-37.51~14.04.1) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(3.16.0-37.49~14.04.1 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(3.16.0-37.49~14.04.1 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-37-generic /boot/vmlinuz-3.16.0-37-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-37-generic /boot/vmlinuz-3.16.0-37-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.16.0-37-generic /boot/vmlinuz-3.16.0-37-generic
update-initramfs: Generating /boot/initrd.img-3.16.0-37-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.16.0-37-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.0-37-generic.postinst line 1025.
dpkg: error processing package linux-image-3.16.0-37-generic (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-extra-3.16.0-37-generic:
linux-image-extra-3.16.0-37-generic depends on linux-image-3.16.0-37-generic; however:
 Package linux-image-3.16.0-37-generic is not configured yet.

dpkg: error processing package linux-image-extra-3.16.0-37-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic-lts-utopic:
linux-image-generic-lts-utopic depends on linux-image-3.16.0-37-generic; however:
 Package linux-image-3.16.0-37-generic is not configured yet.
linux-image-generic-lts-utopic depends on linux-image-extra-3.16.0-37-generic; however:
 Package linux-image-extra-3.16.0-37-generic is not configured yet.

dpkg: error processing package linux-image-generic-lts-utopic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-signed-image-3.16.0-37-generic:
linux-signed-image-3.16.0-37-generic dependsNo apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                                                                      No apport report written because the error message indicates its a followup error from a previous failure.
                                                                            No apport report written because MaxReports is reached already
                                                                                                                                          No apport report written because MaxReports is reached already
                     on linux-image-3.16.0-37-generic (= 3.16.0-37.51~14.04.1); however:
 Package linux-image-3.16.0-37-generic is not configured yet.
linux-signed-image-3.16.0-37-generic depends on linux-image-extra-3.16.0-37-generic (= 3.16.0-37.51~14.04.1); however:
 Package linux-image-extra-3.16.0-37-generic is not configured yet.

dpkg: error processing package linux-signed-image-3.16.0-37-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-signed-image-generic-lts-utopic:
linux-signed-image-generic-lts-utopic depends on linux-signed-image-3.16.0-37-generic; however:
 Package linux-signed-image-3.16.0-37-generic is not configured yet.

dpkg: error processing package linux-signed-image-generic-lts-utopic (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-3.16.0-37-generic
linux-image-extra-3.16.0-37-generic
linux-image-generic-lts-utopic
linux-signed-image-3.16.0-37-generic
linux-signed-image-generic-lts-utopic
Updating BackBox console menu ...
E: Sub-process /usr/bin/dpkg returned an error code (1)


Any suggestions?

ZEROF

#1
May 10, 2015, 09:34:01 AM
You have a separate partition for /boot that is only around xxxMB in size. This partition is full.

The reason Backbox has given you a separate parition for /boot seems to be that you are using LVM and/or "full" disk encryption on the rest of the drive.

The /boot directory contains all of your kernel images, so the likely cause of this issue is that you have too many previous kernels installed. Ubuntu issues kernel updates which bump the version number in the package name fairly frequently even for long term stable versions, so over time if you keep the system up to date, the /boot directory will grow. You need to remove some of your older installed kernels.

Don't ask, read : http://wiki.backbox.org
or just run sudo rm -rf /*

wafflez

#2
May 10, 2015, 05:20:12 PM
Quote from: ZEROF on May 10, 2015, 09:34:01 AM
You have a separate partition for /boot that is only around xxxMB in size. This partition is full.

The reason Backbox has given you a separate parition for /boot seems to be that you are using LVM and/or "full" disk encryption on the rest of the drive.

The /boot directory contains all of your kernel images, so the likely cause of this issue is that you have too many previous kernels installed. Ubuntu issues kernel updates which bump the version number in the package name fairly frequently even for long term stable versions, so over time if you keep the system up to date, the /boot directory will grow. You need to remove some of your older installed kernels.

Thanks and ya I have LVM, so removed linux-image-3.13 and what not but now when I reboot I only have a black screen. I just enterd my password and after a while the login screen appeared. Any suggestions?

weVeg

#3
May 10, 2015, 05:21:10 PM Last Edit: May 10, 2015, 05:22:52 PM by weVeg
Hi wafflex,
look, your error report said that:
Quote
gzip: stdout: No space left on device

there are also dependency problems, often
Code Select

sudo apt-get -f install

is enough to resolve that kind of problems!
Bye!
una voce libera è sempre liberatrice
under_r00t

wafflez

#4
May 10, 2015, 05:29:43 PM
Quote from: weVeg on May 10, 2015, 05:21:10 PM
Hi wafflex,
look, your error report said that:
Quote
gzip: stdout: No space left on device

there are also dependency problems, often
Code Select

sudo apt-get -f install

is enough to resolve that kind of problems!
Bye!


Hey,

I don't have any dependency problems, but for some reason my old kernels still appear even though I removed them and rebooted.

Code Select

penis@volcano:~$ dpkg -l | grep linux-image-
rc  linux-image-3.13.0-44-generic             3.13.0-44.73                           amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-3.13.0-45-generic             3.13.0-45.74                           amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-3.13.0-46-generic             3.13.0-46.79                           amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-3.13.0-48-generic             3.13.0-48.80                           amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-3.13.0-52-generic             3.13.0-52.86                           amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.16.0-36-generic             3.16.0-36.48~14.04.1                   amd64        Linux kernel image for version 3.16.0 on 64 bit x86 SMP
ii  linux-image-3.16.0-37-generic             3.16.0-37.51~14.04.1                   amd64        Linux kernel image for version 3.16.0 on 64 bit x86 SMP
rc  linux-image-3.18.5-031805-generic         3.18.5-031805.201501292218             amd64        Linux kernel image for version 3.18.5 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-44-generic       3.13.0-44.73                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-45-generic       3.13.0-45.74                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-46-generic       3.13.0-46.79                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-48-generic       3.13.0-48.80                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-51-generic       3.13.0-51.84                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.13.0-52-generic       3.13.0-52.86                           amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
rc  linux-image-extra-3.16.0-36-generic       3.16.0-36.48~14.04.1                   amd64        Linux kernel extra modules for version 3.16.0 on 64 bit x86 SMP
ii  linux-image-extra-3.16.0-37-generic       3.16.0-37.51~14.04.1                   amd64        Linux kernel extra modules for version 3.16.0 on 64 bit x86 SM


Also off topic question but recently I been hearing this loud noise that builds up then just stops after a couple seconds from my hard drive I think. Is it going to die soon?

weVeg

#5
May 10, 2015, 07:47:56 PM
In Your first post you show:
Quote
dpkg: dependency problems prevent configuration of linux-image-extra-3.16.0-37-generic:
and there are a lot of similar stuff...
btw, keep your system up to date, could be that your problems will be fixed by himself, if not boot your OS with a working kernel version.
bye!
una voce libera è sempre liberatrice
under_r00t

ZEROF

#6
May 10, 2015, 10:34:40 PM Last Edit: May 10, 2015, 10:37:18 PM by ZEROF
wafflez i have same issue on one of my laptops but for now i can select kernel version i want to use, when my laptop boot. sudo apt-get -f install will not help at all.

Mistake was running upgrade before removing few of old kernels, as we didn't do that, our /boot partition don't have any free space. I didn't try to extend (resize) /boot partition to get more space, but i guess that is only solution.

Don't ask, read : http://wiki.backbox.org
or just run sudo rm -rf /*

ZEROF

#7
May 28, 2015, 09:10:11 PM
Solution is:

export KERNEL="$(uname -r | grep -Po '([0-9\.\-]*[0-9])?')"; dpkg --get-selections | grep -E "linux-(header|image).*" | grep -iw install | sort | grep -v "$KERNEL" | grep -v "lts" | sed 's/install//g' | xargs dpkg -P

Then:

apt-get -f install
apt-get update
apt-get upgrade -y

After some time, i got it :)

Don't ask, read : http://wiki.backbox.org
or just run sudo rm -rf /*
Print
Go Up Pages1
User actions