Since you seem to have internet access, try downloading a boot and
root disk from RedHat website..
Good luck.
PS: If RedHat does not have boot and root disk for you to download,
try SuSe (www.suse.com) or try to get to other distro from
www.linux.org...
______________________________ Reply Separator _________________________________
Subject: Re: Redhat6.1 crashed
Author: "Hong F Du" <[EMAIL PROTECTED]> at INTERNET-MAIL
Date: 7/21/00 1:35 PM
I greatly appreciate your detail instructions.
My bootdisk doesn't have root directory on it, I think. It automatically went to
/dev/hda10 and mounted root. It passed the clean check for /dev/hda10. It
prompted Remounting root filesystem in read-write mode [OK] too. Then it tried
to do next step and stop there.
I also tried to use "rescue" option when booting from bootdisk. It asked me for
a root disk which I don't have and I am stuck again. Am I dead here? : (
[EMAIL PROTECTED] wrote:
> Are you booting the kernel from the bootdisk but using the root as
> /dev/hda10?? I am talking about booting using the bootdisk both
> kernel and root directory. Do not supply /dev/hda10 as your root
> directory to be used, just boot normally as though you have no prior
> Linux setup at all. Should boot you using ramdisk (I am not sure, I
> have never installed RedHat distro before...)
>
> Then when it boots up, mount your /dev/hda10 to its mount point
> (usually /mnt but anything is ok) then go into rc.d and try to clean
> up (meaning comment out ANY process or applications that you do not
> need to boot up the system - gpm, X, etc...) maybe even getting rid of
> modprobe line may help too in case any of your modules are corrupted.
> Of course this should be done AFTER you do the file system check in
> /dev/hda10..
>
> Then, try to reboot normally to your system. Then, first thing I
> would do is to recompile the kernel, to make sure all my modules are
> not corrupted, then uncomment 1 application at a time from your init
> script. If you can uncomment all the lines without any problem, then
> it was corrupted modules, if one of them hangs your system, then you
> know which prog is bad, so you can boot with your boot disk again, and
> reinstall the package.
>
> Good luck!!!!
>
