Comment 66 for bug 798414
Revision history for this message
| Guillermo (casalguillermo) wrote RE: [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space | #66 |
Thank you. Also i founded this alternative solution:
https:/
> Date: Wed, 9 Sep 2015 10:24:00 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: Re: [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
>
> Thank you.
>
> 2015-08-15 7:35 GMT+02:00 David Gerstmann <email address hidden>:
>
> > Hello Alan Burgess, my name is David. The easiest way that I have found to
> > deal with this problem is to go into your Terminal and type in the
> > following in this order (I'll try to be as specific as possible).
> > sudo apt-get autoclean (that's exactly how it should look, then press
> > enter), next...
> > sudo apt-get autoremove (then enter), again...
> > sudo apt-get clean (enter)
> >
> > Do this every time before you attempt to update your computer. It may be a
> > bit of a pain, but it'll get you to where you need to be until someone
> > comes up with a permanent fix or another long term supported version comes
> > out again. Try this and let me know how it works for you. Good luck.
> > P.S., if you don't know what the terminal is, go into your dash and
> > simply type in the search window... "terminal", and that should come up
> > with what's known as the terminal emulator. Click on it and follow the
> > above instructions.
> >
> > On Wed, Aug 12, 2015 at 1:35 PM, Alan Burgess <email address hidden>
> > wrote:
> >
> > > Hello Casaba,
> > >
> > > Could you provide detailed instructions on how to resolve this issue
> > > please.
> > >
> > > Also when will this bug be resolved?
> > >
> > > Thanks
> > >
> > > Alan
> > >
> > >
> > >
> > > On 12/08/15 12:10, Csaba wrote:
> > > > ** Project changed: null-and-void => ubuntu
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to the bug
> > > report.
> > > https:/
> > >
> > > Title:
> > > update-initramfs should produce a more helpful error when there isn't
> > > enough free space
> > >
> > > Status in initramfs-tools:
> > > Confirmed
> > > Status in Ubuntu:
> > > Fix Released
> > > Status in initramfs-tools package in Ubuntu:
> > > Confirmed
> > >
> > > Bug description:
> > > Binary package hint: initramfs-tools
> > >
> > > When generating a new initramfs there is no check for available free
> > > space, subsequently its possible for update-initramfs to fail due to a
> > > lack of free space. This is resulting in package installation
> > > failures for initramfs-tools. For example:
> > >
> > > Setting up initramfs-tools (0.98.8ubuntu3) ...
> > > update-initramfs: deferring update (trigger activated)
> > > Processing triggers for initramfs-tools ...
> > > update-initramfs: Generating /boot/initrd.
> > >
> > > gzip: stdout: No space left on device
> > > E: mkinitramfs failure cpio 141 gzip 1
> > > update-initramfs: failed for /boot/initrd.
> > > dpkg: error processing initramfs-tools (--configure):
> > > subprocess installed post-installation script returned error exit
> > > status 1
> > >
> > > WORKAROUND:
> > >
> > > Remove unused kernels using computer janitor or manually free space on
> > > your partition containing the /boot file system.
> > >
> > > To manage notifications about this bug go to:
> > > https:/
> > >
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https:/
> >
> > Title:
> > update-initramfs should produce a more helpful error when there isn't
> > enough free space
> >
> > Status in initramfs-tools:
> > Confirmed
> > Status in Ubuntu:
> > Fix Released
> > Status in initramfs-tools package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > Binary package hint: initramfs-tools
> >
> > When generating a new initramfs there is no check for available free
> > space, subsequently its possible for update-initramfs to fail due to a
> > lack of free space. This is resulting in package installation
> > failures for initramfs-tools. For example:
> >
> > Setting up initramfs-tools (0.98.8ubuntu3) ...
> > update-initramfs: deferring update (trigger activated)
> > Processing triggers for initramfs-tools ...
> > update-initramfs: Generating /boot/initrd.
> >
> > gzip: stdout: No space left on device
> > E: mkinitramfs failure cpio 141 gzip 1
> > update-initramfs: failed for /boot/initrd.
> > dpkg: error processing initramfs-tools (--configure):
> > subprocess installed post-installation script returned error exit
> > status 1
> >
> > WORKAROUND:
> >
> > Remove unused kernels using computer janitor or manually free space on
> > your partition containing the /boot file system.
> >
> > To manage notifications about this bug go to:
> > https:/
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> update-initramfs should produce a more helpful error when there isn't
> enough free space
>
> Status in initramfs-tools:
> Confirmed
> Status in Ubuntu:
> Fix Released
> Status in initramfs-tools package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: initramfs-tools
>
> When generating a new initramfs there is no check for available free
> space, subsequently its possible for update-initramfs to fail due to a
> lack of free space. This is resulting in package installation
> failures for initramfs-tools. For example:
>
> Setting up initramfs-tools (0.98.8ubuntu3) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.
>
> gzip: stdout: No space left on device
> E: mkinitramfs failure cpio 141 gzip 1
> update-initramfs: failed for /boot/initrd.
> dpkg: error processing initramfs-tools (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> WORKAROUND:
>
> Remove unused kernels using computer janitor or manually free space on
> your partition containing the /boot file system.
>
> To manage notifications about this bug go to:
> https:/