Thanks for testing this out! You have narrowed it down to the grub
loader. Now for the critical difference between the two grubs... The
Ubuntu grub has a lot of Ubuntu changes patched in, I don't know about
the Mandriva one. No surprise they have different file size, they are
compiled in different
tormod, I don't need to backup my data - the system is alway clear "a
fresh new installation" ;-)
ok, but now here the results:
(1) changing menu.lst --> with the Ubuntu menu.lst i can normal booting Ubuntu
(ok, this is what we expected)
(2) changing stage-files --> crash ! can't boot any system
mpwalter, I hope you have a good boot floppy/cd and a backup, because
this can get messy :) Actually it shouldn't be any risk at all, only
boot sectors will be changed, and if you can boot a grub floppy you can
always recover.
- I am not sure if it's possible to use stage1 from Mandriva and stage1
tormon, some question: You mean, I will "start" with Mandriva GRUB, go
to the command line and install then the Ubuntu-Grub - right?
So at the cmd line I try to handle with "setup" ... hmm, I don't really
know to do ... for my understanding: with "setup" I can copy/Install the
"stage"-Files from M
Sorry, I was too fast there. In (1) it would install the Ubuntu boot
loader to MBR, even when running the Mandriva grub. You have to do it
more manually, copying the Mandriva stage1 file to the Ubuntu /boot/grub
directory for instance. It might be the "setup" command can specify the
"stage1" to use
mpwalter, it would be very interesting to know if it works with the Mandriva
grub, for instance doing something like this:
1. Try installing only the boot loader from Mandriva, by booting the Mandriva
grub, go in command mode and run "root" to choose the Ubuntu partition and run
"setup" to insta
mpwalter, so you get the broken /proc/cmdline, and you've not even
installed dmraid? This might be a more general problem then.
--
ALERT! does not exist at boot with fakeraid
https://bugs.launchpad.net/bugs/106887
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I don't use any raid , so I don't check it. But I can set up one to test
, if Mandriva Grub works.
--
ALERT! does not exist at boot with fakeraid
https://bugs.launchpad.net/bugs/106887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
The corrupted /proc/cmdline output indicates some serious trouble.
Either there's a grave bug in grub or in the kernel (fakeraid modules?)
or the BIOS corrupts the kernel and initrd when it reads them from disk.
That the Mandriva grub works fine would point to grub.
Do you have raid-1 (mirror)? Ca
Hi,
had the same problem (SATA2 HDD on ICH7 - 82801). I have this discuss
here: http://forum.ubuntuusers.de/viewtopic.php?p=744986 (german only,
sorry). With Ubuntu 6.06 - 7.04 it doesn't work - same error(s). The I
have installed - for testing - Mandriva 2007 Spring Power Pack, which
use also GRU
Arno, you have a different problem -> please file a new bug. The
udevsettle line has been included in the Feisty version. I experienced
myself a slow boot in Edgy, even when including udevsettle, but I
upgraded to Feisty and everything was fine (I was just stepping through
Edgy on an upgrade from D
Hi
I get a similar error on the an intel ich7 as well. In my case though
the raid partition appears after the ALERT! message, saying something
like
check root= bootarg cat /proc/cmdline or missing modules, device : cat
/prc/modules ls /dev ALERT! /dev/mapper/
/dev/mapper/isw_bbfdjggjhj_HDDRAID6 d
I have checked
-in the grub menu, with e : root= is right filled, same as in the meu.lst
-with break=mount : make no difference
-if I do "cat /proc/cmdline , after that all the caracters and line are made of
cube, triangle and losange. I can only do ctrl-alt-del to restart the computer
because
I forgot to mention that I have also a lot of line like this :
sda: rw=o, want=582163478, limit=29304678, attempt to access beyond end
of device
before the error with the "waiting for root filesystem"
--
ALERT! does not exist at boot with fakeraid
https://bugs.launchpad.net/bugs/106887
You rec
Your menu.lst looks fine AFAICS. But I wonder if grub is reading it
correctly when you boot. In the grub menu, please press 'e' to edit the
entry, and verify that the root= is filled out. Please also do as
suggested by the error message: type "cat /proc/cmdline" and tell us
what it is.
Try also to
here is my /boot/grub/menu.lst
I've got 4 primary partition :
device Volume0
--Volume01 /boot
--Volume02 /ntfs (win)
--Volume03 /
--Volume04 swap
I have removed 'savedefault'
** Attachment added: "boot/grub/menu.lst"
http://librarian.launchpad.net/7336637/menu.lst
--
ALERT! does not exist
Thanks for your bug report. Please attach your /boot/grub/menu.lst
** Changed in: dmraid (Ubuntu)
Status: Unconfirmed => Needs Info
--
ALERT! does not exist at boot with fakeraid
https://bugs.launchpad.net/bugs/106887
You received this bug notification because you are a member of Ubuntu
B
17 matches
Mail list logo
