Re: GRUB & Rieserfs
>From what I've read and seen GRUB can read Reiserfs: at least that's what I
thought the reiserfs_stage1_5 file was to provide...
Am I far off here? I've read MANY docs and I've seen several references to
GRUB supporting Reiserfs.
I REALLY want to use GRUB, and I wanted to play with reiserfs as well. The
system got stripped down to the bare minimum packages so I could move things
around, but I gotta get it back up and running so I can use the blasted thing to
actually DO some work on with it...
So, do I scrap GRUB (which would be easier to reinstall at a later date) or do
I put one or more ext2 file systems where I was going to have one large
reiserfs?
(LILO seems so old... )
So far I can get GRUB to come up, and can boot to about any ext2 partition I
choose.
I can mount the reiserfs file systems on any of those once I'm up and running.
This makes me believe that I have GRUB installed properly and that my kernel
really does support reiserfs.
Is it the kernel or the boot loader that makes the call to init? If the kernel
is making
the call and it has already loaded the root file system (as the boot time
messages
appear to indicate) then why can't it find init? The message says to try to
pass an
init= parameter to the kernel (which I did with no luck...) so that makes me
think
that it is the kernel who's unable to read the file system.
Could this have anything to do with the notail option? Should I have created
the
reiserfs an mounted it with notail before I copied any files on to it? Are
there
kernel parameters that can be passed that effect how the root file system is
mounted?
Chuck
Joerg Johannes wrote:
> Chuck Stickelman wrote:
> >
> > Howdy,
> >
> > I've made two changes to my home system (I know... should have done
> > one at a time...)
> > I've changed my boot loader from LILO to GRUB and I've changed my root
> > file system
> > from ext2 to reiserfs.
> >
> > my partition table is setup as:
> > /dev/hda1 ext2 /boot
> > /dev/hda2 swap
> > /dev/hda3 reiserfs /
> >
> > GRUB comes up with a menu and I can boot to /boot if needed.
> > To boot normally I tell GRUB that:
> > root (hd0,2)
> > kernel (hd0,0)/vmlinuz-2.4.5 root=/dev/hda3 ro
> >
> > I see the kernel loading, I see it mount the / (root) file system as a
> > reiserfs
> > (reiserfs support is in the kernel, not a module)
> > but I then get a kernel panic saying it is unable to find init.
> >
> > What's up? I've read through as many README's and .html files as I
> > can find.
> > The one thing I've noticed is a reference that says -notail is needed
> > for some
> > programs like LILO - is GRUB "like LILO" in this instance? If so, how
> > do I mount
> > / (root) with the -notail option? (I've tried editing the /etc/fstab
> > to include notail,ro
> > without any change.
> >
> > I'd guess I'm doing something stupid or overlooking the obvious...
> > just need to get
> > my machine back up and running and would rather not have to re-create
> > one or more
> > ext2 file systems...
> >
> > Any and all help appreciated.
> > Chuck
> >
>
> Hi Chuck
>
> The difference between lilo and grub is: lilo stores the raw place where
> the kernel image lies (the reason why you must run lilo every time you
> change your kernel) while grub has to be able to read the root
> partition: /boot/vmlinuz is a symlink to /vmlinuz => this is the
> cracking point.
>
> Are you sure grub can read reiserfs? I don't think so, so switch back to
> lilo until grub can read reiserfs and you will be fine for now
>
> hth
>
> joerg
>
> PS.: Everybody, please correct me if I'm wrong...
>
Reply to: