Announcement

**vinnywright** · Dec 01, 2013, 01:13 PM

run

Code:

uname -a

see what kernel your running ,,,,,,purge all but the one you are running and 1 under it . (so if your running 3.2.0-44 keep it and 3.2.0-41) purge all the rest ,,the vmlinuz-x.x.x-x and the initrd.img-x.x.x-x

why the separation to different partitions of ,/tmp,/boot,/usr,/home and /opt ?

VINNY

**ph4ntom74** · Dec 01, 2013, 02:51 PM

Thanks for the tip vinny but its a no go. I purged all but the 3.2.0-44 and 3.2.0-41 along with the mvlinuz and initrd.img as you suggested. didn't work.

Code:

m@dalila:~$ sudo apt-get -f install 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  initramfs-tools libpython2.7 linux-generic linux-headers-generic linux-image-3.2.0-56-generic linux-image-generic python2.7
Suggested packages:
  fdutils linux-doc-3.2.0 linux-source-3.2.0 linux-tools python2.7-doc
The following NEW packages will be installed:
  linux-image-3.2.0-56-generic
The following packages will be upgraded:
  initramfs-tools libpython2.7 linux-generic linux-headers-generic linux-image-generic python2.7
6 upgraded, 1 newly installed, 0 to remove and 242 not upgraded.
25 not fully installed or removed.
Need to get 0 B/42.5 MB of archives.
After this operation, 150 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 552828 files and directories currently installed.)
Unpacking linux-image-3.2.0-56-generic (from .../linux-image-3.2.0-56-generic_3.2.0-56.86_amd64.deb) ...
Done.
Setting up libglib2.0-data (2.32.4-0ubuntu1) ...
Setting up libglib2.0-bin (2.32.4-0ubuntu1) ...
dpkg: dependency problems prevent configuration of python2.7:
 python2.7 depends on python2.7-minimal (= 2.7.3-0ubuntu3.2); however:
  Version of python2.7-minimal on system is 2.7.3-0ubuntu3.4.
dpkg: error processing python2.7 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          dpkg: dependency problems prevent configuration of libpython2.7:
 libpython2.7 depends on python2.7 (= 2.7.3-0ubuntu3.2); however:
  Package python2.7 is not configured yet.
dpkg: error processing libpython2.7 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python:
 python depends on python2.7 (>= 2.7.3); however:
  Package python2.7 is not configured yet.
dpkg: error processing python (--configure):
 dependency problems - leaving unconfigured
Setting up initramfs-tools-bin (0.99ubuntu13.4) ...
No 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.
                                                                               Setting up procps (1:3.2.8-11ubuntu6.3) ...
procps stop/waiting
dpkg: dependency problems prevent configuration of initramfs-tools:
 initramfs-tools depends on initramfs-tools-bin (<< 0.99ubuntu13.1.1~); however:
  Version of initramfs-tools-bin on system is 0.99ubuntu13.4.
