grub2: After current update update-grub messes up device names, making the system unbootable.

grub2: After current update update-grub messes up device names, making the system unbootable.

[Robert Millan]

On Mon, May 07, 2007 at 07:10:54PM +0200, Szántó Dániel wrote:
> Root partition is /dev/md0.

Ah, you should have mentioned that you're using software RAID or the likes.

RAID is supported but it is not too mature.  Please can you run
"grub-probe -v -t device /boot/grub" and send the output?

I'm also forwarding this to upstream mailing list.  Keep them in CC.

GRUB maintainers: Szántó got /dev/sda1 instead of /dev/md0 when running
grub-probe -t device.

> For clarification I have attached the original and the updated 
> /boot/grub/grub.cfg, with comments cut away, as well as /etc/fstab and 
> /etc/mtab

/etc/fstab and /etc/mtab are not used now, only grub-probe.

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Re: grub2: After current update update-grub messes up device names, making the system unbootable.

[Robert Millan]

On Tue, May 08, 2007 at 09:41:55PM +0200, Szántó Dániel wrote:
> On Tue, May 08, 2007 at 09:22:17AM +0200, Robert Millan wrote:
> > On Mon, May 07, 2007 at 07:10:54PM +0200, Szántó Dániel wrote:
> > > Root partition is /dev/md0.
> > Ah, you should have mentioned that you're using software RAID or the likes.
> > 
> > RAID is supported but it is not too mature.  Please can you run
> > "grub-probe -v -t device /boot/grub" and send the output?
> 
> Sorry for not pointing out RAID, I'm not yet an expert at reporting 
> bugs :) Anyway, I have attached the result.

Actualy you forgot it ;-)

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Re: grub2: After current update update-grub messes up device names, making the system unbootable.

[Yoshinori K. Okuji]

On Tuesday 08 May 2007 09:22, Robert Millan wrote:
> On Mon, May 07, 2007 at 07:10:54PM +0200, Szántó Dániel wrote:
> > Root partition is /dev/md0.
>
> Ah, you should have mentioned that you're using software RAID or the likes.
>
> RAID is supported but it is not too mature.  Please can you run
> "grub-probe -v -t device /boot/grub" and send the output?
>
> I'm also forwarding this to upstream mailing list.  Keep them in CC.
>
> GRUB maintainers: Szántó got /dev/sda1 instead of /dev/md0 when running
> grub-probe -t device.

Is it really mounted correctly? What is the content of /proc/mount?

Okuji

Re: grub2: After current update update-grub messes up device names, making the system unbootable.

[Robert Millan]

retitle 422459 update-grub generates broken grub.cfg when /boot is a separate partition
thanks

On Tue, May 08, 2007 at 10:16:50PM +0200, Szántó Dániel wrote:
> > 
> > Is it really mounted correctly? What is the content of /proc/mount?
> > 
> > Okuji
> 
> Here it is:
> 
> ananasz:~# cat /proc/mounts 
> [...]
> /dev/sda1 /boot ext3 rw,data=ordered 0 0

Here it is.  /dev/sda1 _is_ the right device, but your grub.cfg is still wrong.

What do you see during boot?

Can you try "ln -s . /boot/boot" and confirm this works around the problem?

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Re: grub2: update-grub generates broken grub.cfg when /boot is a separate partition

[Robert Millan]

On Wed, May 09, 2007 at 10:25:53PM +0200, Szántó Dániel wrote:
> On Wed, May 09, 2007 at 09:15:48AM +0200, Robert Millan wrote:
> > > ananasz:~# cat /proc/mounts 
> > > [...]
> > > /dev/sda1 /boot ext3 rw,data=ordered 0 0
> > 
> > Here it is.  /dev/sda1 _is_ the right device, but your grub.cfg is still wrong.
> > 
> > What do you see during boot?
> 
> What details should I give? The output of dmesg with the correct grub.cfg
> or the error message I get when trying to boot with the wrong one?

The error message.

> > Can you try "ln -s . /boot/boot" and confirm this works around the problem?
> 
> Nothing changes, after symlinking /boot to /boot/boot update-grub 
> generates exactly the same grub.cfg.

Does it boot now?

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Re: grub2: update-grub generates broken grub.cfg when /boot is a separate partition

[Robert Millan]

On Thu, May 10, 2007 at 08:28:09PM +0200, Szántó Dániel wrote:
> On Thu, May 10, 2007 at 09:19:05AM +0200, Robert Millan wrote:
> > On Wed, May 09, 2007 at 10:25:53PM +0200, Szántó Dániel wrote:
> > > On Wed, May 09, 2007 at 09:15:48AM +0200, Robert Millan wrote:
> > 
> > > > Can you try "ln -s . /boot/boot" and confirm this works around the problem?
> > > 
> > > Nothing changes, after symlinking /boot to /boot/boot update-grub 
> > > generates exactly the same grub.cfg.
> > 
> > Does it boot now?
> 
> No,

Ah.  Well, I spotted a problem with update-grub not generating relative paths
when /boot is a separate partition.

But it seems you hit other bugs related with RAID.  I'm afraid I can't comment
on these.

> It gives the same error message:
>   Booting "Debian GNU/Linux, linux 2.6.20-1-amd64"
> 
> error: you need to load the kernel first
> 
> Press any key to continue...
> 
> If I edit the grub command line and settings to set root to hd0,0 and 
> the linux kernel paramter to root=/dev/md0, I get the same error if
> the cursor is below the last line. If the cursor is at the end of the 
> last line I get 
> error: Out of memory
> instead.
> I 
> DTR
> 

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.