Mailinglist Archive: opensuse (3378 mails)

[SMD (Michael) Alachouzos <alacos@xxxxxxxxxxxxxx>]

Hello.

On Wed, 3 Apr 2002 22:47:15 +0200, Henne Vogelsang wrote:
>Hi,
>
>On Wednesday, April 03, 2002 at 22:41:38, SMD Alachouzos wrote:
>
>>When I installed SuSE Linux 7.3, I chose to write LILO to my boot
>>partition /dev/hda3 during the installation process. This was OK,
>>and Linux now boots from /dev/hda3.
>>
>>However, I now need to re-write LILO to the /dev/hda3 boot
>>partition. But whenever I use YaST2 to try to do so all that I get
>>is an error message saying "Could not write the LILO boot sector".
>>
>>I have no idea WHY YaST2 cannot write LILO to my /dev/hda3
>>partition. However, it seems that this is not just a problem with
>>this particular destination partition but rather a problem with
>>writing LILO to ANYWHERE -- because YaST2 refuses to write LILO to
>>a floppy either. (i.e. if I try to create a boot floppy with YaST2
>>I get an error message saying "Could not write the LILO boot sector
>>to the floppy. Please check that the floppy disk is formatted [it
>>is] and that the write protection tab is removed [it is]".
>>
>>Any ideas as to how I might go about investigating what is wrong?
>
>Run lilo from console as root with -v -t
>
>$ lilo -v -t
>
>and post the output of it here.
>
>Henne

OK -- I'm posting the output below. A further peculiarity, by the
way, is that whenever I attempt to write LILO to anywhere with YaST2
this seems to result in the line "lba32" being deleted from my
/etc/lilo.conf file. (I inserted that line in the file in order to
overcome any 1024-cylinder-boundary problems).

Anyway, the output from the lilo -v -t test is as follows:--

linux:~ # lilo -v -t
LILO version 21.7-5 (test mode), Copyright (C) 1992-1998 Werner
Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 06-May-2001 and compiled at 22:38:15 on Sep 23 2001.

Reading boot sector from /dev/hda3
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz
Mapping RAM disk /boot/initrd
Added linux *
Boot image: /boot/vmlinuz.suse
Mapping RAM disk /boot/initrd.suse
Added failsafe
Boot other: /dev/hda1, on /dev/hda, loader /boot/chain.b
Warning: CHANGE AUTOMATIC assumed after "other=/dev/hda1"
Added windows
Boot image: /boot/memtest.bin
Added memtest86
The boot sector and the map file have *NOT* been altered.
linux:~ #