UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm currently trying to get ubuntu on an old spare system:
Mobo: Pinegroup PT-VP41-17
CPU: K62 500MHz
HD: WD 313500 (13GB) IDE
CDROM: 52X Liteon 525 IDE
Memory: 256MB PC100
NIC: 3Com xx905B PCI
Graphics: Onboard Trident 3D Blade
I get an Error 18 this time when grub is loading. Locks up.
Here's my Menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single
## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
How is the drive on this machine actually partitioned? Just from reading the boot stuff, it appears that the drive has a single partition on it, /dev/hda1, and everything is on that single partition? Is this correct, or do you have the system split into a couple of partitions, in particular do you have a /boot partition?
How is the drive on this machine actually partitioned? Just from reading the boot stuff, it appears that the drive has a single partition on it, /dev/hda1, and everything is on that single partition? Is this correct, or do you have the system split into a couple of partitions, in particular do you have a /boot partition?
I found that there was a requirement to create a /boot because the computer was older. I went back and reparted everything as such:
#1 /boot (50MB)
#2 / (13GBMB)
#3 /swap (512MB)
I got the grub to start without locking but now I got an error stating that it cannot find /dev/hda2. I'm still trying to figure that out. Is 13GB too big for the / partition even with a /boot?
Error 18: Selected cylinder exceeds maximum supported by BIOS
This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB on others.). In more practical terms this means the BIOS is unable to start executing the kernel because the kernel is not located within the block it can access at boot up time.
This can be circumvented by creating a boot partition at the beginning of the disk that is completely within the first 1023 cylinders of the harddrive. This partition will contain the kernel.
The kernel it self does not suffer from the same limitations as the BIOS so after the BIOS has loaded the kernel the kernel will have no problem accessing the whole harddrive. Newer BIOSes will automatically translate the harddrives size in a way that it can be completely contained within the first 1023 cylinders and hence modern computers do not suffer from this problem.
The same error can happen when the BIOS detects a disk in a different way as Linux does. This can happen when changing motherboards or when moving a GRUB-bootable disk from one computer to another. If this happens, just boot with a GRUB floppy, read the C/H/S numbers from the existing partition table and manually edit the BIOS numbers to match. If using a SUSE linux and installing on VM Ware this problem is solved by creating a small partition at the very beginning of the harddisc, and mounting it as /boot.
Ya I know Wells. I put the /boot at the start of the HD within the limit. I broke the parts down to <8gb as well.
Funny thing is that in this configuration, the grub loaded but it couldn't find the HDA2:
#1 /boot (50MB)
#2 / (13GBMB)
#3 /swap (512MB)
In this configuration it givea Error 18 again, even though the /boot partition size did not change.
#1 /boot (50mb)
#2 / (7gb)
#3 /home (6gb)
#4 /swap (~512mb)
I'm trying to avoid a grub floppy. Considering the pitiful quality of diskettes, I'd be making copies every other day.
Hmmm. What about a grub bootable cd??? That would be more reliable than a floppy.
When I boot Knoppix LiveCD it can see the drive partitions fine. Although ubuntu refuses to see them upon booting. It's as if they don't exist. I don't see them listed in the /dev from the busybox either.
Christ sakes! No matter what I do this sucker will not load.
- If I don't make a boot partition and load it in mbr, I get an error 18.
- If I do make a boot partition, grub loads but can't find the root partition.
Why can't it see the root partition? It's clearly there if I boot up on Knoppix livecd. I can access it. It's extfs3 set to mount as /.
This is the kind of stuff that makes me want to throw Linux discs against the wall. I've read every how to instruction I can find.
My exact steps (starting at custom partitioning):
- Kill all partitions.
- Create /boot partition, 200 mb, beginning of free space, boot flag on.
- Create / partition, ~8gb, beginning of free space
- Create /swap, ~500 mb, beginning of free space
- Write partition table
- Continue with install.
- Reboot
- Grubs starts
- cannot find /dev/hda(n), drops to busybox.
OK...this is a bit sick and twisted, but have you tried using lilo instead of grub? Since lilo is an older boot loader, it may not have this problem on your older system.
OK...this is a bit sick and twisted, but have you tried using lilo instead of grub? Since lilo is an older boot loader, it may not have this problem on your older system.
No I haven't. The default for ubuntu is grub. I don't even get an option to install Lilo. Considering I'm a newbie, I don't really know how to do it. Also how to prevent grub from being installed.
Old system with old boot loader...this might work.
I'll look around for some documentation and see if it works. It's worth a try. I refuse to give up. My anger only means I'm learning.
I'm fairly certain that if you hit esc at some point during the installation while it is waiting for input, it will escape you to a menu which has the option to install lilo
I tried putting in on the boot partition first then I tried to put it on the MBR. Both ways reported a failed attempt.
I did continue anyway and the machine rooboted. LILO started up and got dropped to busybox.
I see lots of errors reporting no directory or file found. Also seeing lots of errors for DriveSeek and CRC errors while trying to mount the partitions.
I've tried 3 different hard drives on this. One would suspect there is a serious hardware problem with the mobo. However it does install and run WinXp lite perfectly.
Since Lilo started, something did get written.
I booted up with UBCD and took a look at the partitions with XFDISK, I got a partition table erro and it bailed.
I tried Ranish and I got a warning box stating that the MBR/EMBR partition overlaps an existing partition.
I tried SPFDISK 2000 and it report an invalid partition table. It's worth noting that when I bypass the error and look there is a single partion listed at 504MB which immediately reminded of the old 504MB barrier.
OMG, I found the problem! Hardware issue. No warnings, no errors anywhere else, and even Xp Pro ran fine BUT............
The IDE cable was faulty. For some reason Linux was more sensitive to it and refused to see the partitions. The fact that XP loaded up with no probs lead me to suspect a software issue instead of a hardware issue.
Regardless, with a new IDE cable, Ubuntu is up and running. What a battle!
Trial by fire is often the best way to learn tho.
I wonder if I should go back and reinstall with GRUB now. Any adivice on the partition sizes? Which parition should I make the largest to give in more room?
Thanks for all the help and guidance! I'm a happy newbie.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.