dpkg: error processing initramfs-tools (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of udev:
 udev depends on initramfs-tools (>= 0.92bubuntu63); however:
  Package initramfs-tools is not configured yet.
dpkg: error processing udev (--configure):
 dependency problems - leaving unconfigured
Setting up libc-dev-bin (2.15-0ubuntu10.5) ...
No apport report written because MaxReports is reached already
                                                              Setting up linux-libc-dev (3.2.0-56.86) ...
Setting up libc6-dev (2.15-0ubuntu10.5) ...
Setting up libc6-i386 (2.15-0ubuntu10.5) ...
Setting up libglib2.0-dev (2.32.4-0ubuntu1) ...
Setting up linux-firmware (1.79.7) ...
dpkg: dependency problems prevent configuration of linux-image-3.2.0-56-generic:
 linux-image-3.2.0-56-generic depends on initramfs-tools (>= 0.36ubuntu6); however:
  Package initramfs-tools is not configured yet.
dpkg: error processing linux-image-3.2.0-56-generic (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-3.2.0-45-generic; however:
  Package linux-image-3.2.0-45-generic is not installed.
dpkg: error processing linux-image-generic (--configure):
 dependency problems - leaving unconfigured
Setting up linux-headers-3.2.0-56 (3.2.0-56.86) ...
No apport report written because MaxReports is reached already
                                                              Setting up linux-headers-3.2.0-56-generic (3.2.0-56.86) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-56-generic /boot/vmlinuz-3.2.0-56-generic
Setting up linux-headers-generic (3.2.0.48.58) ...
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 3.2.0.45.54); however:
  Package linux-image-generic is not configured yet.
 linux-generic depends on linux-headers-generic (= 3.2.0.45.54); however:
  Version of linux-headers-generic on system is 3.2.0.48.58.
dpkg: error processing linux-generic (--configure):
 dependency problems - leaving unconfigured
Setting up linux-headers-3.2.0-49 (3.2.0-49.75) ...
No apport report written because MaxReports is reached already
                                                              Setting up linux-headers-3.2.0-49-generic (3.2.0-49.75) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-49-generic /boot/vmlinuz-3.2.0-49-generic
Setting up linux-headers-3.2.0-51 (3.2.0-51.77) ...
Setting up linux-headers-3.2.0-51-generic (3.2.0-51.77) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-51-generic /boot/vmlinuz-3.2.0-51-generic
Setting up tzdata-java (2013g-0ubuntu0.12.04) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 python2.7
 libpython2.7
 python
 initramfs-tools
 udev
 linux-image-3.2.0-56-generic
 linux-image-generic
 linux-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

Really never saw this anywhere, hope i wont have my system hangged. I think i have to make a fresh install.

ps: the partioning is for security purpose, plus i like to install some other apps that have nothing to do with the system in /opt, like gns3.

**vinnywright** · Dec 01, 2013, 04:19 PM

slow down ,,,their is still more to do.

first check your

Code:

df -h

output and see that you have space in boot once again

now you have unconfigured packages still from /boot filling up wile trying to do an upgrade ,,,run

Code:

sudo dpkg --configure -a

this will try to configure all the packages that did not get configured when the last attempt failed.

if it also will not finish do a

Code:

sudo dpkg-reconfigure -a

do this and report back any more errors or completion

VINNY

**ph4ntom74** · Dec 01, 2013, 04:49 PM

now it wont boot. i'm dual booting it with win7x64, after grub it just hangs there reading

Code:

* Stopping configure virtual network devices       [OK]

I'm scared because i kinda have a lot of stuff that i really need

it just sits there, i can try issuing those commands but im not sure in what run level he is.

NL

**oshunluvr** · Dec 02, 2013, 10:41 AM

#1: If you have stuff you really need, you should have a backup.
#2: Unless you re-formatted your file system, your stuff is still there so relax a bit.

First task is to figure out why it's not booting. Try booting into safe mode. If that fails, try booting to a live session via USB or CD. Then go to /var/log and read your system and boot logs to see where it's stuck.

I'm not sure what "security" you're accomplishing by having a separate /boot partition. AFAIK, the only reason to use a separate /boot is because you're using a file system grub can't boot to. Clearly, if you're going to use a non-standard partitioning scheme you need to be more on top of system maintenance. It's not very secure to leave your system unbootable.

**luckyone** · Dec 02, 2013, 02:52 PM

I'd suggest booting a LiveDisk/USB and getting your data to a safe place. IE: to DVD or another HDD

I'd agree there's very little security to be had using your setup.

**vinnywright** · Dec 02, 2013, 03:22 PM

sory I did not abandon you ,,,,,,just had to get back to work

so ya ,,,do like @ oshunluvr suggested and check safe mode and your logs ,,,,,,and if you can use a live cd/usb post the contents of your /boot partition as it is now.

VINNY

**Teunis** · Dec 02, 2013, 03:38 PM

Another way would be to run a Live CD/USB and use *parted to increase the size of /boot at the expense of the neighbouring partitions like /usr and /tmp.
Once upon a time I used to have a scheme similar to yours but then I realised it wastes precious disk space, the past ~10 years I'm very happy with just /, swap and /home.

**jglen490** · Dec 02, 2013, 07:56 PM

Agree with all the approaches above, especially booting to Live CD and saving what's important.

Root, home, a swap are all you need. Keep root and home separate, so that neither steps on the other. Keep home only for you and any other users you have, put everything else in root - further partitioning does nothing except put your system integrity at risk.

**Teunis** · Dec 03, 2013, 10:49 AM

Duh, I forgot the easiest way

Start up a live session, go to the /boot partition and delete a bunch of the kernels you aren't using anyway.
Now upgrade Grub and continue with life

As an example, I have two kernels in /boot and the total size is 73.1MiB, you have 388MB...

Announcement

Cannot update, upgrade, /boot partition is full, apt-get -f install, remove wont work

Cannot update, upgrade, /boot partition is full, apt-get -f install, remove wont work

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment