Warning: /dev/hdb1 is not on the firstdisk

Whats up!

I installed RedHat on my Second Harddrive on my machine. Windows 2000 on the first Harddrive. I used windows bootloader on the MBR using this site as my reference!
http://www.littlewhitedog.com/reviews_other_00011.asp

Everything worked properly. Then i decided i needed a newer Recompile kernel to 2.4.18. But when i added it to my lilo.conf file and ran the /sbin/lilo i got 2 errors.

Warning /dev/hdb1 is not on the first disk
Fatal: Map segement is too big,

Here is what my lilo.conf file looks like!!
XP=NTFS=HDA2
Linux=EXT=HDB1
#############################
prompt
timeout=90
default=Linux
boot=/dev/hdb1
map=/boot/map
install=/boot/message
linear

image=/boot/vmlinuz-2.4.18-3
label=linux
initrd=/boot/initrd-2.4.18-3
read-only
root=/dev/hdb1
append="hdc=ide-scsi"
other=/dev/hda2
label=WindowsXP

image=/boot/bzImage
label=2.4.19
initrd=/boot/newinitrd-image
read-only
root=/dev/hdb1
append="hdc=ide-scsi

Update:
I fixed the MBR by booting into the recovery console and running:
fixmbr


But i still get those tow erros when running the lilo.conf file
/sbin/lilo

Warning /dev/hdb1 is not on the first disk
Fatal: Map segement is too big,


Any help on how to fix this?

If you're using the windows bootloader, is it necessary to also have LILO?
And where is it located? It's possible that , when you run /sbin/lilo, it is trying to put the
lilo bootloader in the wrong place.

Some times it may be good to have two bootloaders, one in the MBR, chained to a second one
perhaps on the first block of one of your partitions, but it complicates matters,
and I would try to see if one bootloader could handle the whole job.
:cool:

The problem with the boot Loader is fixed... Im using windows boot loader on the MBR but i still get those two errors when i run /sbin/lilo ??

How can i get rid of those?

Have you tried eliminating the reference to the new kernel
and trying it?
The first message about /dev/hdb not being the first disk
may be only informational, and not really an error.
It's the second one I would worry about.

Did you understand all that stuff on that site, about saving the
boot sector to a file and editing the windows boot.ini file?

Does it still boot ok with the old kernel?
:cool:

Ok this is what i got done soo far:
Windows Loader is on the MBR soo when i restart it lets me chooose(i ran fixmbr from the recovery console)
"Windows XP"
"Linux"
When i choose Linux
Lilo's boot loader comes up and lets me pick between
"Linux"
"WindowsXP"
"2.4.19"
Everything seems to be booting properly i mean all kernels and windows boots up properly .And "WINDOWS loader is on the MBR" soo everthing looks fine but when i run "/sbin/lilo" i get these 2 errorS:

Warning /dev/hdb1 is not on the first disk
Fatal: Map segement is too big <---------

Soo the first error is just a message? But the second one is somethig i should worry about here is what my lilo.conf file looks like right now: Soo what im saying everyhting seems to be working properly and how i want it :

prompt
timeout=150
default=linux
boot=/boot/map
install=/boot/message
linear

image=/boot/vmlinux-2.4.18-3
label=linux
initrd=/boot/initrd-2.4.18-3
read-only
root=/boot/hdb1
append="hdc=ide-scsi"
other=/dev/hda2
label=WindowsXP

image=/boot/bzImage
label=linux
initrd=/boot/newinitrd-image
read-only
root=/boot/hdb1
append="hdc=ide-scsi" !

:D I know one way to solve the 1 error messages is to stop running /sbin/lilo and i then i wont see any errors? :D but could that message casue me problems later if i leave things how they are right now?

I don't know, but if you can boot OK from windows or from
either linux kernel, then lilo must have installed properly
in spite of the messages.

Since you only run /sbin/lilo when you make changes to /etc/lilo.conf,
you may as well not worry about it until the next time you change kernels.

I ran that error message through a google search and found a lot
of people asking about it but few answers. One answer that came up
occasionally was "use GRUB instead of LILO"

In fact, it may be just as well to put GRUB on the MBR of /dev/hda
and let it be the sole boot loader. I think some people here have
said they do it that way. I have GRUB on /dev/hda with WIN98 on
/dev/hda1 and Red Hat 7.2 on /dev/hdb, but Win98 is more compliant
with dual booting (IMO), so maybe it's not the same as WIN2000
in that respect.
:cool: