Alfredo, please attach your menu.lst.
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://bugs.launchpad.net/bugs/46223
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
This bug still exists in Hardy. Each time I upgrade my kernel, I have to
manually restore my menu.lst file.
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://bugs.launchpad.net/bugs/46223
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Interesting that Dell got bitten by this, they are probably not using RAID like
in this bug. Congratulations with your new Ubuntu Dell, Lonnie :)
The convert() and find_device() functions inside update-grub are not pretty.
They are also duplicated in grub-install. I hope it will be all rewritten
This is still a problem on 6-6-2007:
http://www.howtoadvice.com/DellUbuntu/
The update-grub command does a poor job of determining which partition
the operating system in on.
Instead of using the "#groot" line in /boot/grub/menu.lst why doesn't it
just look at the last kernel's root partition and
I think we can leave this bug open:
1) The installer should have written #groot=(hd0,4) in the first place.
2) if the #groot gets lost (like it did in Giuseppe's case because he removed
the#) and it needs to be autogenerated, it should guess better than (hd0,0).
** Changed in: grub (Ubuntu)
Ok, this is not a bug, I read menu.lst:
## DO NOT UNCOMMENT THEM, Just edit them to your needs
so the right valuse is # groot=(hd0,4)
** Changed in: grub (Ubuntu)
Status: Needs Info => Rejected
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/bug
Attachment is update-grub.txt
I think problem is here:
+ sed -ne /^### BEGIN AUTOMAGIC KERNELS LIST$/,/^### END DEBIAN AUTOMAGIC
KERNELS LIST$/ {
/^## ## Start Default Options ##$/,/^## ## End Default Options
##$/ {
/^# groot=/ {
Sorry, I meant:
sudo sh -x /sbin/update-grub 2>update-grub.txt
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/bugs/46223
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks. This is update-grub trying to be smarter than it is - it will
try to detect a RAID and pick the right raw device but fails, and falls
back to (hd0,0).
(IMHO it's a separate bug that update-grub at all tries to change these
#groot or #kopt values that users have configured. That should mayb
And this is the menu.lst after update-grub
** Attachment added: "menu.lst after update-grub"
http://librarian.launchpad.net/5152532/menu.lst.after
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/bugs/46223
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I set groot=(hd0,4), but update-grub delete it and add a commented
groot=(hd0,0)
Attachment is the good menu.list
** Attachment added: "menu.lst working"
http://librarian.launchpad.net/5152514/menu.lst
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/
Make sure that your menu.lst has correct #kopt and #groot entries. Can
you please attach your menu.lst?
** Changed in: grub (Ubuntu)
Status: Confirmed => Needs Info
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/bugs/46223
--
ubuntu-bugs mailin
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Confirmed
--
[DAPPER] update-grub doesn't work correctly with raid partitions
https://launchpad.net/bugs/46223
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I confirm this (the bug exists at least in 6.06.1 and 6.10).
I just installed a new machine with two disks and with the following
partitions:
sda1 NTFS sdb1 ext3==> used as /data
sda2 RAID sdb2 RAID==> md0 used as /
sda3 RAID sdb3 RAID==> md1 used as swap
sda4 RA
14 matches
Mail list logo
