Projects / LILO / Comments

Comments for LILO

18 Mar 2004 18:41 genezkool323

Re: Help me - help me, please ;_;!

> Most Micro$oft products will restore the
> MBR with:
>
>
> C:> fdisk /mbr
>
>


thx alot ^_^! when i did some research, I read that in some occasions your computer might not boot up after this command, so i'm backin up my important files. and, off topic, does anybody reccomend any good books on linux? (general info, file system, distros, compatibility); specifically on SuSE? (don't have to answer)

17 Mar 2004 21:15 johncoffman

Re: Help me - help me, please ;_;!
Most Micro$oft products will restore the MBR with:


C:> fdisk /mbr

17 Mar 2004 19:40 genezkool323

Help me - help me, please ;_;!
I'm really good when it comes to Windows and DOS and the Microsoft things. I decided to try some Linux. I have two hard drives. I use one for Windows and the other was an extended partition.

I downloaded the SuSE ISOs and installed it on my second harddrive (formatted the extended partition). It gave me the boot manager LILO. I was gonna read some more about linux (file system, installing source, etc...) but I didn't have time and i needed some HD space, so I deleted the Linux partition.

I Didn't delete the LILO boot manager before doing so and now it says SuSE is still there after I deleted the partition, and SuSE is the master-boot. Now if I don't select Windows at bootup it will automatically load SuSE (which isn't there).

So can someone please tell me how to get rid of it now that I have uninstalled SuSE. I don't want to reinstall SuSE again (and that probably won't solve the problem anyway).

Thanks, Oli ^_^

29 Feb 2004 07:25 johncoffman

Re: lilo dual boot problem
The kernel is aware of ez-bios. LILO (/sbin/lilo) boot installer does all I/O through the kernel; hence, there is no conflict with ez-bios. (EZ-BIOS moves the actual boot sector from sector 0 to sector 1; the kernel will use the correct boot sector.)

28 Feb 2004 18:24 treilly

Re: lilo dual boot problem

> First you have a Windows problem:
> Windows (all versions) boots ONLY from
> drive 0x80. Using the current LILO:
>
>
> other=/dev/hda1
>
> label=Win98
>
> master-boot
>
> will take care of that problem. And
> yes, ez-bios will have to be installed
> on /dev/hdb too, but set to control
> /dev/hda.
>
> Personally, I'd suggest going back to
> booting from /dev/hda by installing the
> LILO boot record on /dev/hda
> (boot=/dev/hda). Then Windows is on the
> 0x80 (C:) drive already.
>


Thanks John,

So I don't have to worry about ez-bios being overwritten by lilo when I install lilo to hda ?

Tim

28 Feb 2004 15:59 johncoffman

Re: lilo dual boot problem
First you have a Windows problem: Windows (all versions) boots ONLY from drive 0x80. Using the current LILO:


other=/dev/hda1


label=Win98


master-boot


will take care of that problem. And yes, ez-bios will have to be installed on /dev/hdb too, but set to control /dev/hda.

Personally, I'd suggest going back to booting from /dev/hda by installing the LILO boot record on /dev/hda (boot=/dev/hda). Then Windows is on the 0x80 (C:) drive already.

28 Feb 2004 11:34 treilly

lilo dual boot problem
I have a 15G hardisk on hda and a 4G hardisk on hdb.
The hda partitioning is :

hda1 Boot Primary Win95 FAT32 7.682.42
hda5 Logical Win95 Fat32 7674.19
Pri/Log Free Space 8.23

hdb partitioning is:
hdb5 Boot Logical Linux ext2 7.71
hdb6 Logical Win95 Fat32 1068.32
hdb7 Logical Linux swap 317.40
hdb8 Logical Linux ext2 2903.04

Some kind soul on the debian web site had the
excellent idea to put lilo on drive b, and change the
boot order in bios so that drive b becomes a in essence.
This basically worked after i put in the bios=0x80
command for /dev/hdb command.

The problem is that lilo won't boot the windows drive. It
just hangs. The other issue is that ez-bios is on
drive a. Is the problem that lilo is trying to boot windows
without starting ez-bios ? Is there a way to get ez-bios
going and then start windows. Below is my lilo.conf:

prompt
lba32

disk = /dev/hdb
bios = 0x80
disk = /dev/hda
bios = 0x81

boot=/dev/hdb
root=/dev/hdb8
install=/boot/boot.b
map=/boot/map
vga=normal
delay=20
image=/boot/vmlinuz-2.4.18-bf2.4
Label=Linux
other=/dev/hda1
Label=Win98

Thanks,

Tim

11 Dec 2003 11:04 johncoffman

Re: Boot from an external RAID array
Have you run the LILO diagnostic disk #1? If the external RAID array has no BIOS device code (as detected by the diagnostic), you will not be able to boot from the drive.


Kernel drivers for hardware RAID arrays are in a state of flux. LILO 22.5.8 issues a cautionary message about installations when the "ataraid" driver is in use. If the external RAID array is SCSI, a lot will depend on the driver in use.


My homepage at http://lilo.go.dyndns.org/ contains questions to be answered if you would e-mail me directly.

11 Dec 2003 05:23 romain

Boot from an external RAID array
Hi,

We would like to use LILO to start up a Linux server, but we didn't find out how to do this. Here are some elements to understand how we are disappointed!

- The system boot perfectly (default install settings) from the internal SCSI hard drive (sdc)

- When Linux is installed on the RAID array, an "Operating System not found" error message is displayed.

- The only solution is to boot from a floppy, which contains the kernel and the initrd.

- Linux rescue perfectly detects the different partitions on the external RAID (sda).

- LILO do not display any warning during MBR writing.

- We tried the "disk", "bios", "linear", "lba32" options without succes.

Here is our /etc/lilo.conf:
prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
linear

image=/boot/vmlinuz-2.4.21-4.ELsmp
label=linux
root=/dev/sda3
initrd=/boot/webs-initrd.img
read-only

Here is an extract of dmesg:

Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 71811072 512-byte hdwr sectors (36767 MB)
Partition check:
sda: sda1 sda2 sda3 sda4

Here is the layout of the different partitions:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 13013756 2067116 10285568 17% /
/dev/sda1 147766 16155 123982 12% /boot


We are using LILO version 22.5.8.

Anybody got an idea?

Thanks a lot,

Romain.

29 Nov 2003 12:01 hurtta

Re: LILO can't acces /dev/fd0

> I have a dev directory with fd0, console
> and null in it. I got lilo to eork by
> first mounting fd0 with:
> mount -o dev /dev/fd0
> I heard this from someone on the net,
> and I would like to know exactly why did
> it work. The documentation for the dev
> option is quite cryptic:
>
> dev Interpret character or block
> special devices
> on the file system.


'nodev' tradiotionally prevents doing 'character'
or 'block' special files to filesystem. So 'dev'
is just opposite.


crw-rw-rw- 1 root root 5, 0 Nov 29 21:06 /dev/tty


That 'c' indicates that this is character special file.


brw-rw---- 1 root disk 3, 0 Apr 7 2003 /dev/hda


That 'b' indicates that this is block special file.

Screenshot

Project Spotlight

ReciJournal

An open, cross-platform journaling program.

Screenshot

Project Spotlight

Veusz

A scientific plotting package.