On Wed, 11 Jan 2006 14:40:57 +0100, ArvinD <arvind.ayyangar@xxxxxxxxx> wrote:
Unruh wrote:
No redhat has 17 CDs No idea what you are talking about.
this was a general remark which meant that i have had 17 copies of
the SAME os,all currupted.
>created a bootable floppy using mkbootdsik and the sytem is booting
>usinh that floppy, and now shows the prompt
>boot:
No idea what you are talking about. That prompt is the LILO prompt asking
which kernel of the list to boot from. Sounds like there is no list.
On the off chance that Redhat were stupid enough to use that as teh prompt
in the shell of the rescue disk, try typing in a command. ls say. Does it
work?
If it does, you can reinstall the lilo bootloader
mkdir /disk
mount /dev/hda1 /disk
lilo -r /disk -b /dev/hda
(assuming your / partition for linux was on /dev/hda1)
Note that this will at this point remove your ability to boot into windows.
Boot into linux, edit /etc/lilo.conf and add an entry for your windows
no..these command are not wking, what shall i do then.
thanx in advance
Hello Arvin,
I think I recall that you said the grub loader... maybe you are using
grub, not lilo?
Unfortunately, I don't remember what mkbootdisk did. I think that must
have been something that was in use back when Red Hat had Lilo as its
default loader. Others may be able to advice you on how to do with lilo,
but I can probably tell you how to do it with grub.
This procedure should work even if you never used Grub before, and even
if you don't have a grub.conf file.
Since you now can boot into window, find and download a grub floppy image.
If you don't find one, I can upload one to my ISP, and mail you a link.
(Not before you ask). You also need a program that is called "rawrite.exe",
and runs under windows/dos. It copies an image file to a floppy.
If you know you used to have a grub config file, it is simple.
Just boot off the CD and when the prompt appears, say
setup (hd0)
and grub will search for a partition containing grub's stage2 file
and use that. Reboot, and you should be back in business.
If not, you need to know, or use Grub to find, the partition that
contains the kernel. If you know the partition is, e.g., /dev/hda1, then
the grub name is (hd0,0) The first zero is for the disk, the second for
the partition. Linux disks a, b, c, etc are grub's 0, 1, 2, etc. -
normally. (We deal with the exceptions if and when you tell that the
normal way fails.) The partitions are numbered from zero, so just
substract one from the linux partition number.
If you don't know the partition, just boot off the floppy and try this
command, when you get the Grub prompt:
find /etc/fstab
That will output e.g.
(hd0,4)
showing your root partition is /dev/hda5
Next you type
cat (hd0,4)/etc/fstab
Here you can see if you have a separate /boot partition or not. (You
probably already knew that.) If you had one, you now see the linux name
of the partition. If you had not, the kernels are on the same partition
as the /etc/fstab file.
Now enter the command
root (hd0,4)
or whichever is the partition containing the kernel(s). Note, don't let
the name of this command lead you astray. It does not refer to the
root file system, unless that happens to be where the kernels are.
Continue with one of these
kernel /boot/vmlin<TAB>
kernel /vmlin<TAB>
That is, /boot is a separate partition, that partition does not contain
a directory called /boot. It contains what you usually see as the contents
of that directory, at the root of the partition. In this case, the second
line above. <TAB> means you hit the TAB key. Grub will automatically
complete the file name for you. This is fortunate, because otherwise
you would have to try in turn all kernel names known to have been used
under RH9. If there are multiple kernels in the directory, you need to
press TAB twice, to see a list of your options. This is how Grub
implements the "ls" command.
Once you know in this way the file name of the kernel, add a few options
to the command line, e.g.
fixing grub : mbr fix when windows install after linux ... "There is not a boot manager screen at all, ...windows but GRUB boot window does not appear. ... "I forgot to install GRUB, I didn't install GRUB in the MBR, I chose ... Fedora but that was not an active primary partition".... (comp.os.linux.misc)
Re: Naming harddisks (Linux) ... But I also see that for an USB drive it uses /dev/sdas the ... Does GRUB recognize SCSI drives? ... The first step in understanding the boot process is to ... The bootloader's job is to load the OSs kernel.... (comp.os.linux.misc)
Re: Fedora Core 2/Windows XP dual boot: selecting Linux doesnt work ...grub is installed on the /root partition, which is the first partition on hdc: hdc1, or in grub notation. ... Stage1 is the unpatched 512-byte file, that is patched and copied to the boot record during setup. ... This byte is initialized to 0xff in the stage1 file, but patched to 0x81 in your setup, to say "we are booting from disk." ... (comp.os.linux.setup)
Re: Boot manager for Windows only ... And also is GRUB capable of booting any ... > Windows partition or will it always hand over to the XP boot loader?... (comp.os.linux.setup)
Re: changing default os in grub ... > I've just installed a 2.6.8 kernel in Sarge and was ... > hoping the adjustment to grub would return Sarge to ... # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ... # This entry automatically added by the Debian installer for an existing ... (Debian-User)