Mbr

[scottie924]

I got Linux installed but then I couldn't get into windows. It just flashes "L07 07 07 07 07..." but the rescue part of the install CD that will reload the windows boot loader doesn't work. Any ideas how to fix this? I need it fixed becuase I don't know how to set up my internet on Linux because I use HPNA through a USB port.

[jetblackz]

What distro and Windows?

http://jetblackz.freeservers.com/ConfiguringMultiBooting.html

Generally speaking, i would do a

dd if=/dev/hda1 of=/w2k.mbr bs=512 count=1

before Linux install. That's a Win2000 bootloader backup.

If you want to fix 2000, boot the 2kCD and go to recover console. Enter

fixboot
fixmbr

[scottie924]

I have Windows XP home Ed. and mandrake 9.0. I can get linux to start, but Windows is messed up. I am pretty sure its the MBR that is messed up because I accidently worte the boot loader to that and it didn't work. I went to the console on linux and I had it show the partitions and the first one said windows 98 and it should be XP. I think this is a problem, any ideas on how to fix it?

[jetblackz]

2k and xp are basically the same.

I've fixed both using the same method. Boot XP CD. You'll see. You may need admin password, though.

[sajchurchey]

Typically, w/ NT-based windows (such as 2k and XP) you have to isntall the bootloader to the "first sector of the boot partition," which you can usually set as an option other than MBR.

What does your bootloader config looklike?

What bootlaoader are you using?

We may be able to fix this.

[DMR]

Originally posted by sajchurchey
What bootlaoader are you using? The "L 07" error code indicates lilo.


Originally posted by sajchurchey
What does your bootloader config looklike?Yes, post the contents of /etc/lilo.conf. Also tell us exactly which drive(s) and partitions XP and Linux are installed on.

[2ndsign]

ok get a windows 98 or me floppy disk

boot with the floppy into dos.

use no cd support(you wont need it)

at a prompt type"fdisk /mbr"
(that resets your mbr)

now type "fdisk"
use large disk support
now choose the menu
set active partition

set your windows partition to boot!

