None of the affected versions reported here are supported versions; and
grub legacy upstream is also stopped, only receiving possible random
fixes locally
** Changed in: grub (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bu
I got my system unbootable after deleting some "old" kernels, then spent
about an hour recovering the system, debugging and trying to figure out
why update-grub is not doing what is saying it's doing.
I'm using latest Ubuntu, of course.
There should at least be an HUGE warning when one runs updat
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202009
Title:
update-grub not updating menu.lst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
I'm having same problem in Oneiric too and the strange fact is that the
Upgrade from Natty to Oneiric didn't upgrade my grub installation
keeping Grub legacy instead of Grub2. About last issue, i don't know if
this behaviour is correct or not.
--
You received this bug notification because you ar
Sorry, meant to say Oneiric, not Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202009
Title:
update-grub not updating menu.lst
To manage notifications about this bug go to:
https://bugs.laun
I am having this problem with grub legacy in Natty. I just realized that
despite update-manager downloading new versions of the kernel and
running update-grub with apparent success, that my menu options only go
as high as 3.0.0-12 when the latest installed version is 3.0.0-15.
--
You received thi
This should not be flagged medium - it's a serious bug in that the
kernel isn't upgraded without manual override. Please upgrade this to
major
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202009
Titl
as for the public, this is not a minor bug, having servers running old
kernels is a security issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202009
Title:
update-grub not updating menu.lst
To m
this still is a problem with lucid, some 18 months after its relese.
would it be a good idea to fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202009
Title:
update-grub not updating menu.ls
Hi just encountered a similar issue after upgrading to Natty.
The menu.lst was refusing to update (I believe I've still got grub installed
not grub2) with the 11.04 kernels.
I've just backed up my menu.lst and recreated it using update-grub and new
kernels appear to have been added correctly.
I'v
To comment #67: after boot another (old) Ubuntu from 2nd partition and
running update-grub2 under it, boot menu was fixed, but only until i
modify it again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
$ update-grub --version
grub-mkconfig (GRUB) 1.98+20100804-5ubuntu3
$ update-grub2 --version
grub-mkconfig (GRUB) 1.98+20100804-5ubuntu3
Both not work: properly listed items on terminal during updating, not shown in
boot menu after restart.
But when auto-update installs new kernel image, result i
WIth the Lucid release, there are installed both:
~$ ls /usr/sbin/update-grub*
/usr/sbin/update-grub /usr/sbin/update-grub2
Added lines in /etc/grub.d/40_custom are NOT incorporated into
/boot/grub/grub.cfg with usage of
$ sudo update-grub
However there is success if there is used
$ sudo upd
On upgrade to Lucid, grub2 was NOT installed for me; not sure if it
should have been.
Therefore, I am still experiencing this bug in Lucid. I resolved it by
backing up my menu.lst (renaming it to menu.lst.backup), and then
running update-grub. New menu.lst had correct entries. (If you copy
menu.ls
This isn't a patch that fixes the bug but a script that works around the
issue to get things working again. Unsubscribing reviewers.
** Tags removed: patch
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of U
To retain compatibility with 9.04 I've just moved the only external
function (grub_file_is_not_garbage) that was used in the script. Now it
should work with Jaunty and maybe other previous releases.
Artur, can you further detail the commands you issued and the output ?
Please also keep in mind tha
** Tags added: patch
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
After install new -image- package, update-grub2 doesn't run. Lucid.
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Bear in mind that this script has been tested on 9.10's with grub (not
grub2), when trying it on a 9.04:
.: 39: Can't open /usr/lib/grub/grub-mkconfig_lib
Another fix/workaround should be found then :-S
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received thi
I've been trying with other workstations/setups and I've added some
corrections on their particular case, as well as a warning regarding
"updatedefaultentry" and "savedefault" menu.lst options.
Please keep in mind that, according to menu.lst, changing the
"savedefault" setting could break dmraid-b
Hi people,
I've put together a little script that should be placed under:
/etc/grub.d
Since I'm pretty sure that there are plenty of corner cases, I encourage
you to try it and:
1) Report success/failure.
2) Send patches based on it !
You can run this by simply instantianting it:
sh /etc/grub
mike,
the issue you describe is unrelated to this bug report, and results from
your having installed the legacy 'grub' package, replacing the grub-pc
(grub2) package included Ubuntu 9.10. To resolve this, you should run
'sudo apt-get install grub-pc' to pull grub2 back in.
--
update-grub not up
I just took the latest kernel 2.6.31-17-generic and again had to apply the
hack I listed above.
update-grub continues to update the menu.lst rather than grub.cfg
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a memb
This moved me from being stuck at 2.6.31-14-generic to
2.6.31-16-generic, it allso filled in the menu for 15
sudo chmod 777 /boot/grub/grub.cfg
sudo grub-mkconfig > /boot/grub/grub.cfg
sudo chmod 444 /boot/grub/grub.cfg
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
I have also experienced this bug on both the HP G60-231WM & the Acer
Aspire 3690-2900 -- the fix is very simple... so simple you will think
"Why didn't I think of that???"
Ok so mouse doesn't work after upgrade to 9.10... then press
CNTRL/ALT/F1 to get yourself to the Command Line...
First login
It's still relevant because Grub2 is not installed automatically on
upgrade from Jaunty.
2009/10/29 parker :
> Ok It seems to me that this is irrelevant at this point as all new
> releases of Ubuntu will use grub2. It's a pain in the ass, but it is
> what is. "Make a change and call it progress" A
Ok It seems to me that this is irrelevant at this point as all new
releases of Ubuntu will use grub2. It's a pain in the ass, but it is
what is. "Make a change and call it progress" All I want a boot loader
to do is load the OS I want and the latest kernels and then leave me
alone. But the deve
2009/10/29 Steve Langasek :
> On Thu, Oct 29, 2009 at 08:44:57AM -, Przemysław Kulczycki wrote:
>> Same thing after upgrading from Jaunty to Karmic. Update-grub fails to
>> update menu.lst after I chose to keep my version of menu.lst during the
>> upgrade.
>
> If you chose to keep your version
On Thu, Oct 29, 2009 at 08:44:57AM -, Przemysław Kulczycki wrote:
> Same thing after upgrading from Jaunty to Karmic. Update-grub fails to
> update menu.lst after I chose to keep my version of menu.lst during the
> upgrade.
If you chose to keep your version of menu.lst, this is not a "failure"
When I had this problem using 'legacy grub' because I didn't accept
'install maintainer's version' I simply removed grub/menu.lst. When I
rebooted it created a new menu.lst with the updated kernels.
Now I'm using grub2 which presents a whole new set of problems.
Good luck,
Paco
Przemysław Kulc
I had to edit menu.lst by hand to fix it, yet I'm afraid that I'll have
to do it again after each kernel update.
** Tags added: grub jaunty karmic regression-release
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a m
** Attachment added: "menu.lst"
http://launchpadlibrarian.net/34590261/menu.lst
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
azr...@laptop:~$ sudo fdisk -l
[sudo] password for azrael:
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb452b452
Device Boot Start End Blocks Id System
/dev/sda1
** Attachment added: "fstab"
http://launchpadlibrarian.net/34590213/fstab
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Same thing after upgrading from Jaunty to Karmic. Update-grub fails to
update menu.lst after I chose to keep my version of menu.lst during the
upgrade.
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
This bug shows itself at my place if I make any modifications to the
automagic generated kernels. After a modification (for example removing
the kernel from the title) a subsequent "sudo update-grub" seems to
work, but fails to update the kernel list.
Parker's solution (#41) works, but it is also
Had this problem when I installed the latest kernel in Jaunty. At the
end of the install I accepted the default of keeping the existing Grub
menu. Big mistake. update-grub would not add the new kernel to the
menu.lst. Spent 2 days trying various solutions proposed in forums.
Finally found a simple
I don't disagree that this is serious, but unfortunately the old
update-grub is such a mess at this point that it's nearly certain that
any attempts to fix problems will make something else worse. We're
replacing the old update-grub system with grub2's entirely rewritten
version in karmic; I have s
Confirmed on jaunty.
This is a pretty serious problem. I just discovered that I haven't been
running the latest kernel since about four releases ago. I don't really
think it's fair to blame on the user for editing the wrong part of the
file too. On my system the automagic kernels section was so bi
I was also bitten by this when upgrading from 8.10 to 9.04. update-grub
said that it found the new kernel, but it did not change menu.lst.
The reason was that I had previously modified the 'automagically
generated' section of menu.lst (removing the 'splash' option to help
diagnose another issue),
+1 on upgrade from 8.10 to 9.04 not updating the menu.lst on amd-64 - worked
fine on my i386 upgrade
I manually changed the names for the images referred in the menu.lst
Now the Grub menu displays correctly and boots correct image.
Sudo update-grub did not write correct image names to menu.lst alt
This bug affects me, too:
ch...@lotus:~$ date
Mo 11. Mai 13:29:05 CEST 2009
ch...@lotus:~$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu
Confirmed on jaunty.
$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found k
Confirmed on jaunty.
$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found k
Guy M, if you are looking for support on how to get around this (or any
other) problem, I suggest the ubuntu forums or Launchpad Answers
http://ubuntuforums.org
https://answers.launchpad.net/ubuntu/+source/grub
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You recei
I have just run into this.
Now when I ran grub and looked for /boot/grub/menu.lst
I get "error 15: file not found"
I'm a noob but I'd like to figure this thing out
Thanks
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you
After
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/202009/comments/29
(just a few messages up) , I'm back and everything works
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
My buddy Alex helped me fix this. I had to use Grub to write the new
/boot/grub/menu.lst to the MBR.
So:
First, get into grub
ja...@jakes-desktop:~$ grub
Probing devices to guess BIOS drives. This may take a long time.
[ Minimal BASH-like line editing is supported. For
the f
Well , I got the same issue.
I backed up my menu.lst, deleted the original one , ran 'sudo upgrade-grub',
answered 'yes' to create the file for me ...
And I've got a full menu.lst with all installed kernels.
I just have to reboot to see if everything is ok ...
--
update-grub not updating menu.ls
Thanks again Steve. I posted in the forum at:
http://ubuntuforums.org/showthread.php?p=6638834#post6638834
I have three disks with two partitions each. Two disks are part of the
raid 1 array and the third disk is a spare. One partition is mounted on
root and the second is the swap. I checked the a
On Thu, Jan 29, 2009 at 06:01:17AM -, JacobSteelsmith wrote:
> Thanks for the reply. I run only one operating system on this machine
> and I do not have a separate boot partition:
> ja...@jakes-desktop:~$ df -h
> FilesystemSize Used Avail Use% Mounted on
> /dev/md0 22
Thanks for the reply. I run only one operating system on this machine
and I do not have a separate boot partition:
ja...@jakes-desktop:~$ df -h
FilesystemSize Used Avail Use% Mounted on
/dev/md0 228G 161G 56G 75% /
tmpfs 2.0G 0 2.0G 0% /lib/init
I tried running sudo update-grub and sudo dpkg-reconfigure linux-
image-2.6.27-11-generic to no avail. menu.lst looks good, but the grub
menu at boot time is still the old menu.
I am curious as to where menu.lst is being read from or cached. In my
experience, if menu.lst was changed, it would show
On Thu, Jan 29, 2009 at 05:36:27AM -, JacobSteelsmith wrote:
> I removed linux-image-2.6.24-22-generic and got the same prompt about
> menu.lst. I chose to keep the maintainers version. I rebooted with the
> same results. In fact, I was able to boot to the 2.6.24-22 kernel even
> though I remov
I removed linux-image-2.6.24-22-generic and got the same prompt about
menu.lst. I chose to keep the maintainers version. I rebooted with the
same results. In fact, I was able to boot to the 2.6.24-22 kernel even
though I removed the image.
--
update-grub not updating menu.lst
https://bugs.launchp
I think I have a similar issue. I also removed the splash option from
the kernel, and I was also prompted to keep my modified version of
menu.lst.
However, I remembered what I had done and choose to use the maintainer's
version. Now, menu.lst does not reflect what is presented at boot time.
It doe
As this can cause users to run older kernels, in particular missing
security fixes, I'd argue that it's fairly important.
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
for this bug to leave your system unbootable, you must:
- manually edit the list of boot stanzas in the "automagic" section of menu.lst
- install a new kernel and choose the "safe" default when asked what to do
about menu.lst
- manually uninstall your existing kernel.
Downgrading the bug importan
just got bitten by this myself. I do think that something leaving an
inexperienced user unable to boot the system is indeed critical.
Marking as such, please adjust if you feel this is necessary.
** Changed in: grub (Ubuntu)
Importance: Undecided => Critical
--
update-grub not updating menu.
Thanks for this . Will try as soon as possible.
--
Francis
On Mon, Nov 24, 2008 at 6:42 PM, felix.rommel <[EMAIL PROTECTED]> wrote:
> Have located my problem:
>
> NEVER put anything manually into the
>
> BEGIN AUTOMAGIC KERNELS LIST
>
> section. Otherwise menu.lst will grow bigger and bigg
Have located my problem:
NEVER put anything manually into the
BEGIN AUTOMAGIC KERNELS LIST
section. Otherwise menu.lst will grow bigger and bigger!
Put menu additions below the ## End default options ## section
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
Y
Me too.. Is there any workaround?
I tried re-installing the kernel, but still update-grub refuses to
modify menu.lst. Also tried to install and use startupmanager; this
hangs on close.
/var/lib/ucf/cache/\:var\:run\:grub\:menu.lst does show the kernels I
expect to see in the normal menu.lst.
I
I'm still experiencing this problem in Intrepid.
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Another big problem is:
If I start grub-update and choose the menu.lst version which is provided
by the packager, my menu.lst file grows bigger and bigger everytime I
run grub-update.
That mustn't happen - choosing menu.lst version from packager should
create a clean menu.lst file - otherwise peo
Please set Importance to critical, as this is a serious issue: if
someone runs into this, and deinstalls older kernels, he/she will be
unable to boot his/her system.
** Changed in: grub (Ubuntu)
Status: New => Confirmed
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/
Can confirm this. The same issue: aptitude installed the newer kernels,
I failed to allow the postinstall script to overwrite grub.lst. I
thought it wants to change some default values, that I set to my
preferences, and the boot lines are going to be updated anyway, later,
when update-grub is calle
I have to agree with jfjellstad and bugmenot, the wording is pretty
confusing. I assumed that what came up with as default was the prior
action, that it would update menu.lst with the new kernels at the top of
the AUTOMAGIC section. I think better wording for "Install package
maintainers version"
I was having this problem too. I just uninstalled all the old kernel
items via synaptic. Anything with linux 2.6.22-14 should be able to be
removed. I was then prompted again whether I would like to keep my
current menu.lst. This time I said to use the package maintainer's
version and menu.lst
Ditto. The wording of the prompt is totally unhelpful. It asks
something like "What would you like to do with menu.lst", to which my
natural response is "I haven't a clue, please tell me what you're trying
to do with it!"
Since I didn't understand the question and couldn't find an answer
online
I ran into the same problem. That is, update-grub did not update menu.lst
because I answered "keep old version"
Note that with "Keep old version", update-grub will not install new kernel
images into menu.lst
The wording seems wrong, since I interpreted "Install package
maintainers version" to m
I am in the same boat. Like Jamie, I said not to alter menu.lst because
I had removed "splash" from the default options.
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I am not explicitly setting DEBIAN_FRONTEND and I have never set that myself.
I did change menu.lst at one point (playing with splash and quiet) and do
remember getting prompted by grub. I said to keep the currently installed
version:
$ echo "get grub/update_grub_changeprompt_threeway" | debcon
$ echo "get debconf/frontend" | debconf-communicate
0 Dialog
This is not DEBIAN_FRONTEND; I'm looking for the value of the
DEBIAN_FRONTEND environment variable here, which overrides whatever
frontend setting is stored in debconf itself.
The expected behavior is that when you run update-grub (as
Here is an strace, though nothing jumped out at me.
** Attachment added: "update-grub.strace"
http://launchpadlibrarian.net/12660443/update-grub.strace
** Changed in: grub (Ubuntu)
Status: Incomplete => New
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
Yo
$ echo "get debconf/frontend" | debconf-communicate
0 Dialog
** Attachment added: ":var:run:grub:menu.lst"
http://launchpadlibrarian.net/12660435/%3Avar%3Arun%3Agrub%3Amenu.lst
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification beca
Hi Jamie,
Please also provide the contents of
/var/lib/ucf/cache/\:var\:run\:grub\:menu.lst .
What is your DEBIAN_FRONTEND set to when you invoke update-grub?
** Changed in: grub (Ubuntu)
Status: New => Incomplete
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/2020
Here is my menu.lst
** Attachment added: "menu.lst"
http://launchpadlibrarian.net/12657846/menu.lst
--
update-grub not updating menu.lst
https://bugs.launchpad.net/bugs/202009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
77 matches
Mail list logo