On 12/7/05, Andy Stewart <andystewart@comcast.net> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dick Goodman wrote:
> I recently configured a RedHat 9 system with OpenVPN . The original
> configuration was done on an old junk box. This is a single boot w/grub
> system
>
> As of last week I knew nothing about grub; I now know marginally more.
>
> As it was working successfully, it was decided to build a new box for it.
> The hard drive was imaged with Ghost Corporate 8.x and restored onto the
> new drive. There are some known issues with 8.x and grub
>
> The grub screen comes up on booting the new box, but when selecting the
> (one) entry for RH9, after a short pause it comes back to the grub
> screen. I read the grub manual, and from the grub screen did c-command,
> then
>
> root (hd0,0)
> setup (hd0)
> quit
>
> The messages after setup did not look like error messages. The behavior
> is the same, although I see a message about stage 1.5 flicker by.
> I figured out how to look at the hard drive with Knoppix 3.8.2 Live CD
> and the partitions  and contents look "ok", so it appears to just be a
> boot issue.
>
> How do I resolve this? What additional information do you need? Is there
> a better way to clone Linux drive -> Linux drive?
>
> Dick
> _______________________________________________
> Wlug mailing list
> Wlug@mail.wlug.org
> http://mail.wlug.org/mailman/listinfo/wlug
>

Here's what I use for boot commands in GRUB on my system.  Its SuSE, but
I don't think it should make a difference.

root (hd0,0)/vmlinuz <boot parameters>
initrd (hd0,0)/initrd

- From a GRUB command line, make sure (by using the TAB key) that (hd0,0)
is a legitimate partition, and that it can find /vmlinuz (or whatever
kernel image you are using).  If you need initrd, you can use the same
trick with the TAB key to get a poor man's directory listing.

After you enter those lines, or edit the existing lines to make them
look as above, boot it and you should at least get the kernel to start.
You may need to specify "root=/dev/xxx" as one of the boot parameters
on the "root" command.  If you get a panic when it tries to mount root,
it is either because you didn't specify "root=/dev/xxx", or because the
code for the root device isn't present in the kernel (for example, a
SCSI driver or a reiserfs module, as appropriate).  I hope root isn't
part of LVM...that's a can of worms you should avoid, but I digress.

I hope this helps,

Andy

- --
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA, USA
http://www.wlug.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDlnkCHl0iXDssISsRAuiaAJ0ZhX3Il4sFM2Yt2cCG1IQBZMy11wCfZIcn
bPoThROtkjrTtXGgaHq2Vms=
=J3lU
-----END PGP SIGNATURE-----
_______________________________________________
Wlug mailing list
Wlug@mail.wlug.org
http://mail.wlug.org/mailman/listinfo/wlug