troubleshooting Question

lilo lba32 boot problem (1024 cylinder problem)

Avatar of aCp
aCp asked on
10 Comments1 Solution741 ViewsLast Modified:
Hi experts.
I just bought a new maxtor HD (40 GB) and a PCI IDE controller so that I can use it, my motherboard being somewhat old. I managed to install linux on this HD (after a series of difficulties), anyway, the problem is now with lilo in booting all OSes installed.
On the 40 GB HD I have installed linux and then WinME.
On the old 8.4 GB I have Win2k installed.
I can boot on linux and win2k but not on winme. WinME was the last OS I installed and after the setup process was over, it rebooted so as to finish up the work and install necessary drivers, as it did. This means that apparently I can boot on WinME.

Anyway I then reconfigured lilo and installed it once again on hda (Win2k) in the MBR.
Now I was forced to use the linear option (I don't know exactly why, maybe because of the pci controller). When I added the WinME entry I got an error message when the winME entry was installed:

Warning: device 0x1604 exceeds 1024 cylinder limit.
   Use of the 'lba32' option may help on newer (EDD BIOS) systems.
Warning:  LINEAR may generate cylinder# above 1023 at boot-time.
Fatal: Sector address 53319735 too large for LINEAR (try LBA32 instead).

But I must use the linear option, if I change it to lba32, lilo hangs on boot up and I can load any of the OSes... Now as far my motherboard is concerned, I flashed the BIOS (it is an ASUS P2-99), the fixes where for some boot loaders as said by Asus. Didn't changed my problem.
I launched a utility in linux, can't remember its name, which said that the motherboard didn't support lba. Still when I enter the setup tool of the motherboard, in the autodetection of the HDs, I can choose between NORMAL, LBA, LARGE. The problem is that winME is installed on the 40 GB HD which is connected on the PCI IDE controller, therefore not seen by the motherboard during the setup. So I can't set it as LBA.

I know that I can fix the problem by reinstalling linux, win2k and winME by paying attention to the 1024 cylinder limit which seems to be the problem, but I can afford it, it will take me too much time!

So, this is a somewhat delicate problem. Please post some comments even if you don't think it will help, maybe it will! :)

A solution might be using the boot loader of win2k and reconfigure lilo so as to boot on linux or windows. When selecting the windows entry, the win2k boot loader will take the lead and allow me to choose between winME and win2k. Any ideas on how I make win2k boot manager work, because for the moment it doesn't seem to load at all, win2k are immediatly booting...

Few, I think that's all...
Oh yes, one last thing. When I enter the lba32 option, after the timeout lilo will boot in the default OS, but if I try to choose one myself (even if it is the default one), it will hang. Don't understand why, well anyway maybe you do. ;)

Thanks in advance!


Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 10 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 10 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros