I have killed my first HDD and likely the bootloader was installed there. Is there any posibility to install a Botlader no metter which out of the konsole? because actually i have another problem (watch here), but it would be very nice if i had one problem fixed.
Hi Jilly. I suggest you use the installation DVD to reinstall a bootloader:
Step 1 - Assisted Boot into openSUSE: Insert Suse’s installation CD/DVD and reboot the computer. On the boot screen choose to “Repair Installed System”. Wait for three choices and select “Expert Tools”. Then click option “Install New Boot Loader”. Select the partition where you installed Suse (if asked). You’ll get the Grub GUI setup screen. Check under the Tab “Boot Loader Installation” that the checkmark is in “Boot from Master Boot Record” and remove any other checkmarks. Click “Finish”. Wait for message “The boot loader was installed successfully”. Click OK → Next → Finish. Ignore any error messages and reboot. That should install an elementary Grub and allow you to boot to openSUSE. So do that and it will take you to step 2
Step 2 - Reinitialise and Reinstall Grub: Once Suse has fully booted and settled down, go to Yast → System → Boot Loader. The Grub configuration screen comes up with the Tab “Section Management” activated. In the lower right is a drop-down selector labelled “Other”. Select from “Other” the option “Propose New Configuration” and then wait for Grub to analyse your partitions and display a new configuration. This may take a while. Important: When that finishes, activate the tab labelled “Boot Loader Installation” and select to “Boot from the Master Boot Record”. [Yast will often default to booting from the root or boot partition rather than from the MBR but that’s for experts only – always choose the MBR.] Then click Finish to save the changes and install the reconfigured Grub into the hard drive’s MBR. If you get a message that "The bootloader boot sector will be written to a floppy disk … don’t bother with the floppy – just click OK to proceed and install to the MBR. Reboot and you should be able to boot to openSUSE using the Grub menu screen.
The quote comes from here:
GRUB Boot Multiboot openSUSE Windows (2000, XP, Vista) using the Grub bootloader.
thanks for your help. I tried the first step already, but when i want to quit the install programm i get an error message, and still habe no bootloader.
But when i have the CD insertet while booting i can choose boot from Harddisk then i geht gurub bur only with one entry. Anyway thats thw way i am starting Suse at the moment.
Which version of Suse are you using?
Im running suse 11.0 kernel 2.6.25… -pae
the kernelversion on the CD is perhaps an other one… 2.6.15
Seems like my suse CD has crashed, because now it prints an error message while loading the kernel when im trying to repair the system.
I’ll search for an other one.
But still, is there the possibility to install and configure a bootloader only with the console? I’m sure there is a way, but can samebody explane it to me?
Can you run memtest86? Bad RAM might be the source of your problems. Perhaps re-seating of modules, removal of dust, which may clog fans and heat sinks, basic maintenance can sometimes heal.
Killed disks often aren’t, really dead. Sometimes they have corrupted partition tables, and then pass drive fitness tests. In such cases, if you don’t have sfdisk(8) dump of the partition table, gpart(8) can help build a suitable one, though data recovery may require a deep understanding to correct the table.
I’ll try memtest as fast as possible.
No i think mine is pyhsically demaged because it told me befor it crashed that some sectors wuold be unreadable and unwriteable.
I would check the disk with the Repair Installation system on the OpenSUSE install media. That runs in RAM so the disk state should not cause the repair system to crash. If you have bad RAM, then well, it won’t work. If your disk passes, then it will rebuild the bootloader subsystem also.
And BTW, the Repair Installation system is also useful when migrating a disk with a working installation to another motherboard because it figures out what modules are needed to support the disk controller in its new environment, and what the disk paths are, then rebuilds the initrd and grub entries. I just used it today to help a friend move his disk to another box.