Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.
Course Of The Month
2 days, 18 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
LILO error URGENT!
Posted on 1999-01-25
After a reboot* command on a dual Win NT and Linux(redhat 5.2) I can not start Linux. LLIO starts as follows: "LIL-" and I heard the error mean: "The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. - from www.yggdrasil.com"
WHAT SHOULD I DO? Formating the Hard DRIVE partition will be ruled out. Is any way I can remove LILO and install it again? Will this will work?
Thank you,
WHAT SHOULD I DO? Formating the Hard DRIVE partition will be ruled out. Is any way I can remove LILO and install it again? Will this will work?
Thank you,
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
3 Comments
Are you using NT's boot loader to get to LILO or do you boot NT from LILO.
The following discussion assumes you are using the NT boot loader ( my preference )
Have you just installed Linux. If so, did you have a look at /etc/lilo.conf. make sure the images it points to are the ones you want to use (ie: boot=, map=, kernel=). If they are execute the following /sbin/lilo with no arguments. You should a line of text for every label specified ( a label is associated with a bootable OS by using the label= statement within /etc/lilo.conf, read the LILO documentation if you are really lost ).
If you didn't get any errors things are probably o.k., if you got a warning about Linux not being on the first disk device, you can ignore that as long as it's on the second device.
Now 'peel' the bootsector off of the linux root partition
I have installed Linux on my second IDE drive in the first partition so if I were to need to 'peel' the boot sector i would issue this command:
dd if=/dev/hdb1 of=bootsect.lnx bs=512 count=1
now copy that file ( bootsect.lnx) to the root of your NT partition ( in my case DOS C: drive ).
The following discussion assumes you are using the NT boot loader ( my preference )
Have you just installed Linux. If so, did you have a look at /etc/lilo.conf. make sure the images it points to are the ones you want to use (ie: boot=, map=, kernel=). If they are execute the following /sbin/lilo with no arguments. You should a line of text for every label specified ( a label is associated with a bootable OS by using the label= statement within /etc/lilo.conf, read the LILO documentation if you are really lost ).
If you didn't get any errors things are probably o.k., if you got a warning about Linux not being on the first disk device, you can ignore that as long as it's on the second device.
Now 'peel' the bootsector off of the linux root partition
I have installed Linux on my second IDE drive in the first partition so if I were to need to 'peel' the boot sector i would issue this command:
dd if=/dev/hdb1 of=bootsect.lnx bs=512 count=1
now copy that file ( bootsect.lnx) to the root of your NT partition ( in my case DOS C: drive ).
I think I need more information to even be able to decide if I can answer it.
Are you using LILO or the NT boot loader as your main OS loader ?
Have you just recompiled your kernel without running /sbin/lilo ?
Can you reply with a copy of your /etc/lilo.conf ?
Are you using LILO or the NT boot loader as your main OS loader ?
Have you just recompiled your kernel without running /sbin/lilo ?
Can you reply with a copy of your /etc/lilo.conf ?
I recommend using dd with bs=448, 'cause it does not copy the partition table
elvaaa, when you installed lilo, it made a backup copy of the MBR, it's usually
/boot/boot.301, where 301 is a number identifying the disk where it came from.
You max copy it back with the dd command (see PinTails comment)
elvaaa, when you installed lilo, it made a backup copy of the MBR, it's usually
/boot/boot.301, where 301 is a number identifying the disk where it came from.
You max copy it back with the dd command (see PinTails comment)
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Linux users are sometimes dumbfounded by the severe lack of documentation on a topic. Sometimes, the documentation is copious, but other times, you end up with some obscure "it varies depending on your distribution" over and over when searching for …
The purpose of this article is to fix the unknown display problem in Linux Mint operating system. After installing the OS if you see Display monitor is not recognized then we can install "MESA" utilities to fix this problem or we can install additio…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month2 days, 18 hours left to enroll
621 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.