LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 03-07-2008, 10:17 PM   #1
okos
Member
 
Registered: May 2007
Location: California
Distribution: Slackware/Ubuntu
Posts: 609

Rep: Reputation: 38
Angry Lilo not recognized how can I get linux to boot?


I screwed up my system .
I have xp and slackware as a dual boot.
I was running out of room on my "/" root partition, hdc5 so I decided to make a bit more room by moving things over.
I defragged xp and reduced it by 1 gig. Moved my swap and reduced it to 800 mb. Then increased my "/" root partition by 1+ gig. Now my system wont boot. Grrrrrrr. Im currently running from a live cd.

When I boot my computer I only get this,"99 99 99 99 99 99 99 99 99."

How can I fix this? Your help would be much appreciated!

okos
 
Old 03-07-2008, 11:18 PM   #2
Junior Hacker
Senior Member
 
Registered: Jan 2005
Location: North America
Distribution: Debian testing Mandriva Ubuntu
Posts: 2,687

Rep: Reputation: 61
Changing the size of swap probably did her in. I use bootitng for my boot manager, I can move swap around and my Linux systems will boot and resume swap without editing anything, but I haven't tried changing the size of swap.
Some Linux may still keep track of the exact location of the partition on the drive and refuse to boot if they are not where expected.
Some Linux may not work if the start of the / partition's location has changed.
With my boot manager and the distributions I've installed, these issues are not an issue.
 
Old 03-07-2008, 11:51 PM   #3
Wim Sturkenboom
Senior Member
 
Registered: Jan 2005
Location: Roodepoort, South Africa
Distribution: Slackware 10.1/10.2/12, Ubuntu 12.04, Crunchbang Statler
Posts: 3,786

Rep: Reputation: 282Reputation: 282Reputation: 282
Personally, I don't think that the change of the swapsize is responsible for the 99. Reason is that the system (to my knowledge) has not even attempted yet to setup the swap.

Did you run lilo (as a command) after you made the changes?

If not, the following is what I would try (no guarantee whatsoever)
boot from slack CD and login (like with install)
mount hdc5
chroot to the directory where you mounted hdc5
run lilo
if no errors, reboot
else fix them in the lilo configuration file (no slack at hand, so not sure what the file is called (menu.lst? lilo.conf?))

hope it does the trick


PS make backups if your data is important

Last edited by Wim Sturkenboom; 03-07-2008 at 11:52 PM. Reason: added PS
 
Old 03-08-2008, 12:08 AM   #4
elsheepo
Member
 
Registered: Feb 2008
Location: Los Angeles
Distribution: Slackware-current
Posts: 86

Rep: Reputation: 19
I have a similar problem, trying to get rid of my windows partiton and merge the free space into my linux primary. ? any advice?
 
Old 03-08-2008, 12:29 AM   #5
okos
Member
 
Registered: May 2007
Location: California
Distribution: Slackware/Ubuntu
Posts: 609

Original Poster
Rep: Reputation: 38
Quote:
Originally Posted by Wim Sturkenboom View Post
Personally, I don't think that the change of the swapsize is responsible for the 99. Reason is that the system (to my knowledge) has not even attempted yet to setup the swap.
I agree
Quote:
Did you run lilo (as a command) after you made the changes?

If not, the following is what I would try (no guarantee whatsoever)
boot from slack CD and login (like with install)
mount hdc5
I am using backtrack live cd. It is the only live cd I have other then the slack12 install disks.
I tried the following:
Code:
cd /mnt/hdc5/sbin/
./lilo
I wanted to make sure to run the lilo from my hd and not from the cdrom. I am not sure if that makes any difference. I got the following error
Quote:
Fatal: raid_setup: stat("/dev/sda")
However I do not have a scsi drive. I tried just lilo and had the same error.

I am not shure about what you are saying here.
Quote:
chroot to the directory where you mounted hdc5
run lilo
Lilo is configured with lilo.conf. It just directs where the kernel is located
Quote:
if no errors, reboot
else fix them in the lilo configuration file (no slack at hand, so not sure what the file is called (menu.lst? lilo.conf?))
update--
I did the following command,
Code:
 chroot /mnt/hdc5 lilo
Warning: LBA32 addressing assumed
Warning: '/proc/partitions' does not exist, disk scan bypassed
Added Slack-2.6.24 *
Added Slack
Added XP
2 warnings were issued.
Im not sure about what the warning means or how to fix it.

