Re: Bug#108640: grub: doesn't load symlinks kernel images on reiserfs (big drive)

[Stephane Jourdois]

On Thu, Aug 16, 2001 at 02:36:27PM +0200, Jochen Hoenicke wrote:
> I thought I had fixed symlinks for new reiserfs.  I haven't tested
> symlinks to files, though, or maybe the format has changed again.
That's what I'm afraid...
Anyway, I decided then to use the great tool provided for debian, update-grub.
It doesn't use symlinks.
I'll help you anyway :-)

> > ----- Forwarded message from Stephane Jourdois <address@hidden> -----
> > > Issuing the following commands at the grub prompt at boot doesn't work:
> > > > root (hd0,0)
> > > > kernel /boot/vmlinuz root=/dev/hdh1
> > > No error message, nor warning message, just prompt again.
> > > if I enter the 'boot' command then, it asks me to load a kernel image 
> > > before.
> > > Then:
> > > > kernel /boot/vmlinuz-2.4.8-ac1 root=/dev/hdh1
> > > works fine.
> > > 
> > > Now some important things about my config:
> > > - /boot/vmlinuz is a symlink to vmlinuz-2.4.8-ac1
> Do directory symlinks work for you? I.e if you make a symlink to
> /boot, can grub follow it correctly?  You can try this in the grub
> shell under linux it should make no difference.
Well, grub recognize the symlink itself. the 'find' command finds the file, and
the 'cat' command catalogize it. I'll test for directory symlinks.

> You can generate more debugging information by enabling REISERDEBUG.
> For this open fsys_reiserfs.c and change in line 25 the #undef to a
> #define.  The easiest way to capture this output is to start 
> "grub --no-curses" in an xterm.  You can redirect the output to a file
> but then you have to type blindly.

> > > - I have a 75 Go IBM disk, a single partition on it. (/boot is in /)
> > > - That partition is reiserfs
> > > - my hard drive is brand new, but I used exactly the same config before, 
> > > and
> > >   AFAIR, it used to work fine...
> Did you have reiserfs before?
Yup

> > > Perhaps a too small buffer for symlinks on my big drive ?
> I don't think that this is the case but the debugging information
> would tell this.

root(pts/3)@mafalda:~# grub --version
grub (GNU GRUB 0.90)
<!-- debian package is 0.90.5 -->
root(pts/3)@mafalda:~# grub --no-curses >grub.log
Probing devices to guess BIOS drives. This may take a long time.
root (hd4,0)
kernel /boot/vmlinuz root=/dev/hdh1
boot
root(pts/3)@mafalda:~#

see grub.log attached.

The problem is, AFAIK, that in console mode I can't know if the boot command is
successfull or not. I mean I got the same "no-debug" output when it used to 
work.
Hope it can help anyway...


-- 
Stephane Jourdois - Ingénieur développement  /"\
  6, av. de la Belle Image                   \ /  ASCII RIBBON CAMPAIGN
  94440 Marolles en Brie   - FRANCE           X     AGAINST HTML MAIL
     +33 6 8643 3085                         / \

pgpCqxFtFLs9M.pgp
Description: PGP signature