LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
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 05-24-2004, 08:55 AM   #1
philos
LQ Newbie
 
Registered: Mar 2004
Location: Dallas
Distribution: Slackware
Posts: 7

Rep: Reputation: 0
boot problems (I think)


Wow. I've had Slackware installed for two days, and I've already managed to mess it up.

Okay, first, what I have....
Slackware 9.1
I use KDE when I feel the need for a GUI.
Slack is installed on a second hard drive (hdb1), and Win2k is on hda. Lilo was working just fine yesterday morning.

So, what's the problem? Glad you asked.

When I boot my computer, it goes through the initial couple screens, then the screen clears and brings up the first 'L' of 'LILO'. (I'm used to seeing it, I had mandrake installed previously on this hd, though I never used it, which is why I know what the L was) Anyway, then the screen fills up with '9A 9A' so that it looks something like this:
Quote:
L 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A 9A
You get the idea.

So, I boot with the boot disk I made when I installed Slack... It goes through the normal screens, until it comes to the following intimidating message...

Quote:
fsck 1.34 (25-Jul-2003)
/sbin/e2fsck: Is a directory while trying to open /
/:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsk with an alternate superblock:
e2fsck -b 8193 (device)

***********************************************************
*** An error occurred during the root filesystem check. ***
*** You will now be given a chance to log into the ***
*** system in single-user mode to fix the problem. ***
*** ***
*** If you are using the ext2 filesystem, running ***
*** 'e2fsck -v-y <partition> might help. ***
***********************************************************

Once you exit the single-user shell, the system will reboot.


Type control-d to proceed with normal startup,
(or give root password for system maintenance):
That's word-for-word, save the lack of proper spacing for the asterisk border (forums ignore whitespace).

I'm not a total n00b to Linux, but I'm a n00b to any kind of administration with Linux. Give me cd, give me ls, give me grep, give me rm, I'll hang with the best of 'em. Give me chmod, and I'll bring down the server. (you think I'm exaggerating, don't you? I really did that with our servers at work, which btw, also run off slack.)

So, um, yeah... Help... *whimpers softly* And to think I want to learn to do more stuff, like compile a kernel... *shudders at the thought*

-----------
edit: oh yeah. Since I figured the first problem was a Lilo problem, I tried to do what I could with it, using KDE (the command-line just blows my mind on it), which obviously got me nowhere. Then I tried the lilo -u, as a last resort, which, again, did nothing for me.

Last edited by philos; 05-24-2004 at 09:05 AM.
 
Old 05-24-2004, 12:54 PM   #2
DropSig
Member
 
Registered: Apr 2004
Location: East of Quebec
Distribution: Ubuntu, Centos
Posts: 208

Rep: Reputation: 30
I came accross this problem not long ago here is what i did:
Rebooted with slack cd
run the setup
installed a pkg i wanted to install for a while(You need to install something even if its nothing, otherwise the setup does not let you reconfigure your system, at least mine did not)
then reconfigure and reinstall lilo
ps.:do not overwrite you fstab or if you do make sure youve selected all your partition. (That just to make sur you dont come accross more problem after..)
That's it
worked for me hope it will help ya!
 
Old 05-24-2004, 01:23 PM   #3
philos
LQ Newbie
 
Registered: Mar 2004
Location: Dallas
Distribution: Slackware
Posts: 7

Original Poster
Rep: Reputation: 0
bleh

Well, that was looking very promising.

Then, when I told it to install Lilo, I got this...

Quote:
LILO INSTALL ERROR #1

Sorry, but the attempt to install LILO has returned an error, so LILO has not been correctly installed. You'll have to use a bootdisk to start your machine instead. It should still be possible to get LILO working by editing the /etc/lilo.conf and reinstalling LILO manually. See the LILO man page and documentation in /usr/doc/lilo/ for more help.
Hrm..
 
Old 05-24-2004, 02:04 PM   #4
DropSig
Member
 
Registered: Apr 2004
Location: East of Quebec
Distribution: Ubuntu, Centos
Posts: 208

Rep: Reputation: 30
What is in youre lilo.conf. can you print it on the board. it should be in /etc
If we can see it we should be more able to help you.
 
Old 05-24-2004, 02:25 PM   #5
philos
LQ Newbie
 
Registered: Mar 2004
Location: Dallas
Distribution: Slackware
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 #Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hdb1
#compact # faster, but won't work on all systems.
prompt
#timeout = 300
# VESA framebuffer console @ 800x600x256
vga = 771
# Normal VGA console
# vga=normal
# VESA frame buffer console at 1024x768x64k
# vga=791
# VESA frame buffer console at 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA frame buffer console at 800x600x64k
# vga=788
# VESA frame buffer console at 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA frame buffer console at 640x480x64k
# vga=785
# VESA frame buffer console at 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root =
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other =
label - Win2k
# map-drive = 0x80
# to = 0x81
table =
# DOS bootable partition config ends
 
  


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
dual boot problems, now no boot loader after fixmbr mipia Debian 2 04-04-2004 10:43 PM
Dual boot for Redhat 9 and Solaris 9 boot manager problems steve_2010 Red Hat 1 01-30-2004 10:14 PM
Kernel update boot problems, no boot loader StaticSage Red Hat 2 01-09-2004 07:05 AM
Boot problems, carn't boot Linux anymore Thom_Redhat Linux - General 2 01-01-2004 09:21 AM
Boot problems, NTLDR missing but trying to boot on second hard drive Outabux Linux - Newbie 0 04-09-2003 06:29 PM


All times are GMT -5. The time now is 12:27 AM.

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