Hi folks, am stuck,

Am working on a system that is running suse 9.3 but the system grub can no longer boot suse 9.3.
The system root partition has reiserfs file format at /dev/hda4
I have tried to reinstall grub using the following procedures but am still not yet sorted.

mount -t reiserfs -o rw /dev/hda4 /mnt
chroot /mnt
grub-install /dev/hda

grub-install /dev/hda4 -outputs the same result as the later.

On pressing the enter key, the prompt runs the statement below.
grub-install can't find the corresponding BIOS drive.

I have tried out tips including the one below but the journey still looks untouched. It's now getting me crazy.

Originally on booting the system could load grub prompt & below is how i dealt with it,
i.e
grub> rootnoverify (hd0,3)
grub>makeactive
grub>chainloader 1
grub> boot

On booting, the system reloads the grub prompt i.e grub>
Could anyone on this platform share with me on how i can rectify the crazy grub such that am able to load suse 9.3 normally without performing an update to suse 10 or even using cd1 [boot diskette] always to boot suse.

thx.
Roy

Can you not repair the bootloader from CD1 on 9.3?

What changes did you make that caused the grub to stop working?

Hi Jongi
Well i tried to auto repair the system from CD 1 but there are No changes made to the system.
Auto repair doesn't cause any changes therefore.

And am not sure what happened to the system to damage it's grub because am just helping out
to rectify this error.

Hey guys has some one out there got a solution he can share with me about my problem/ fix or i post this to the general forum?

Thx

i normally will use installation CD1 to manually boot into this partition to see whether it's ok or not.

to manually boot into your partition, /dev/hda4 in your case, choose manual install for the first screen from CD and choose proper options.

when this is ok, we know that it's bootloader issue and we can start from there
use grub to fix itself
use windows bootloader
try to install a small linux OS to fix grub and use this one (so that your bootloader is on its own and won't be affected at all

if not, when there is no hardware problem, i doubt this because your partition number somehow messed. use fdisk to fix partition number. i have this doubt because normally hda4 will be your extended one and one cannot use it directly - you need to use a logical partition instead. it's rare but happens as i did myself, that hda4 is a primary one.

hope this helps, shen

What have you done before the system stopped booting? Usually systems don't just break. If they do, you must assume a hardware failure of some kind. Does 'fdisk -l' show you root partition?