[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

lilo refuses



Weird message from lilo -t -v:

Warning: LBA addressing assumed
Reading boot sector from /dev/fd0
Fatal: Trying to map files from unnamed device 0x000c (NFS/RAID mirror down?)

OK.  My RAID, a software RAID, is not down, and contains /home and /usr 
as LVM volumes.  Can lilo not use it?

/deb/fd0 has a floppy disk in it.
/boot is on /dev/hda1, which is not a raid.


Are lilo's private files on /usr, and is it unable to read from a 
software RAID?  Do I somehow need to move lilo's private files from /usr 
to /hda1?  And which ones are they?  And how can I tell it the 
files have moved?  Or has lilo become a hopeless case?

-- hendrik

Here's the complete output from lilo -t -v
----------------
LILO version 22.6.1 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 23:17:54 on Mar 30 2006
Debian GNU/Linux

Warning: LBA32 addressing assumed
Reading boot sector from /dev/fd0
Fatal: Trying to map files from unnamed device 0x000c (NFS/RAID mirror down ?)
----------------

And here;s lilo.conf:
----------------
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt' (if you have created it), or   |
# | install a new kernel.  The computer will most likely fail to  |
# | boot if a kernel-image post-install script or you don't       |
# | remember to run `lilo'.                                       |
# |                                                               |
# +---------------------------------------------------------------+

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/fd0

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1

# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#	prompt
#	delay=100
#	timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#


# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
 
# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=

#
# Boot up Linux by default.
#
default=Linux

image=/boot/vmlinuz-2.6.15-1-amd64-generic
	label=Linux
	read-only
#	restricted
#	alias=1
	initrd=/boot/initrd.img-2.6.15-1-amd64-generic

image=/boot/vmlinuz-2.6.12-1-amd64-generic
	label=Linuxold
	read-only
#	restricted
#	alias=1
	initrd=/boot/initrd.img-2.6.12-1-amd64-generic

# image=/vmlinuz
#	label=Linuxln
#	read-only
#	restricted
#	alias=1

#	initrd=/initrd.img

# image=/vmlinuz.old
# 	label=LinuxOLD
# 	read-only
# 	optional
# #	restricted
# #	alias=2
# 
# 	initrd=/initrd.img.old


# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#	label=HURD
#	restricted
#	alias=3
----------------




Reply to: