Latest (k)ubuntu installer checks for free space on /boot and aborts the
upgrade if there isn't enough space -- thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173468
Title:
release upgrade d
The same problem appears to have occurred during the upgrade from
3.8.0-19 to 3.8.0-21. In other words, this bug appears to be of broader
scope than just the release upgrade.
I worked around the problem by deleting the abi, initrd.img and
System.map files for 3.8.0-19. I did so with much trepidati
This bug was fixed in the package ubuntu-release-upgrader - 1:0.195
---
ubuntu-release-upgrader (1:0.195) saucy; urgency=low
[ Dustin Kirkland ]
* debian/release-upgrade-motd: LP: #1173209
- recheck release upgrade once-a-day, even if stamp file is
already populated
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173468
Title:
release upgrade doesn't properly calculate free space needed for /boot
To manage notificati
When update-initramfs is ran a backup of the initrd for the kernel being
installed is made, while the new one is being generated. Hence, the
need for additional free space.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
>From what I can tell it looks like update-initramfs is run two times,
once by linux-image-3.8.0-19-generic and a second time by linux-image-
extra-3.8.0-19-generic.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you
Running through this process myself I discovered the following in my
boot partition at the time of the failure:
16M initrd.img-3.8.0-19-generic
16M initrd.img-3.8.0-19-generic.dpkg-bak
0M initrd.img-3.8.0-19-generic.new
So it seems that the new kernel image is getting created multiple times
du
