The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
I also had the problem were grub chose the wrong root (hdx,y) for all
partitions.
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
We have the machine locked again with the same problem after new kernel update
linux-image-2.6.15-27-amd64-generic (2.6.15-27.48).
Is there anybody who cares about ubuntu users and about perception of
stability and reliabilty of Ubuntu as a distribution ?!?
I consider this a serious ( if not crit
> because all grub entries are 'patched' to point to (hd0,0) and
/dev/hda1
Did you replace manually all occurences of hd(0,0), or did you change
the commented value (such as groot=, kopt=), and then run 'sudo update-
grub' ?
If you installed ubuntu on the first partition, and then you moved it,
a
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Jan, did you fix your #kopt line? Please attach your menu.lst if you
still have problems.
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
i have modified both the groot line and the 2 kopt lines a couple of
times now.
this last kernel update i have become certain - the changes to both of
these values in menu.lst are edited away by the script that updates
grub.
i am sure those two lines were correct because this has happened a few
t
i just tried to update menu.lst manually and then did update-grub
perhaps this error message is helpful. of course im certain of the UUID - i got
it from /dev/disks/by-uuid and it seems to work in fstab every time
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to r
this gets weirder and weirder. when i do mount or df to check that the
root partition is mounted it doesnt show up...but im running my linux
box with no problem...what is happening? any advice or help appreciated
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
h
sorry for the repeated comments but now im sure the problem lies with
findfs
when my fstab uses /dev/hda2 update-grub works correctly. but when my
fstab uses the UUID which is correct update-grub fails and gives the
above error message. i hope this will allow somebody to solve it...
--
GRUB's me
Hello :)
i've got the same problem I guess and I got it since I upgraded from
Dapper Drake to Edgy Eft (even with reinstalling the system from
scratch). grub does not properly generate the menu.lst so I can't boot
without editing manually the startup script. It is a problem of UUID by
the way : my
Jedi, I suggest you file a new bug against udev (which maps disk/by-uuid
using vol_id) for the mismatch with blkid (from e2fsprogs).
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because
OK thanks. I was not sure where the problem could come from ;-)
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
I also had the problem were grub chose the wrong root (hdx,y) for all
partitions.
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
We have the machine locked again with the same problem after new kernel update
linux-image-2.6.15-27-amd64-generic (2.6.15-27.48).
Is there anybody who cares about ubuntu users and about perception of
stability and reliabilty of Ubuntu as a distribution ?!?
I consider this a serious ( if not crit
> because all grub entries are 'patched' to point to (hd0,0) and
/dev/hda1
Did you replace manually all occurences of hd(0,0), or did you change
the commented value (such as groot=, kopt=), and then run 'sudo update-
grub' ?
If you installed ubuntu on the first partition, and then you moved it,
a
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Jan, did you fix your #kopt line? Please attach your menu.lst if you
still have problems.
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
i have modified both the groot line and the 2 kopt lines a couple of
times now.
this last kernel update i have become certain - the changes to both of
these values in menu.lst are edited away by the script that updates
grub.
i am sure those two lines were correct because this has happened a few
t
i just tried to update menu.lst manually and then did update-grub
perhaps this error message is helpful. of course im certain of the UUID - i got
it from /dev/disks/by-uuid and it seems to work in fstab every time
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to r
this gets weirder and weirder. when i do mount or df to check that the
root partition is mounted it doesnt show up...but im running my linux
box with no problem...what is happening? any advice or help appreciated
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
h
sorry for the repeated comments but now im sure the problem lies with
findfs
when my fstab uses /dev/hda2 update-grub works correctly. but when my
fstab uses the UUID which is correct update-grub fails and gives the
above error message. i hope this will allow somebody to solve it...
--
GRUB's me
Hello :)
i've got the same problem I guess and I got it since I upgraded from
Dapper Drake to Edgy Eft (even with reinstalling the system from
scratch). grub does not properly generate the menu.lst so I can't boot
without editing manually the startup script. It is a problem of UUID by
the way : my
Jedi, I suggest you file a new bug against udev (which maps disk/by-uuid
using vol_id) for the mismatch with blkid (from e2fsprogs).
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because
OK thanks. I was not sure where the problem could come from ;-)
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
I also had the problem were grub chose the wrong root (hdx,y) for all
partitions.
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
We have the machine locked again with the same problem after new kernel update
linux-image-2.6.15-27-amd64-generic (2.6.15-27.48).
Is there anybody who cares about ubuntu users and about perception of
stability and reliabilty of Ubuntu as a distribution ?!?
I consider this a serious ( if not crit
> because all grub entries are 'patched' to point to (hd0,0) and
/dev/hda1
Did you replace manually all occurences of hd(0,0), or did you change
the commented value (such as groot=, kopt=), and then run 'sudo update-
grub' ?
If you installed ubuntu on the first partition, and then you moved it,
a
Hello :)
i've got the same problem I guess and I got it since I upgraded from
Dapper Drake to Edgy Eft (even with reinstalling the system from
scratch). grub does not properly generate the menu.lst so I can't boot
without editing manually the startup script. It is a problem of UUID by
the way : my
Jedi, I suggest you file a new bug against udev (which maps disk/by-uuid
using vol_id) for the mismatch with blkid (from e2fsprogs).
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because
OK thanks. I was not sure where the problem could come from ;-)
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
i have modified both the groot line and the 2 kopt lines a couple of
times now.
this last kernel update i have become certain - the changes to both of
these values in menu.lst are edited away by the script that updates
grub.
i am sure those two lines were correct because this has happened a few
t
i just tried to update menu.lst manually and then did update-grub
perhaps this error message is helpful. of course im certain of the UUID - i got
it from /dev/disks/by-uuid and it seems to work in fstab every time
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to r
this gets weirder and weirder. when i do mount or df to check that the
root partition is mounted it doesnt show up...but im running my linux
box with no problem...what is happening? any advice or help appreciated
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
h
sorry for the repeated comments but now im sure the problem lies with
findfs
when my fstab uses /dev/hda2 update-grub works correctly. but when my
fstab uses the UUID which is correct update-grub fails and gives the
above error message. i hope this will allow somebody to solve it...
--
GRUB's me
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
Jan, did you fix your #kopt line? Please attach your menu.lst if you
still have problems.
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
i have modified both the groot line and the 2 kopt lines a couple of
times now.
this last kernel update i have become certain - the changes to both of
these values in menu.lst are edited away by the script that updates
grub.
i am sure those two lines were correct because this has happened a few
t
i just tried to update menu.lst manually and then did update-grub
perhaps this error message is helpful. of course im certain of the UUID - i got
it from /dev/disks/by-uuid and it seems to work in fstab every time
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to r
this gets weirder and weirder. when i do mount or df to check that the
root partition is mounted it doesnt show up...but im running my linux
box with no problem...what is happening? any advice or help appreciated
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
h
sorry for the repeated comments but now im sure the problem lies with
findfs
when my fstab uses /dev/hda2 update-grub works correctly. but when my
fstab uses the UUID which is correct update-grub fails and gives the
above error message. i hope this will allow somebody to solve it...
--
GRUB's me
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
I also had the problem were grub chose the wrong root (hdx,y) for all
partitions.
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
We have the machine locked again with the same problem after new kernel update
linux-image-2.6.15-27-amd64-generic (2.6.15-27.48).
Is there anybody who cares about ubuntu users and about perception of
stability and reliabilty of Ubuntu as a distribution ?!?
I consider this a serious ( if not crit
> because all grub entries are 'patched' to point to (hd0,0) and
/dev/hda1
Did you replace manually all occurences of hd(0,0), or did you change
the commented value (such as groot=, kopt=), and then run 'sudo update-
grub' ?
If you installed ubuntu on the first partition, and then you moved it,
a
Jan, did you fix your #kopt line? Please attach your menu.lst if you
still have problems.
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
Hello :)
i've got the same problem I guess and I got it since I upgraded from
Dapper Drake to Edgy Eft (even with reinstalling the system from
scratch). grub does not properly generate the menu.lst so I can't boot
without editing manually the startup script. It is a problem of UUID by
the way : my
Jedi, I suggest you file a new bug against udev (which maps disk/by-uuid
using vol_id) for the mismatch with blkid (from e2fsprogs).
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because
OK thanks. I was not sure where the problem could come from ;-)
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
i have modified both the groot line and the 2 kopt lines a couple of
times now.
this last kernel update i have become certain - the changes to both of
these values in menu.lst are edited away by the script that updates
grub.
i am sure those two lines were correct because this has happened a few
t
i just tried to update menu.lst manually and then did update-grub
perhaps this error message is helpful. of course im certain of the UUID - i got
it from /dev/disks/by-uuid and it seems to work in fstab every time
Searching for GRUB installation directory ... found: /boot/grub
findfs: Unable to r
this gets weirder and weirder. when i do mount or df to check that the
root partition is mounted it doesnt show up...but im running my linux
box with no problem...what is happening? any advice or help appreciated
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
h
sorry for the repeated comments but now im sure the problem lies with
findfs
when my fstab uses /dev/hda2 update-grub works correctly. but when my
fstab uses the UUID which is correct update-grub fails and gives the
above error message. i hope this will allow somebody to solve it...
--
GRUB's me
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
I also had the problem were grub chose the wrong root (hdx,y) for all
partitions.
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
We have the machine locked again with the same problem after new kernel update
linux-image-2.6.15-27-amd64-generic (2.6.15-27.48).
Is there anybody who cares about ubuntu users and about perception of
stability and reliabilty of Ubuntu as a distribution ?!?
I consider this a serious ( if not crit
> because all grub entries are 'patched' to point to (hd0,0) and
/dev/hda1
Did you replace manually all occurences of hd(0,0), or did you change
the commented value (such as groot=, kopt=), and then run 'sudo update-
grub' ?
If you installed ubuntu on the first partition, and then you moved it,
a
Jan, did you fix your #kopt line? Please attach your menu.lst if you
still have problems.
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: grub (Ubuntu)
This is still a problem. I detail much of it here:
http://www.howtoadvice.com/DellUbuntu/
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
In Dell's case and in the original report, it was the result of a custom
installation that didn't set #groot correctly.
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://bugs.launchpad.net/bugs/61108
You received this bug notification because you are a mem
As of Ubuntu 7.04, people install via the gui, and there is no
opportunity for them to set #groot. If they don't install their OS at
(hd1,0), they'll lose their ability to boot the first time they do a
system update that contains a kernel update!
Let's responsibility here, and help people avoid th
Lonnie, it's not that bad. The installer sets #groot correctly for most
people. It's usually when you have raids, or a mix of ide/sata drives it
guesses wrong. But I agree that it shouldn't do these poor guesses every
time you install a new kernel.
It makes sense to have one #groot for all kernel
** Bug 61630 has been marked a duplicate of this bug
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The kernel doesn't modify the menu.lst, it only calls update-grub.
** Changed in: linux-source-2.6.15 (Ubuntu)
Sourcepackagename: linux-source-2.6.15 => grub
--
GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot
https://launchpad.net/bugs/61108
--
ubuntu-bugs maili
1 - 100 of 132 matches
Mail list logo