restart, remove floppy!
hopefully you can boot into windows if not
its reformatting time!:(

if it boots now just reinstall gentoo

good luck!!

[scottie924]

boot=/dev/hda
map=/boot/map
default=linux
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
ignore-table
image=/boot/vmlinuz
label=linux
root=/dev/hdb2
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi quiet"
vga=788
read-only
image=/boot/vmlinuz
label=linux-nonfb
root=/dev/hdb2
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi"
read-only
image=/boot/vmlinuz
label=failsafe
root=/dev/hdb2
initrd=/boot/initrd.img
append="devfs=nomount hdc=ide-scsi failsafe"
read-only
other=/dev/hda2
label=NT
table=/dev/hda
other=/dev/fd0
label=floppy
unsafe


that is the contents of that folder, Windows is on C: (hda1) and Linux is on L: (hdb8 or 2 or 6 not sure?). How do I see my other hard drives from linux?

[2ndsign]

i use xosl 115 to boot from different hard drive

youll still will probably do what i had mentioned!

if you get xosl read carefully, put only on dos partion when asked.

im boot 3 linux Oses(hda)
and win98SE(hdb)

lilo doesnt see the windows only in mandrake so i use xosl instead.

xosl can support up to 24 Oses!:D

[DMR]

Originally posted by scottie924
Windows is on C: (hda1) If that's true, why does your Windows entry in lilo.conf reference hda2? --Originally posted by scottie924
other=/devhda2
label=NT
table=/dev/hda


Originally posted by scottie924
and Linux is on L:No, Windows cannot recognize Linux partitions, and therefore cannot assign them a drive letter.

Originally posted by scottie924
(hdb8 or 2 or 6 not sure?).
If you can boot into Linux from lilo, then the hdb2 designation used in your lilo.conf would be the correct partition.
Originally posted by scottie924
How do I see my other hard drives from linux?One thing at a time, we don't need to get into that yet.

What exact error do you get when you try to boot Windows (or where exactly does it fail)?

[scottie924]

When I try to boot windows, my computer goes through the POST, I'm pretty sure, and just puts L 07 07 07 after that on a blank screen
it doesn't say anything else

[DMR]

Sorry about asking for the error again, I spaced on the fact that it was in your first post.

You've got some sort of disk geometry problem, where lilo and the BIOS aren't agreeing on the cylinder/head/sector layout of one of your drives.

Did you add the second hard drive just prior to installing Linux, or had both dives been in the system for a while?

Does your BIOS correctly recognize both drives? The lilo README has this to say about the "07" error code:
0x07 "Invalid initialization". The BIOS failed to properly initialize the disk controller. You should control the BIOS setup parameters. A warm boot might help too.
Also, adding the "lba32" or "linear" option to the global section of lilo.conf might help. (The "global" section is the part before first "image=" line).

[scottie924]

I installed the new hard drive, got widows to notice it all, its a 200GB hard drive. Once I got that, after figuring out about partition magic it kept freezing. But then I installed linux and both OS's worked fine, then I tryed to reinstall linux to get different settings and I think I accidently told it to put the boot loader on the wrong partition.

How do I write to the /etc/lilo.conf file?

[DMR]

lilo.conf is a plain text file; you can use any text editor to change it.

In terms of where lilo is installed, the "boot=/dev/hda" entry in lilo.conf means that it's installed on the MBR of the Primary Master drive.

By the way, you did install the Master/Slave jumpers on each drive correctly, yes?

[scottie924]

Yes, the jumpers were set right, I have had it work with both OS's I just reinstalled linux and messed it up. While I was browsing the linux system, I found out that I can see all the files on my XP partition, I just can't boot into it, maybe this could help provide a path to fix the problem?

[DMR]

Originally posted by scottie924
I found out that I can see all the files on my XP partition, I just can't boot into it, maybe this could help provide a path to fix the problem? Yes, Linux understands Windows-formatted partitions, but reading your Win files probably won't help here.

What about the /dev/hda1 vs. /dev/hda2 discrepancy I mentioned in my ealier post? You can find out which partition Windows is really on by looking in your /etc/fstab file; there will be a line specifying which partition Windows is on, and which directory Linux mounts it in.

[scottie924]

/dev/hdb2 / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
/dev/hdb9 /home ext3 defaults 1 2
none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0
none /mnt/cdrom2 supermount dev=/dev/hdd,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0
/dev/hda2 /mnt/nt ntfs iocharset=iso8859-1,ro,umask=0 0 0
/dev/hdb5 /mnt/nt2 ntfs iocharset=iso8859-1,ro,umask=0 0 0
/dev/hdb6 /mnt/nt3 ntfs iocharset=iso8859-1,ro,umask=0 0 0
/dev/hdb7 /mnt/nt4 ntfs iocharset=iso8859-1,ro,umask=0 0 0
none /proc proc defaults 0 0
/dev/hdb8 swap swap defaults 0 0


I might be missing it but I don't see it on there. This is probably causeing the problem. Thanks for all the help and effort you are giving. I think the 'none /proc is where it was, cause I tried using the install disk to reinstall the windows boot loader and I remember seeing that. I should be getting a Windows XP recovery disk on monday, I would have had it thursday but HP sent me the wrong disk, it was XP pro.

[DMR]

/proc is a virtual Linux filesystem (it exists only in memory); you couldn't have installed anything on it.

<edit>hda2 and hdb5->hdb7 </edit> are your Windows (NTFS) partitions. Which one has the actual operating system on it?

Also, fstab makes no mention of a #1 partition for either drive (hda1, hdb1)- what's up with that? You can use the fdisk program to find out if need be.

[scottie924]

I know that I have two NTFS partitions on my first hard drive, and two on the second, then the three Linux mounts. Windows is on hda1. When I put the linux boot CD in the drive, it says f1 for setup or enter to install, if I hit f1 and then go to the console or something like that I can get a list of my partitions, it showed me a few days ago that I had windows 98 on a Fat 32 file system and on hda1, so I know that there is something wrong. How does the computer come up with hdb1,2,3,4 etc? if its in order, then hdb1 should be a 93GB partition that I'm using for music and movies.

[DMR]

I think you should replace the "hda2" reference in the "other=" line of lilo.conf with "hda1"; I'll bet that's where your Win installation lives.

Linux names drives and partitions on IDE devices as follows:

The drive names:
hda -> hdd : Primary Master, Primary Slave, Secondary Master, Secondary Slave

The partition names:

1-4 : 1st -> 4th Primary partitions (one of these can be an Extended partition)

If one of the above is an Extended partition, the Logical partitions you create in the Extended will always be numbered starting at 5.

For example:

hda1 : First Primary partition on Primary Master drive
hda5 : First Logical partition on Primary Master drive
hdb6 : Second Logical partition on Primary Slave drive
etc.,
etc.,

Run Linux's fdisk on both drives and see what it reports.

[scottie924]

I tried to edit the lilo.conf file in a text editor and when I went to save it, it says "Unable to make backup of the original file" and then "Unable to write to file".

[DMR]

-You need to log in as root to edit lilo.conf.

-Which editor?

-What information does fdisk give you for each drive?

[scottie924]

I changed the text file and it didn't change anything on the boot process. How do I do fdisk? I am just a newbie so I don't know how to do some stuff.

[DMR]

Originally posted by scottie924
I changed the text file and it didn't change anything on the boot process.Sorry, I forgot to mention that you need to re-execute lilo after you make changes to lilo.conf in order for those changes to take effect. As root, run:

/sbin/lilo

Originally posted by scottie924
How do I do fdisk?Type:
fdisk /dev/hda

At the "Command (m for help):" prompt type "p" (omit the quotes) to print hda's partition info on your screen. I'm pretty sure hda1 will be your Windows partition, but post the info that fdisk gives you just to be sure. Once you've got that info, type "q" to quit fdisk.

[2ndsign]

dude get the xosl 115 and read the documentation.


ill help you get your system up and running in no
time!

[scottie924]

When you say re-execute lilo, do you mean to restart the computer? Also where do you get to the command line? I went to something but I wasn't sure it if was right so I closed it. When you say run /sbin/lilo to run the root or whatever, I got into root by logging of and loging on using root at the user name. Would this have worked?

[dungscooperdave]

Okay, every time you edit /etc/lilo, you need to execute /sbin/lilo, which is a program designed to actually make the changes that you specified in /etc/lilo. Basically, what you should do is this: Open up a terminal, (If you're using either KDE or Gnome, click on one of the menus and look around for a terminal, like XTerm. They're not usually too hard to find.) and then type 'su' (without the quotes of course) and press enter afterwards. If prompted, enter in your root password, and then you're automagically logged in as root (in this particular terminal anyway). Now type '/sbin/lilo' (without the quotes again) and the changes that you specified in /etc/lilo will now be made to your hard disk. After running /sbin/lilo, type 'exit'. This will log you out of root, but the terminal should still be open, with you logged in as whatever user you were using before. Typing 'exit' again will usually close the terminal window, and you'll be all set. Reboot your box and the lilo boot menu should run just the way you told it to.

[scottie924]

[root@swbell scott]# fdisk /dev/hda

The number of cylinders for this disk is set to 7753.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/hda: 240 heads, 63 sectors, 7753 cylinders
Units = cylinders of 15120 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 611 4619128+ 12 Compaq diagnostics
/dev/hda2 * 612 7753 53993520 7 HPFS/NTFS

Command (m for help):


that is what it said. Also the editing the lilo.conf did not change anything. When I tried to boot windows, it just put L07 07 07, and linux booted the same way.

[dungscooperdave]

Originally posted by scottie924
Also the editing the lilo.conf did not change anything. When I tried to boot windows, it just put L07 07 07, and linux booted the same way.
Did you try this yet?
From My Above Post
Okay, every time you edit /etc/lilo, you need to execute /sbin/lilo, which is a program designed to actually make the changes that you specified in /etc/lilo. Basically, what you should do is this: Open up a terminal, (If you're using either KDE or Gnome, click on one of the menus and look around for a terminal, like XTerm. They're not usually too hard to find.) and then type 'su' (without the quotes of course) and press enter afterwards. If prompted, enter in your root password, and then you're automagically logged in as root (in this particular terminal anyway). Now type '/sbin/lilo' (without the quotes again) and the changes that you specified in /etc/lilo will now be made to your hard disk. After running /sbin/lilo, type 'exit'. This will log you out of root, but the terminal should still be open, with you logged in as whatever user you were using before. Typing 'exit' again will usually close the terminal window, and you'll be all set. Reboot your box and the lilo boot menu should run just the way you told it to.

[scottie924]

Yea I tried that. It didn't work. Any other ideas? HP should be getting me that disk pretty soon.

[DMR]

Originally posted by scottie924
Device Boot Start End Blocks Id System
/dev/hda1 1 611 4619128+ 12 Compaq diagnostics
/dev/hda2 * 612 7753 53993520 7 HPFS/NTFS Oh bugger- you've got that special Compaq diagnostic partition. Since that's the case, you're XP installation really is on hda2 instead of hda1. The Compaq partition might be causing trouble, but I'll have to look into that further to make sure.

Have you tried adding the "lba32" or "linear" options in the global section of lilo.conf yet? If not, do so. Only use one of the options at a time; if "lba32" doesn't work, remove it and replace it with "linear".

Again, don't forget to run /sbin/lilo after each change to lilo.conf.

[scottie924]

I just tried lba32 and linear and neither worked. lba32 didn't change the boot process and linear caused an error message about the disk being too big for it

[dungscooperdave]

Originally posted by DMR
Oh bugger- you've got that special Compaq diagnostic partition.
I was wondering what that was.....

[dungscooperdave]

Originally posted by scottie924
Yea I tried that. It didn't work. Any other ideas? HP should be getting me that disk pretty soon.
When you say it didn't work, what do you mean? Did it just give the same error message, or did it do something else?

[scottie924]

I tried lba32 and it didn't change anything in the boot process except instead of L07 it was L99 99 99 99 99 but still didn't load Windows. When I want to load windows, it loads into windows if I don't have the boot floppy in. If its in I go into linux.

[DMR]

Originally posted by scottie924
When I want to load windows, it loads into windows if I don't have the boot floppy in. If its in I go into linux. Could you describe that more specifically please?

[LinuxLuke]

Well, this thread had gotten pretty long... I'd personally ditch LiLo, and use GAG, I'm sure a google will turn up some hits on it, and from my experience Windows has to be on hda1 to save a lot of work.

[scottie924]

When I turn on the computer without a floppy disk it, it used to load windows until I messed it up. To get into linux, I have to put the floppy disk into the drive and it goes to linux. I tried installing linux on the MBR but it messed up like it is now and I reinstalled the windows boot loader and it fixed it. I tried to reinstall linux again but I accidently put the lilo in the MBR and now I can't fix it. I tried to reload the windows boot loader but it didn't work. I did something in the colsole of the rescue part of the Linux disk and saw something that said hda1 was windows 98 on a FAT 32 and hda2 was NTFS (which is correct) and hdb all numbers were right.

[scottie924]

Good news, I got the XP recovery disks. I put the first one in and it said something like, caution you will loose all data on all partitions I think, so I quit the program, and it went into windows. I havn't tried to restart without the disk but I bet it won't work. Any idea on how to fix this? Is there a way I could put something on a floppy that will allow me to choose the OS to load? Thanks for your help.

[2ndsign]

how many more post is it going to be before you fix this minor problem.

get the xosl 115 bootloader ok but i guess youll try another way after 100 post.


let me know when you're going to try it

very simple it is!!:D

[sharth]

huh?

[bs_texas]

golly.

That's what i was gonna ask.

[dungscooperdave]

Are you absolutely sure that trying to 'fixmbr', that is, trying to reload the Windows bootloader doesn't work? Can you try it again?

[scottie924]

I just tried to fix the windows boot loader. When I do it, it gives me two options, 1. LILO <hda> 2 LILO <hdb2>. Neither one works but when I do the first one and reboot, it exits and when it goes to reboot, it just goes to a screen with black, white, and grey vertical bars on the screen. Any ideas why this won't work? And about you guys who are trying to get me to use the other boot loader, I will try that, but I don't want to mess up my computer, again, for the 4th time. Can you give me the link to the site that I need go to download the xosl 115 bootloader.

[bs_texas]

Weird!!!!

When I posted after sharth above, the only other post I saw in the whole thread was the one from 2ndsign.

Now, all of a sudden, there are 2 previous pages of posts. :confused:

And the title of the thread was "gee wiz", not "Mbr".

[dungscooperdave]

Originally posted by scottie924
Can you give me the link to the site that I need go to download the xosl 115 bootloader.
You mean this site (http://www.xosl.org/)? I found it super easily on http://www.google.com/ . You should start using it more often. You won't regret becoming accustomed to using such a powerful tool.

[scottie924]

If I want to use that, will I have to reinstall the OS's? or can it be used with already installed OS's?

[scottie924]

If I use fdisk /mbr will it erase the MBR and rewrite it for Windows XP? Also would I type this in the console terminal?

[dungscooperdave]

Originally posted by scottie924
If I use fdisk /mbr will it erase the MBR and rewrite it for Windows XP? Also would I type this in the console terminal?
Typing 'fixmbr' from the Windows XP recovery console will erase the MBR and rewrite the Windows XP bootloader. To bring up the Windows XP recovery console (if it works the same way as Win2k), you stick your WinXP disc in the cdrom drive and reboot. Then it should boot off of the WinXP disc. Once it boots up, there should be a menu or option or something that says something like 'WinXP Recovery Console'. Selecting this will start up the WinXP Recovery Console. Once you're at the prompt, typing 'fixmbr' and pressing enter should fix your mbr so that you will then be able to boot up WinXp without any problems. Once you do this however, you won't be able to boot up Linux without a boot disk, so you might want to make a boot disk before you do this. That way you can reboot your computer with the boot disk in to start up Linux. Then setting up Lilo should, theoretically speaking, be able to setup your computer so that you can choose if you want to run Linux or Windows at boot time.

[dungscooperdave]

Don't get confused between the WinXP Recovery Console and the Linux console. They are two completely different things. The WinXP recovery console is used to fix your WinXP machine if you're having problems with it.

[dungscooperdave]

Originally posted by scottie924
If I want to use that, will I have to reinstall the OS's? or can it be used with already installed OS's?
I think it is used with your OSs already installed. You might want to back up your data first, though, just in case.

[2ndsign]

Originally posted by scottie924
If I want to use that, will I have to reinstall the OS's? or can it be used with already installed OS's?

the best bet for you is to reinstall xp (if ok leave alone)
then install linux on prepared partition
but install lilo in root partition not mbr

then install xosl

then set it all up!!:D

[sajchurchey]

Actually you should choose the option on installing lilo on first sector of /boot partition.