Thanks okos
 
Old 03-08-2008, 12:38 AM   #6
okos
Member
 
Registered: May 2007
Location: California
Distribution: Slackware/Ubuntu
Posts: 609

Original Poster
Rep: Reputation: 38
Thumbs up Thanks a bunch!

update---
Hey it worked!

I really appreciate the help.
I also learned a new command chroot.

okos
 
Old 03-08-2008, 03:27 AM   #7
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287Reputation: 1287
Good to hear. Remember to run '/sbin/lilo' whenever you make changes to the kernel (like install a new one) or when you resize partitions.
 
Old 03-08-2008, 03:00 PM   #8
ararus
Member
 
Registered: Mar 2008
Location: UK
Distribution: Slackware
Posts: 56

Rep: Reputation: 15
Quote:
Originally Posted by okos
Im not sure about what the warning means or how to fix it.
The LBA warning should be harmless, unless you are using something with a really old BIOS (>10 years). You can get rid of the warning by adding the 'lba32' keyword to /etc/lilo.conf.

The /proc/partitions warning is just because you have chroot'd and there is no /proc mounted (in the chroot).

It's not a problem but is easily fixed as lilo has an option to chroot itself, -r, i.e.

Code:
/sbin/lilo -r /mnt/hdc5

Last edited by ararus; 03-08-2008 at 03:02 PM. Reason: typo
 
Old 03-08-2008, 05:48 PM   #9
okos
Member
 
Registered: May 2007
Location: California
Distribution: Slackware/Ubuntu
Posts: 609

Original Poster
Rep: Reputation: 38
Quote:
Originally Posted by H_TeXMeX_H View Post
Good to hear. Remember to run '/sbin/lilo' whenever you make changes to the kernel (like install a new one) or when you resize partitions.
The chroot was a new one for me.
I tried to run lilo on my hd by
Code:
cd /mnt/hdc5/sbin/
./lilo
But that did not work.

Quote:
You can get rid of the warning by adding the 'lba32' keyword to /etc/lilo.conf.
Just put "lba32" (without the quotes) in my lilo.conf and run lilo again?

Thanks guys!
 
Old 03-08-2008, 08:29 PM   #10
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,766
Blog Entries: 27

Rep: Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081Reputation: 2081
Hi,
Quote:
Originally Posted by okos View Post
The chroot was a new one for me.
I tried to run lilo on my hd by
Code:
cd /mnt/hdc5/sbin/
./lilo
But that did not work.



Just put "lba32" (without the quotes) in my lilo.conf and run lilo again?

Thanks guys!
The reason was that you had to change to the mount point of the chroot you desired.

The easiest way would be to use the install cd1 to boot the system as if you were going to install. Then after you get to the login from the cli (command line);

Code:
~#mkdir /slacktemp                   #temporary mount point
~#mount /dev/your_device /slacktemp  #this is the device you installed to
~#chroot /slacktemp                  #change to yours
~#cd /slacktemp/etc                  #change to directory with lilo.conf 
~#vi lilo.conf                       #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device     #sda, hda this will only test 
~#lilo -v -b /dev/your_device        #this will write MBR to your_device
You should now be able to re-boot your system.

BTW, you can add the lba32 then run 'lilo'.

Last edited by onebuck; 03-08-2008 at 08:30 PM.
 
Old 03-08-2008, 09:42 PM   #11
okos
Member
 
Registered: May 2007
Location: California
Distribution: Slackware/Ubuntu
Posts: 609

Original Poster
Rep: Reputation: 38
Cool Error removed!

I added lba32 to lilo.conf ran lilo and all looks great!

Thanks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
No errors from GRUB, LILO but boot sector not recognized shatteredllama Linux - Newbie 4 04-23-2007 10:45 PM
Dual Boot: Linux Boot Problems with LILO on Mandrake 10.0 verity Linux - General 7 10-13-2006 04:48 AM
Do I need Linux for lilo to boot windows? rebelscum Slackware 5 07-25-2005 07:22 PM
dual boot - XP and Linux - Need to reinstall XP without effecting linux -LILO boot godofmind Linux - General 1 05-05-2004 08:13 AM
triple boot with lilo(two linux and XP) rmanocha Linux - Software 24 03-24-2004 04:02 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:06 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration