Re: can't boot due to root device problem

[Bob Berman]

I just got back to this system to read my email and in the
interim, I read about the "initrd" comand and how initrds
work. I added initrd=/boot/initrd to my Grub command list
and that worked.

Thanks to everyone.



On Sun, 30 Sep 2001, Mario Klebsch wrote:

> On Sunday, 30. September 2001 17:34, Bob Berman wrote:
> > I am sure that this is the problem. But I have another Linux
> > install on the same machine and that boots fine, although
> > it is SuSe 7.0 vs. this one is SuSe 7.2. This was an
> > initial install from CD and I had never booted it before.
> > Now I have to figure out some way to boot it.
> 
> As someone else has already written, you probably do not boot the
> initial ram disk. The initial ram disk is an additional file system,
> which is used as a temporary root filesystem prior to mounting the real
> root filesystem. This ram disk somtimes does contain drivers needed to
> mount the root filesystem.
> 
> Allthough this IMHO is broken by design and a popular source of
> trouble, linux included it to allow distributions without custom
> kernels. GRUB does have an option to load the initial ramdisk, but I
> cannot tell you about it, because I do not use it. I suppose, the GRUB
> documentation will contain some hints about the initial RAM disk.
> 
> I would just boot your first linux system and build a kerlen which
> includes the drivers needed. This kernel can be put on a floppy disk or
> bootet via grub or lilo.
> 
> 73, Mario
> --
> Mario Klebsch                                         address@hidden
> PGP-Key available at http://www.klebsch.de/public.key
> Fingerprint DSS: EE7C DBCC D9C8 5DC1 D4DB  1483 30CE 9FB2 A047 9CE0
>  Diffie-Hellman: D447 4ED6 8A10 2C65 C5E5  8B98 9464 53FF 9382 F518
> 
> ------------ Output from pgp ------------
> Pretty Good Privacy(tm) Version 6.5.8
> (c) 1999 Network Associates Inc.
> Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc.
> Export of this software may be restricted by the U.S. government.
> File is signed.  signature not checked.
> Signature made 2001/09/30 18:47 GMT
> key does not meet validity threshold.
> WARNING:  Because this public key is not certified with a trusted
> signature, it is not known with high confidence that this public key
> actually belongs to: "(KeyID: 0xA0479CE0)".
> 
>