LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-14-2011, 01:42 PM   #1
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Rep: Reputation: 48
Crashed my shiny new Slackware system into the 99 error wall.


Moderator:

pls delete this post if I should not do this as it is included in http://www.linuxquestions.org/questi...config-856322/


How do I recover from the 99 error when I start my system?

I can only get to my Slackware by booting into it from the Slackware DVD.

I have re-run lilo but I keep getting the 99 error on start up.

Any help would be appreciated,
 
Old 01-14-2011, 03:04 PM   #2
Ramurd
Member
 
Registered: Mar 2009
Location: Rotterdam, the Netherlands
Distribution: Slackwarelinux
Posts: 555

Rep: Reputation: 75
Does this thread solve your issue?

http://www.linuxquestions.org/questi...9-99-a-382997/

With this:
Quote:
I booted from my Slackware install DVD. At the boot: prompt, I booted into my Slackware on sda8 where I selected KDE and logged in as root.
You mean that at the prompt you did:
Code:
huge.S root=/dev/sda8 noinitrd
or something similar?

Did that allow you to boot up correctly?
can you save the output of the last time you ran lilo?
Have you tried lilo -M
 
1 members found this post helpful.
Old 01-14-2011, 04:06 PM   #3
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Original Poster
Rep: Reputation: 48
Yes, I did very close to this:

huge.S root=/dev/sda8 noinitrd


Did that allow you to boot up correctly?: I think so, but Kword & Kspread (maybe more) don't work.

can you save the output of the last time you ran lilo?

I have this:

Code:
bash-4.1# lilo -v -t -b /dev/sda8
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:44:48 on Feb 16 2010

Warning: Ignoring entry 'boot'
Reading boot sector from /dev/sda8
Warning: Unable to determine video adapter in use in the present system.
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Calling map_insert_file

Boot other: /dev/sda1, on /dev/sda, loader CHAIN
Added Windows_XP *

Boot image: /boot/vmlinuz-generic-smp-2.6.33.4-smp
Mapping RAM disk /boot/initrd.gz
Added Slack_Generic

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-2.6.33.4-smp
Added Slack_Huge

The boot sector and the map file have *NOT* been altered.
3 warnings were issued.
bash-4.1#

Have you tried lilo -M: No, I have not tried this yet, should I??

Thanks,
 
Old 01-14-2011, 04:19 PM   #4
cin_
Member
 
Registered: Dec 2010
Posts: 266

Rep: Reputation: 23
LILO or Kernel

Sounds like either LILO or the kernel are corrupt, as booting from the DVD oversteps LILO and also comes with a stock kernel.

Possible solutions... re'configure LILO
Once booted up with DVD run lilo command...
Code:
# lilo
# liloconfig
..remove LILO and reinstall
Code:
# pkgtool
*NAVIGATE PKGTOOL REMOVE PROCESS
# cp /DVDdir/slackware/a/lilo-22.8.i468.txz /home/
# cd /home
# pkgtool
*NAVIGATE PKGTOOL CURRENT PROCESS
# rm lilo-22.8.i486.txz
...remove LILO and install GRUB or GRUB2.
Code:
# pkgtool
*NAVIGATE PKGTOOL REMOVE PROCESS
# cp /DVDdir/slackware/extra/grub/grub-0.97.txz /home/
# cd /home
# pkgtool
*NAVIGATE PKGTOOL CURRENT PROCESS
# rm grub-0.97.txz
# grub-install
... or download the tarballs for GRUB2 and do your own compilation and configuration.

If one or none of these work, you should either configure your own kernel, http://www.gentoo.org/doc/en/handboo...?part=1&chap=7, or copy one from the DVD and place in your /boot/ folder.
Code:
# cp /DVDdir/kernels/hugesmp.s/* /boot/
... and use this bzImage as kernel when booting.

Last edited by cin_; 01-14-2011 at 04:41 PM.
 
1 members found this post helpful.
Old 01-14-2011, 04:34 PM   #5
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,971

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Hello,

you could chroot from the booted DVD into your Slackware, (provided /dev/sda8 is your Slackware / partition) do this
Code:
mount /dev/sda8 /mnt/tmp
mount -t proc none /mnt/tmp/proc
mount -o bind /dev /mnt/tmp/dev
chroot /mnt/tmp /bin/bash
source /etc/profile
then you can issue the lilo command. If it runs without error, don't forget to leave the chroot-environment with the exit command before rebooting.

Markus
 
1 members found this post helpful.
Old 01-14-2011, 10:34 PM   #6
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Original Poster
Rep: Reputation: 48
Thanks to everyone.

I am away from my comatized PC until Monday and will try to revive it then.
 
Old 01-15-2011, 02:58 PM   #7
Ramurd
Member
 
Registered: Mar 2009
Location: Rotterdam, the Netherlands
Distribution: Slackwarelinux
Posts: 555

Rep: Reputation: 75
The 99 error means, according to
Code:
man lilo
Quote:
99 invalid second stage index sector (LILO)
...
Errors 99 and 9A usually mean the map file (-m or map=) is not readable, likely because LILO was not re-run after some system change, or there is a geometry mismatch between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS (one of the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).
Read more in man lilo, it's a nice source of information.

Anyway, checking how /etc/lilo.conf looks (after your boot from dvd with root=/dev/sda8), and validating that output to be correct, lilo -M will install a new MBR. Also check that /boot/System.map is correct and actually points to an existing file or is a valid file itself.)

If in doubt, you can re-install the kernel from your dvd and rerun lilo again. That should fix your problem.
 
1 members found this post helpful.
Old 01-15-2011, 03:16 PM   #8
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,768

Rep: Reputation: 477Reputation: 477Reputation: 477Reputation: 477Reputation: 477
'lilo -v -t -b /dev/sda8' -Uh, the '-t' tells lilo to only test and not really do anything...
 
1 members found this post helpful.
Old 01-15-2011, 06:41 PM   #9
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 213

Rep: Reputation: 43
'lilo -v -M /dev/sda'
Try this and reply on your results.
PS. change command to right drive/partition.

Last edited by Nille_kungen; 01-18-2011 at 02:21 AM.
 
1 members found this post helpful.
Old 01-17-2011, 07:43 AM   #10
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Original Poster
Rep: Reputation: 48
Hello:

I am marking this thread as SOLVED.

As I also had LMDE installed, I used it's Live-CD to reinstall grub, i.e. replace lilo.

This got my boot menu back with all my systems listed: windows xp, LMDE and Slackware.

My only concern is that I have somehow corrupted my Slackware installation so I plan to copy the huge & generic kernels, from the DVD, to my system.

Thanks again for your help,
 
  


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
wall hangs on tty_write system call for about 15 minutes on debian 2.6 kernel kspradhan Linux - Server 1 08-30-2008 06:02 AM
wall hangs on tty_write system call for about 15 minutes on debian 2.6 kernel kspradhan Linux - Newbie 1 08-22-2008 10:10 PM
Slackware 11 and shiny new dual core CPU's TL_CLD Slackware 8 01-02-2007 01:02 AM
Crashed file system jonthelam Red Hat 4 09-30-2004 01:04 PM
System crashed... d_kote23 Linux - Newbie 2 05-12-2004 10:04 AM


All times are GMT -5. The time now is 10:32 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration