Ubiquity creates space for enough kernels. The system is not managing
that space later. Not ubiquity's fault.
These two issues together create the problem on a small /boot partition:
apt: apt-get remove/purge/autoremove is blocked by the (always-failing) kernel
install (not enough space on device
apt-get remove/purge/autoremove is blocked by the (always-failing)
kernel install (not enough space on device)
** Package changed: ubiquity (Ubuntu) => apt (Ubuntu)
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification b
Firstly, me too, this is super annoying. As a rule of thumb any
'feature' that *requires* the user to drop to CLI to put in regular
manual commands *to keep the system secure and updated* ... in a desktop
/ consumer OS... is a bug.
It seems there are separate issues here that could be addressed
se
same here, Ubuntu 15.04 64 bit, encrypted [as opposed to the LVM].
Installed about 2015/09/15, and the Update Manager refuses installing already
the very first update to the Kernel package(s), i.e., from 3.19.0.28.27
to 3.19.0.30.29.
·
·
·
[I know it's off-topic here, but is there any way ro
Someone give me the advise to use the LVM option on a fresh Xubuntu
15.04 install so i did. Use one internal drive, a 256GB SSD and a 2TB
network drive (small NAS) for external storage. Hope there will be a fix
to autoremove those old kernels from /boot partitions before upgrading a
new one.
--
Y
I have this problem but removing old kernels was only partly successful,
probably because I used rm and not apt-get method. In fact, if you have
a laptop, why use LVM at all? You are scarcely going to wander around
with an external hard disk attached to it for the extension to a logical
volume.
Th
This bug comes up again and again on Askubuntu:
http://askubuntu.com/questions/171209/my-boot-partition-hit-100-and-now-i-cant-upgrade-cant-remove-old-kernels-to
http://askubuntu.com/questions/345588/what-is-the-safest-way-to-clean-up-boot-partition
http://askubuntu.com/questions/89710/how-do-i-fr
Trying this on a Dell Inspiron 15 7547 running 100% Ubuntu (No dual
booting). We're unable to upgrade from Ubuntu 14.10 to 15.04 due to this
error. We've tried
>sudo apt-get clean
>sudo apt-get autoremove
and nothing has worked. We don't want to get left behind on software
updates, so fixing the
Same problem as indicated above on 14.04 LTS. Why are "old" kernels left
on a drive that is too small to begin with? Thank you in advance for
fixing it. If fix would allow to expand partition (at least double it)
and remove "old" kernels, this would be great!
--
You received this bug notification
Increasing the boot partition does not solve the underlying problem of
old kernels. Is the size large enough now to accommodate enough
kernels? If it is, we should tackle the real problem of removing old
kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This bug is tedious. /boot holds only 3 kernels for me and it seems
there is a new kernel every couple of weeks. So, each time, I need to go
and delete the previous 1-2 manually. Why do I have to babysit my
machine? Lucky I do not want to do unattended upgrades.
Resizing /boot with LVM requires mu
Added my +1 as it affects me to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
LVM or Encrypted install creates too small /boot partition
To manage notifications about this bug go to
Same problem here for some months now on 14.04 Studio. Autoremove and
bleachbit don't deal with it. Manual cleanup around the November
timeframe last year got me to the March cycle of updates before /boot
was overloaded again. Problem appears to me to be centered on the fact
the old ver. are not
boot partition fills up with updates of kernel.
autoremove does not remove previous kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
LVM or Encrypted install creates too small /
Correction.
APT::AutoRemove::RecommendsImportant and APT::AutoRemove::SuggestsImportant are
only used by aptitude. apt-get just recycles the values of
APT::Install-Recommends and APT::Install-Suggests when deciding which packages
should be autoremoved. apt-get's behaviour is also affected by an
Link to yet another forum thread:
http://ubuntuforums.org/showthread.php?t=2256479
The problem is twofold.
1) Users not paying attention to apt-get saying:
The following packages were automatically installed and are no longer required:
...
Use 'apt-get autoremove' to remove them.
like in the t
** Changed in: ubiquity (Ubuntu)
Assignee: Donald Tripp (dtlongrifles) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
LVM or Encrypted install creates too small /b
I have this problem with Xubuntu 14.04
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Donald Tripp (dtlongrifles)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093
Title:
LVM o
Especially a problem when setting up systems for clients, who you only
visit once or twice a year. The kernel updates fill the boot partition
fast and so users are warned at the start that no space is left.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
The issue here isn't so much the absolute space initially allocated to
the /boot/ LV, it is that the installer allocates 100% of the Volume
Groups space.
The great advantage of LVM is that space can by dynamically allocated
and removed from Logical Volumes as needed.
If the installer were to leav
Just dealt with the problem of an affected user here :
http://ubuntuforums.org/showthread.php?t=2240240
But I guess adding myself to the "Affects Me" list would be cheating?
Since it is not me who is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
21 matches
Mail list logo