Fixed in update manager 1:0.63. Marking as fix released.
** Changed in: update-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notificati
I'm not sure to follow the discussion currently but there is clearly and
obviously a bug. The error should be correct and let the user knows what
actually happen. The worst case I had was a message asking me to free
115MB. After having removed two old kernels, the error was finally gone.
That bein
Ok, here is the link to the first feature suggested:
https://blueprints.launchpad.net/ubuntu/+spec/ubuntu-installer
I haven't found where to request for the second one. However, since, as
I assume, people responsible for update-manager are subscribed to this
bug, they were already notified of it.
Groover,
I definitely agree. Will you please link us to the feature request that
you file?
Thanks,
-Ryan
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member of Ubu
-Begin Error message---
Not enough free disk space
The upgrade aborts now. The upgrade needs a total of 41.9M free space on disk
'/boot'. Please free at least an additional 18.8M of disk space on '/boot'.
Empty your trash and remove temporary packages of former installations using
'sudo
Just to update everyone, deleting the kernel packages using apt-get
allowed the update manager to run with no hitches.
I have a few ideas/suggestions to help avoid more bug reports on this
in the future:
1) The text in the 'not enough free space' dialog box could be amended
to include a note abou
ahhhduh. I incorrectly assumed it was calculating the space by
looking at the images on disk. Boy do I feel dumb now. Thanks for
the help!
Cheers,
-Ryan
On 8/28/07, Michael Vogt <[EMAIL PROTECTED]> wrote:
> @ryanmbruce: Thanks for the logs! It looks like you removed the images
> from the f
@ryanmbruce: Thanks for the logs! It looks like you removed the images
from the filesystem, but not the kernel packages. Please use synaptic to
remove the no longer used kernels (make sure to keep the one you are
currently using :)
2007-08-26 22:56:14,237 DEBUG linux-image-2.6.17-10-386 (upgrade|i
** Attachment added: "main.log"
http://launchpadlibrarian.net/9013186/main.log
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
[EMAIL PROTECTED]:~$ cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/mapper/Ubuntu-root / reiserfs rw,noatime 0 0
/dev/mapper/Ubuntu-root /dev/.static/dev reiserfs rw 0 0
tmpfs /var/run tmpfs r
On 8/26/07, ryanmbruce <[EMAIL PROTECTED]> wrote:
> I'm really stuck right now because I can't resize my boot partition, and
> I can't clean any more out of it. I absolutely cannot upgrade to Gutsy
> unless a workaround is found, or the space requirement is lowered. Any
> help would be appreciate
@ryanmbruce: please not that this looks like a seperate bug from the
original reported one, but I need the requested files to verify this.
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification
Thanks for your bugreport.
This looks like a bug in the parition detection code. Could you please
attach the file /var/log/dist-upgrade/main.log to this report? And also
the content of /proc/mounts?
Thanks,
Michael
--
[MASTER] /boot free space check message misleading and space requirement too
"I think what's using up so much space is that it rebuilds all
initrd.imgs it can find and backups the old ones and then adds
additional entries to your boot menu."
I think it may be doing more than this because I have cleaned out every
single image with the exception of the four I absolutely need
I always just assumed there was an old kernel clean-up because I set
the grub menu to only display 2 or 4 I didn't realize it kept ALL of
them until I cleaned out all but the last four. To me, it seems like
not cleaning those up is somewhat of a waste (both in processing power
when rebuilding, an
>315MB in addition to the 228 that is on there adds up to a rather large
boot partition.
I think what's using up so much space is that it rebuilds all
initrd.imgs it can find and backups the old ones and then adds
additional entries to your boot menu. I haven't looked at the code, it's
just what I
I would also suggest that we create a different bug for the required
repartition/large space requirement that is separate from the misleading
text(which has been fixed).
Cheers,
-Ryan
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/b
Just figured I'd add in my own experience with this bug on an upgrade to
Gutsy Tribe3, as I haven't seen anyone with quite as hefty of a space
requirement as what update-manager is asking of me. 315MB in addition
to the 228 that is on there adds up to a rather large boot partition.
I have two que
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Fix Committed
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
The bug is known and worked on. So please do not try to raise its
awarness by adding comments.
Cheers,
Sebastian
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member
Importance is NOT low, because
- it makes upgrading impossible for many users,
- it wastes a lot of valuable work time.
Best regards
Gerald
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notificatio
The installer could use /tmp for the extra stuff, or anywhere else,
since it's running with root privileges.
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member of Ub
> When it complains about not enough space in /boot and that it needs X
> bytes more... it lies. So this adds to the confusion.
I'm not so sure about this anymore. During the upgrade Ubuntu creates new
initrd images for every installed kernel including backups and temporarily uses
(at least on my
On Mon, 2007-05-07 at 23:50 +, Simon Ruggier wrote:
> JamesRichardson: is there something preventing you from using the
> FeistyUpgradesManual page to upgrade your system?
>
> If so, you might also try setting up your system to use your root
> partition to store /boot in. This involves runnin
JamesRichardson: is there something preventing you from using the
FeistyUpgradesManual page to upgrade your system?
If so, you might also try setting up your system to use your root
partition to store /boot in. This involves running:
# cp -a /boot /tmp/boot.backup
# umount /boot
# cp -a /tmp/boo
Please raise importance of this bug, totally unable to upgrade without
repartitioning, as used ext2 & raw partition for /boot. maybe this was wrong,
but there it is just now...
[EMAIL PROTECTED]:/boot/grub# df -h .
FilesystemSize Used Avail Use% Mounted on
/dev/sda1 37M
I used https://help.ubuntu.com/community/FeistyUpgradesManual to
upgrade, everything was OK.
--
[MASTER] /boot free space check message misleading and space requirement too big
https://bugs.launchpad.net/bugs/104337
You received this bug notification because you are a member of Ubuntu
Bugs, which
If this is the Master thread regarding "space requirement too big"
could you please raise the importance?
Reason: this problem may absolutely prohibit the upgrade to feisty.
In some scenarios resizing partitions may be a (risky)
workaround to satisfy the overly conservative space requirement,
but
28 matches
Mail list logo
