There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
Linux and Unix
Tag Cloud
access acer asus bios bsod computer crash driver drivers error ethernet excel freeze gaming google gpu hard drive hardware hdmi internet laptop malware memory missing monitor motherboard network operating system printer problem ram registry router slow software sound trojan ubuntu 11.10 uninstall usb video virus vista wifi windows windows 7 windows 7 32 bit windows 7 64 bit windows xp wireless
Search
Search for:
Tech Support Guy Forums > Operating Systems > Linux and Unix >
Urgent: Need to Re-Install a Bootloader

Reply  
Thread Tools
Omega_Shadow's Avatar
Senior Member with 4,324 posts.
 
Join Date: Aug 2004
Location: Somewhere south of Hell
Experience: Bringing Linux to the Masses
12-Apr-2006, 05:23 AM #1
Exclamation Urgent: Need to Re-Install a Bootloader
I am currently in a LiveCD session of PCLinuxOS. I just got this distro and liked how it worked so I decided to install it along side my Mandriva install. That did a number on my bootloader. Can't boot anything except this LiveCD. When my computer starts all I get after post is

99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99

So I am taking the hint that my bootloader is toast. This is a very bad thing as I did not want to spend my day off in front of a keyboard. But it does have a silver lining as I wanted to know how to install a bootloader from scratch since my dive into linux.

I have downloaded a tar-ball for a bootloader called grub-gnu and did the usual "./configure" "make" "make install" in the console, but don't know what to do next. I would welcome any help at this point. Any tidbits on how bootloaders work and how to properly configure them would be a bonus.
__________________
I'm not here. I am just more likely to be here then not be here. It's physics, I don't expect you to understand.
lynch's Avatar
Senior Member with 1,962 posts.
 
Join Date: Aug 2002
Location: Back East,Way Back East
12-Apr-2006, 06:10 AM #2
Mandriva and the Mandriva-based PCLinuxOS use Lilo as the bootloader by default. If you can boot with the 1st Mandriva disk and get a terminal, you should just have to type /sbin/lilo to have in restore itself. There may be an option to restore Lilo, IIRC.
lynch
Omega_Shadow's Avatar
Senior Member with 4,324 posts.
 
Join Date: Aug 2004
Location: Somewhere south of Hell
Experience: Bringing Linux to the Masses
12-Apr-2006, 01:22 PM #3
tried that already. It just gave me an error.

I would rather learn how to install a bootloader from scratch then persueing the "auto-fix" solutions. Gotta learn this if my next system is going to have 10+ distros on it
Nurdle's Avatar
Computer Specs
Senior Member with 148 posts.
 
Join Date: Nov 2005
Location: UK - West Midlands - Redditch
Experience: Intermediate
12-Apr-2006, 01:34 PM #4
Is this any help to you m8?

http://www.thinkwiki.org/wiki/How_to_setup_boot_loaders

As a side note....
Check your inbox
saikee's Avatar
Senior Member with 3,409 posts.
 
Join Date: Jun 2004
Location: Newcastle
Experience: A Linux user gone nuts on multi-boot
12-Apr-2006, 07:52 PM #5
All the answers are in my last link of the signature.

In your case Task B3 refers.

When LIlo fails you should see 99 or L on the screen. Just restore the boot loader like you do it for the Windows MBR. Pretty routine stuff.
killfactory's Avatar
Junior Member with 1 posts.
 
Join Date: Apr 2006
24-Apr-2006, 02:01 PM #6
B3 worked wonders for my errors. used auditor live cd. had to mount hda5 in my case.

Thanks Saikee!
Serge_N_Gin's Avatar
Computer Specs
Senior Member with 613 posts.
 
Join Date: Sep 2004
Location: Tassie
Experience: Intermediate
29-Apr-2006, 06:42 AM #7
What happened in your case, Omega_Shadow ? ? ?

'Cos I got those pesky 99's too, after I installed Mandriva 2006.

I got the Saikee link thing too when I posted, but I'm a noob and the info was way too advanced without a hand holder.
Omega_Shadow's Avatar
Senior Member with 4,324 posts.
 
Join Date: Aug 2004
Location: Somewhere south of Hell
Experience: Bringing Linux to the Masses
30-Apr-2006, 01:48 AM #8
oh, sorry, forgot about this thread. Messing around in the consoles I figured out that I overwrote my mandriva install when I installed PCLinuxOS instead of having them co-exist. I ended up saving my user information with the PCLinuxOS live CD and wiped the the "/" partion and started new with a fresh install of PCLOS

Let me know your situation and status. I would be happy to guide you though it
__________________
I'm not here. I am just more likely to be here then not be here. It's physics, I don't expect you to understand.
saikee's Avatar
Senior Member with 3,409 posts.
 
Join Date: Jun 2004
Location: Newcastle
Experience: A Linux user gone nuts on multi-boot
01-May-2006, 07:24 AM #9
ilovedonna,

Restoring a boot loader, be it a Windows, Linux Grub or Linux Lilo, requires overwriting the Master Boot Record (MBR) which is the first 512 bytes of the first bootable hard disk.

For Lilo (same for Grub) the standard way is to boot up "another Linux" first. Create a tempoarary subdirectory on its /mnt directory, mount the Linux partition that has a failed Lilo (or Grub), change root to it and restore the boot loader with the command
Code:
lilo -b /dev/hda
I am sorry that I can't make it simpler but the fact of the matter is any Linux user can boot up a LIveCD and therefore can slavage another Linux with it.

Change root, with "chroot" command, is to jump from Linux A to Linux B thereby a Linux user can work inside the distressed Linux B with a failed boot loader.

Lilo is hard-coded boot loader that cannot tolerate any change to its system settings or responding back with a screenful of 99 display. Therefore to survive in Linux one must know how to get Lilo back and this is easily done by Lilo's own command with "-b" parameter with the designation "/dev/hda" indicating the device hard disk "hda" meaning the MBR.

The above "lilo -b /dev/hda" simply instructs Lilo to replicate itself in the MBR.

If you still have a problem with it list here the content of
Code:
fdisk -l
so that we know your partitioning arrangement and give you the precise instructions/commands if needed. At this moment we can't adivise which partition to mount..
Reply

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Search Tech Support Guy

Find the solution to your
computer problem!




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.
Thread Tools



Facebook Facebook Twitter Twitter TechGuy.tv TechGuy.tv Mobile TSG Mobile
You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -4. The time now is 10:06 AM.
Copyright © 1996 - 2011 TechGuy, Inc. All rights reserved.

Powered by Cermak Technologies, Inc.