Lilo Error 0x01

HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie LILO Disk Error Code 0x01 User Name Remember Me? Password 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. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 04-25-2003, 12:56 PM #1 Techweenie1 Member Registered: Feb 2003 Location: Hinsdale/Chicago, IL, USA Distribution: Slackware 10 (2.6.8.1) Posts: 43 Rep: LILO Disk Error Code 0x01 Okay trying linux once again...this time trying slackware, installed it over a few partitions dedicated to RedHat which had the GRUB bootloader on it beforehand. However when I tried installing LILO over GRUB it errored out, so I removed GRUB manually, then I went into Linux configured my lilo.conf file ran /sbin/lilo under root, and all I get at boot up time is L 01 01 01 01...I installed the scsi.s kernal thinking it would work with my adaptec card used for my intern

20:00:29 -0500 (CDT) On Thu, 3 May 2001, Massimo Alonzo wrote: > Hi, > > I moved my second hard disk from secondary master to secondary slave > hoping to make my cdburner work (without success); the trouble is that I > installed RH7 for tests on that disk (as /dev/hdd2) and the system doesn't > like it. > > In detail: > > - This partition worked really well when the disk was connected as sec > master > > - Lilo into my "work installation: /dev/hda4": > > I added these 2 lines to boot /dev/hdd2: > > boot=/dev/hda #MBR > ...... > other=/dev/hdd2 > label=rh70_test > > > but when I launch "lilo -v" I get: > > ........... > Boot other: /dev/hdd2, on http://www.linuxquestions.org/questions/linux-newbie-8/lilo-disk-error-code-0x01-56755/ /dev/hdd, loader /boot/chain.b > Warning: BIOS drive 0x82 may not be accessible > Added rh70_test > ........... > > - Lilo into my "tests installation: /dev/hdd2": > > boot=/dev/hdd2 #First sector of the partition > map=/boot/map > install=/boot/boot.b > prompt > timeout=0 > message=/boot/message > default=linux > > image=/boot/vmlinuz-2.2.16-22 > label=linux > read-only > root=/dev/hdd2 > > - When I choose rh70_test at boot time I get: > > ERROR 0X01 > > - Bios recognize this disk at startup > https://www.redhat.com/archives/redhat-list/2001-May/msg00278.html - both /dev/hdd1 and /dev/hdd3 (vfat) works > > > My questions are: > > 1) Is it possible to install linux on a sec slave disk? > Yes > > 2) What does "Warning: BIOS drive 0x82 may not be accessible" means? My hd > works .... I tried it. This message doesn't appear if I connect this disk > as sec master, or elsewhere (but sec slave :p). > Depending on your BIOS, you may or may not be able to access devices on the second IDE controller using BIOS calls. It is mainly a problem with older machines. If your BIOS has settings for four drives, chances are you will not have any problems. > > 3) What does "ERROR 0X01" means? > >From the LILO README file: 0x01 "Illegal command". This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. See also "Warning: BIOS drive 0x may not be accessible" in section "Warnings". What I think may have happened is that you ran lilo while the drive was still connected up as the slave drive on the master controller, and now that you have moved the drive, lilo is still trying to load from the old drive location. (The second copy of lilo - the one on what is now /dev/hdd.) This would make sence because you would have to had booted the second copy

/ November22, 2015; 10 months ago(2015-11-22) Repository lilo.alioth.debian.org/ftp/sources/ Development status discontinued Type Bootloader License BSD license Website lilo.alioth.debian.org LILO (LInux LOader) is a boot loader for Linux and was the default boot loader for most Linux distributions in the https://en.wikipedia.org/wiki/LILO_(boot_loader) years after the popularity of loadlin. Today, many distributions use GRUB as the http://www.gossamer-threads.com/lists/linux/kernel/34328 default boot loader, but LILO and its variant ELILO are still in wide use. Further development of LILO was discontinued in December 2015 along with a request by Joachim Weidorn for potential developers. Contents 1 Overview 2 LILO files 2.1 lilo.conf 2.2 /boot/ 3 Master boot record 4 Output 5 Error codes 6 ELILO 7 lilo error See also 8 Notes 9 References 10 External links Overview[edit] LILO does not depend on a specific file system, and can boot an operating system (e.g., Linux kernel images) from floppy disks and hard disks. One of up to sixteen different images can be selected at boot time. Various parameters, such as the root device, can be set independently for each kernel. LILO can be placed in the master lilo error 0x01 boot record (MBR) or the boot sector of a partition. In the latter case, the MBR must contain code to load LILO. At system start, only the BIOS drivers are available for LILO to access hard disks. For this reason, a very old BIOS access area is limited to cylinders 0 to 1023 of the first two hard disks. For a later BIOS, LILO can use 32-bit "logical block addressing" (LBA) to access the entire capacity of the hard disks the BIOS has access to. LILO files[edit] lilo.conf[edit] The lilo.conf file is typically located at /etc/lilo.conf. Within lilo.conf there are typically two section types. The first section, which defines the global options, contains parameters which specify boot location attributes. The second section(s) contain parameters associated with the operating system images to be loaded. The section type can be repeated for up to 16 different boot selections. Remember to run the /sbin/lilo command after editing the /etc/lilo.conf file so that your changes take effect. Definition information can be found in the LILO Manpage. An example for /etc/lilo.conf: large-memory lba32 boot=/dev/hda install=menu map=/boot/map prompt default=Linux image=/boot/vmlinuz-2.6.26 label="Linux" root=/dev/hda1 append="" read-only optional other=/dev/hda3 label="FreeBSD" Note: Here LILO offers after correct installation a menu with Linux and FreeBSD.

Post #1 of 1 (168 views) Permalink LILO + bzImage == Block move error 0x01 Hi, Until recently, I've been able to fit everything I wanted into a normal zImage. However, I've been bumping into the "Kernel too big" stuff when compiling, and have reached the point where it's just getting to be a hassle stripping stuff out to come under the magic size. So, I tried building a bzImage. Built just fine, no problems. Noting the docs, I made sure that I was running a recent version of lilo (lilo-20), and went ahead and added it normally: image = /boot/bvmlinuz-2.1.121 label = 2.1.121 root = /dev/ide/hd/c0b0t0u0p1 append = "ide2=0x1e8,0x3ee,11 root=/dev/ide/hd/c0b0t0u0p1 devfs=mount" vga = ask read-only (Note that I had this problem before going to devfs, so that's not it. The odd ide2=... stuff is to detect the IDE controller on my SB16.) When I boot, and try to come up on that kernel, I get: LILO boot: 2.1.121 Block move error 0x01 I have -no- clue what is happening here; if I strip the kernel down to fit in a "zImage", everything works fine. If there's anything else about my setup that I can provide, please let me know. -- -------------------. emarshal at logic.net .--------------------------------- Edward S. Marshall `-----------------------' http://www.logic.net/~emarshal/ Linux labyrinth 2.1.117 #2 SMP Thu Aug 20 21:20:49 CDT 1998 i586 unknown 10:55pm up 38 min, 1 user, load average: 0.00, 0.01, 0.00 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger Please read the FAQ at http://www.tux.org/lkml/faq.html Index | Next | Previous | Print Thread | View Threaded Linux Kernel Interested in having your list archived? Contact Gossamer Threads Web Applications & Managed Hosting Powered by Gossamer Threads Inc.