Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
03-07-2005, 11:42 AM
|
#1
|
LQ Newbie
Registered: Mar 2005
Distribution: Mandrake 10.1
Posts: 5
Rep:
|
LILO Doesn't Work With 160GB Drive
All,
I've tried to partition the last 32GB of my 160GB harddrive (position 129GB-160GB) with Mandrake 10.1, but the LILO bootloader keeps returning code L 01 01 01... upon reboot. I've tried making the Windows XP partition (first 128GBs) the boot partition, but run across the same L 01 01 01... error when I select the option to start Mandrake Linux from the Windows loader menu. I'm beginning to wonder if my hard drive is too large and cannot boot the partition beyond the first 128GBs. For the record, I've tried using bootpart and a variety of other methods to get this to boot up properly, but to no avail. Any thoughts?... Ben....
|
|
|
03-07-2005, 11:55 AM
|
#2
|
LQ 5k Club
Registered: May 2003
Location: London, UK
Distribution: Fedora40
Posts: 6,154
|
From man lilo :
Code:
The boot process takes place in two stages. The first stage loader is
a single sector, and is loaded by the BIOS or by the loader in the MBR.
It loads the multi-sector second stage loader, but is very space lim-
ited. When the first stage loader gets control, it types the letter
"L"; when it is ready to transfer control to the second stage loader it
types the letter "I". If any error occurs, like a disk read error, it
will put out a hexadecimil error code, and then it will re-try the
operation. All hex error codes are BIOS return values, except for the
lilo-generated 40, 99 and 9A. A partial list of error codes follows:
00 no error
01 invalid disk command
0A bad sector flag
0B bad track flag
20 controller failure
40 seek failure (BIOS)
40 cylinder>1023 (LILO)
99 invalid second stage index sector (LILO)
9A no second stage loader signature (LILO)
AA drive not ready
FF sense operation failed
So it looks like a disk error. What sort of HDD is it? IDE, SCSI, or just maybe....SATA?
|
|
|
03-07-2005, 12:24 PM
|
#3
|
LQ Newbie
Registered: Mar 2005
Distribution: Mandrake 10.1
Posts: 5
Original Poster
Rep:
|
The hard drive is a refurbished 160GB IDE drive on a 1.4GHz PC with 384MB of RAM. Obviously, it's not the world's newest hardware, but I've decided to start learning Linux on the cheap. Thanks for the error codes. I've been looking for the LILO documentation, but couldn't find it in any of my web searches. Do you have a URL?... Ben....
|
|
|
03-07-2005, 06:10 PM
|
#4
|
Member
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248
Rep:
|
for lilo documentation, type "man lilo" from the console.
|
|
|
03-07-2005, 07:25 PM
|
#5
|
Senior Member
Registered: Dec 2004
Location: Lee, NH
Distribution: OpenSUSE, CentOS, RHEL
Posts: 1,794
Rep:
|
There are several options:
1. Upgrade to a newer BIOS
2. Look for a BIOS hack
3. Use a third-party IDE controller
I've used 160GB drives and larger with Linux (running a 160 right now) and previous to installing a hacked BIOS it would only see 137GB of the drive.
|
|
|
03-11-2005, 02:33 PM
|
#6
|
LQ Newbie
Registered: Mar 2005
Distribution: Mandrake 10.1
Posts: 5
Original Poster
Rep:
|
Thank you so much for your help! I've actually updated the BIOS, but the drive size still only shows 138GB of the 160GB. I tried to shrink the WindowsXP partition, but without Partition Magic I can't shrink an NTFS5 partition. Instead of purchasing a $70 software package for a single use, I've decided to play is safe and reinstall WindowsXP in a smaller partition and then install Linux OSs in the remaining portions below the 138GB watermark. Thanks again for all the help you guys gave me... Ben....
P.S. I checked out that flash animation about BBS posting. What a riot! Just as an FYI, I did check thoroughly before posting ;-)
|
|
|
All times are GMT -5. The time now is 09:10 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|