LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 09-22-2004, 07:14 PM   #1
drmauro223
LQ Newbie
 
Registered: Jul 2004
Location: New York
Distribution: SUSE
Posts: 3

Rep: Reputation: 0
1024 cylinder problem


Hi,

I recently ran the Yast Online Update in Suse 9.1. One of the things that was updated was the kernel. When I rebooted, grub gave the following error message:

kernel (hd1,1)/boot/vmlinuz root=/dev/hdb2 vga=0x317 desktop resume=/dev/hdb1 splash=silent

Error 18: Selected cylinder exceeds the maximum supported by BIOS

Grub still boots windows fine. Windows is on hda and Suse is on hdb. I can get into Suse if I want by booting from the installation CD.

Is there an easy way to go about fixing this? Could it be related to the infamous dual boot bug/partition table problem? I tried putting that hard drive in LBA mode, but that didn't work. Would using the fixboot patch from portal.suse.com/sdb/en/2004/05/fhassel_windows_not_booting91.html be a good idea?

I also read on the internet that I should just reinstall and create a seperate /boot partition and make that the first partion on the drive. Would that be a wise thing to do?

I'm fairly new to linux, so thanks for any advice.
 
Old 09-23-2004, 03:39 AM   #2
spuzzzzzzz
Member
 
Registered: Sep 2003
Location: Australia
Distribution: Gentoo
Posts: 465

Rep: Reputation: 30
Quote:
I also read on the internet that I should just reinstall and create a seperate /boot partition and make that the first partion on the drive. Would that be a wise thing to do?
It would indeed. Probably, your kernel was within the first 1024 cylinders when it was first installed, but the upgrade moved it to somewhere else where GRUB can't read it. By creating a 30ish meg /boot partition at the beginning of the drive, you can ensure that the kernel stays at the beginning of the drive.
 
Old 09-23-2004, 07:18 AM   #3
michapma
Member
 
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Rep: Reputation: 39
I've never used grub and am still relatively new to Linux myself, so take this with a grain of salt. But here's something I know (from reading in a manual) about LILO. (LILO is a Linux boot manager like GRUB if you don't know.) I assume that by principle it is applicable to any Linux boot manager. This comes from the SuSE 8.0 manual (translated from German):

LILO consists of:
* a LILO boot sector with first level of LILO code, that starts the actual LILO on boot
* the LILO machine code
* a map file, in which LILO writes where the Linux kernel is found and other data that it needs
* optionally, a message file for the boot screen choices
* the various Linux kernels and boot sectors, that LILO should offer to start

Now comes the important part:
ACHTUNG
Every write-access (also through file moving) to one of these parts makes the map file invalid, and therefore a new installation of LILO is necessary. This applies above all to any change to a new Linux kernel.

Since you have updated the kernel, the information that GRUB has about your current Linux kernel is no longer valid. That is why the problem: GRUB still knows how to boot Windows, but when it tries to start Linux, it is pointing with now-obsolete information to a non-existent Linux kernel.

As with LILO, part of the solultion is probably to make a new GRUB installation. Since you can't really now boot into SuSE to make a new GRUB installation, in order to avoid reinstalling your entire SuSE installation (this would probably make you lose all of your data unless it is backed up somewhere) you will have to find some trick to reinstall GRUB without booting using GRUB. There is almost certainly some way to do this, I just don't know it.

HOWEVER, the error message that you are actually getting is related to the 1024 cylinder problem. Yes, a standard way to get around this is to place a small boot partition in the first 1024 cylinders of the hard drive on a primary partition, so that any boot manager can find it. This is usually limited by the BIOS though, so I'm a bit surprised that it worked before but doesn't now.

Have you tried booting with your rescue disk (bootable floppy)?

Funny that as a Linux "newbie" you are using GRUB with SuSE, since SuSE likes to use LILO by default.

Btw, SuSE has a rescue system of its own. You could maybe read up on that.

Regards,
Mike

Last edited by michapma; 09-23-2004 at 07:20 AM.
 
Old 09-23-2004, 05:10 PM   #4
spuzzzzzzz
Member
 
Registered: Sep 2003
Location: Australia
Distribution: Gentoo
Posts: 465

Rep: Reputation: 30
In this respect, GRUB is different from LILO. GRUB doesn't use a System.map so there is no need to reinstall it every time you update the kernel. Actually, you don't need to re-install LILO every time you change one of these parts--you only need to reinstall LILO to the boot sector. Which basically consists of typing "lilo" at a command prompt.
 
Old 09-23-2004, 06:03 PM   #5
michapma
Member
 
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Rep: Reputation: 39
Quote:
Funny that as a Linux "newbie" you are using GRUB with SuSE, since SuSE likes to use LILO by default.
Grains of salt falling from the sky...

Now I really feel like a heel. I just read that SUSE switched to using GRUB by default as of SUSE 8.1; my docs are for 8.0.

Well I've just updated my distro and it apparently installed a new kernel, so I guess I need to go type LILO somewhere. See you later... "Have a lot of fun!"
 
Old 09-23-2004, 07:46 PM   #6
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
drmauro223

ignoring the lilo distractions for one nanosecond, I don't think you got a reply?

reboot to mbr and grub menu choose C for command and type
root (hd1,1)
find /boot/ AND PRESS THE TAB key to get a list of files in /boot folder
you are likely to have at least 2 vmlinuz files
vmlinuz 2.6.8 (example)
vmlinuz-2.4.20 (example)
initrd-2.6.8 (likely)
initrd - 2.4.20 (maybe)

write down what the exact names are and go back to menu then PRESS E for edit and edit the relevant kernel line and/or initrd line if you have one to point to the correct files
 
Old 09-23-2004, 07:48 PM   #7
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
If the edit worked you had chosen B for boot then go into /boot/menu.lst or /etc/grub.conf and edit the lines exactly as needed. You will need root powers to edit a root owned file.
 
Old 09-24-2004, 02:57 AM   #8
michapma
Member
 
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Rep: Reputation: 39
See, I knew there was a way.

Quote:
Originally posted by aus9
ignoring the lilo distractions for one nanosecond, I don't think you got a reply?

Hmm, well I tried to be useful anyway.
 
  


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 On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
the 1024 cylinder limit visited... ngjunkie0011 Suse/Novell 5 07-04-2005 10:46 AM
Getting around a cylinder 1024 error Digital Surgeon Fedora - Installation 1 02-08-2005 04:26 PM
problem about 1024 cylinder limit hard disk guru Linux - Newbie 3 08-30-2003 04:02 PM
Boost sector > 1024 cylinder amitrgholap Linux - General 2 09-28-2001 11:37 AM
1024 cylinder boundry hmorrow Linux - Newbie 2 05-22-2001 08:15 AM


All times are GMT -5. The time now is 03:56 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration