LinuxQuestions.org
Review your favorite Linux distribution.
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 08-22-2006, 07:46 PM   #16
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15

There are breaks between change-rules and reset, It was just a pasting error i didn't catch
 
Old 08-22-2006, 08:50 PM   #17
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
Repost of Topic Starter

To reduce amount of page-flipping:

I've been using a dual boot configuration successfully for about a year now, with the exact same distro that I'm trying to work with now.
After getting an error about my NVIDIA card that I couldn't seem to fix, I decided to reinstall Linux (specifically Slackware 10.2) from my install CDs.

Eveything went well during the install, or so I thought. Now when I boot, I get:
"Boot From CD"
I wait, don't do anything, and then...
"DISK BOOT FAILURE."
I've tried fixing the MBR with the XP Bootdisk and reinstalling lilo, making sure to /sbin/lilo afterwards.

Here's the strange part (at least it seems strange to me):
After trying numerous things, I discovered that LILO will work, but only if the XP CD is inserted!

From that screen, I am able to boot normally into Windows or Linux.
I've dual-booted my system before, and never had this issue.

Before I disabled "Boot Other Device" from the BIOS, some sort of NVIDIA Boot Loader was coming up, but it never took me to a Boot Selection screen or anything.

One error message I noticed, unsure of its importance,
"Warning: Boot sector and map file are on different disks"

I've "fixmbr"-ed from the XP Rescue CD and reinstalled lilo with liloconfig several times, but always the same "DISK BOOT FAILURE" result.

My lilo.conf has boot set to /dev/hda (the boot sector of my first drive/MBR)
I even ran the lilo GUI from within KDE and it found no errors in the lilo.conf file

My boot order is
CD-ROM
HDD-0 (Windows Drive)
HDD-1 (Linux Drive)

I've also tried this with the Linux Drive in first position, then CD-ROM, then Windows, still the same dead end.

If I can be of further assistance, please let me know. I'm pulling my hair out!

Thanks guys, for all your help,
Eric
 
Old 08-23-2006, 10:12 AM   #18
Randux
Senior Member
 
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705

Rep: Reputation: 54
Is this fixed?
 
Old 08-23-2006, 10:51 AM   #19
jstephens84
Senior Member
 
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098

Rep: Reputation: 102Reputation: 102
I don't think it is.
 
Old 08-23-2006, 10:56 AM   #20
Randux
Senior Member
 
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705

Rep: Reputation: 54
I thought it might be when he said:

> There are breaks between change-rules and reset, It was just a pasting error i
> didn't catch

So if it's still broken, then we need to see the lilo command invocation and the output.
 
Old 08-23-2006, 04:24 PM   #21
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
Sorry for the miscommunication guys. The problem IS NOT fixed. What I meant by that post was that when I had pasted my lilo.conf, a couple line breaks were left out. The post was to avoid someone thinking "Oh, the idiot has 3 commands on the same line. No wonder it's not working!"

I've been doing research on this forum and others, and it seems everyone else solved this by altering the jumper on their drive in some way. However, I haven't touched my drives or added new ones since the last install was working, so I don't think that is the issue. I'm going to boot over to Linux now (i'm in XP writing this) and i'll give you the output you're asking for. Un momento...

Last edited by plinko; 08-23-2006 at 04:39 PM.
 
Old 08-23-2006, 04:37 PM   #22
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
Code:
root@efost:~# lilo -v- t- -b /dev/hda

LILO version 22.5.9 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.

Ignoring entry 'boot'
Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda
Using MENU secondary loader
Calling map_insert_data
Warning: The boot sector and map file are on different disks.

Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added Windows *

Boot image: /boot/vmlinuz
Added Linux

The boot sector and the map file have *NOT* been altered.
Then, I write it to the MBR, per your instructions

Code:
root@efost:~# lilo -v -b /dev/hda
LILO version 22.5.9, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.

Ignoring entry 'boot'
Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda
Using MENU secondary loader
Calling map_insert_data
Warning: The boot sector and map file are on different disks.

Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added Windows *

Boot image: /boot/vmlinuz
Added Linux
But still the same error.

I know it's probably going to be a really simple fix, but I appreciate you all taking the time to help me.
 
Old 08-23-2006, 04:45 PM   #23
jstephens84
Senior Member
 
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098

Rep: Reputation: 102Reputation: 102
Just by looking at your errors your boot loader seems a little shaky. When you install linux where do you place lilo at?
 
Old 08-23-2006, 04:59 PM   #24
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
I selected the MBR option during install
 
Old 08-23-2006, 05:06 PM   #25
jstephens84
Senior Member
 
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098

Rep: Reputation: 102Reputation: 102
Well that blows that idea away. The only recommendation I have is to reinstall XP first then install Linux again.
 
Old 08-23-2006, 05:09 PM   #26
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
It's just so strange that I haven't changed anything hardware-wise since my last install (approx. 1 year ago), but suddenly upon reinstall it won't work. Weird.
 
Old 08-23-2006, 05:11 PM   #27
jstephens84
Senior Member
 
Registered: Sep 2004
Location: Nashville
Distribution: Manjaro, RHEL, CentOS
Posts: 2,098

Rep: Reputation: 102Reputation: 102
Can you remember the last change that you made before this happened. Any software install, any major configuration changes.
 
Old 08-23-2006, 05:52 PM   #28
Randux
Senior Member
 
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705

Rep: Reputation: 54
I would not reinstall anything...did you modify your lilo.conf as I suggested yesterday? The example you showed had some problems in it.

Edit: sorry I see that you did change it.

The only other things I would say are:

* get rid of change rules reset unless you know what it does and have
a reason for using it. I don't have it in my lilo.conf.

* set the BIOS boot order to boot first from the drive where lilo is
in the MBR

When you have bootloader problems they're almost always fixable easily. Don't ever reinstall winbloze or a distro unless you like wasting time and losing data.

Last edited by Randux; 08-23-2006 at 06:06 PM.
 
Old 08-23-2006, 08:46 PM   #29
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
Unfortunately I got your message after reinstalling Slackware. Even THAT didn't fix the problem.I'll post my current lilo.conf and /etc/fstab, both of which are untouched (except for the change you suggested in your last post (removing 'change-rules' and 'reset').

I've also tried all possible hard drive combos in my BIOS, still no luck. Made SURE to install it to the MBR, so as not to create any new problems.

Before reinstalling Slackware, I even went so far as to try 'fixmbr' and 'fixboot' from my XP Rescue disk. No luck there, either.

I was thinking on it, and I might have accidentally picked the "Root" option in the lilo setup the first time I ran it. However, I formatted the partitions associated with Linux before the current reinstall, so I would think that would've cleared the problem, right?

However, as it stands, I still have to have the WINDOWS Rescue CD to get to LILO. Am I the only one who finds that concept mind-blowing?

Regarding jstephens' post:
The error occurred from first boot of my fresh install at the beginning of this whole fiasco, so I had no chance to change anything Now for the brand-spanking new files. fstab is unchanged since latest install, lilo.conf change listed above.

/etc/lilo.conf:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 600
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
  label = Windows
  table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb1
  label = Linux
  read-only
# Linux bootable partition config ends
/dev/fstab:
Code:
/dev/hdb5        swap             swap        defaults         0   0
/dev/hdb1        /                ext2        defaults         1   1
/dev/hdb6        /usr             ext2        defaults         1   2
/dev/hdb7        /opt             ext2        defaults         1   2
/dev/hdb8        /home            ext2        defaults         1   2
/dev/hda1        /win-c           ntfs        ro               1   0
/dev/hdc1        /win-e           ntfs        ro               1   0
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
Thanks for not giving up, guys. I owe ya one.
 
Old 08-23-2006, 08:48 PM   #30
plinko
Member
 
Registered: Dec 2005
Posts: 31

Original Poster
Rep: Reputation: 15
Typo in previous post. should be /etc/fstab. My apologies.

Hopefully one of you has the solution in the ol' noggin somewhere

Last edited by plinko; 08-23-2006 at 08:50 PM.
 
  


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
WinXP/Slack (LILO) Casket Linux - Newbie 7 10-16-2005 08:42 AM
Slack 10.1 -- Mouse issue / X11 issue Pozican Linux - General 4 04-19-2005 04:44 AM
installed GRUB over winxp slack and mandrake and LILO insyte LinuxQuestions.org Member Success Stories 0 08-12-2004 02:04 PM
LILO and MBR with WinXP a_priebe47 Slackware 26 08-05-2004 05:13 AM
LILO, WinXP and Slack 9.0 - need help flame Slackware - Installation 4 02-08-2004 04:33 PM


All times are GMT -5. The time now is 01:29 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