J'ai test� raid-extra-boot=/dev/sda1, /dev/sda2 mais cela ne fonctionne pas � cause du mode raid.
Le message d'erreur fait r�f�rence au device-mapper
device-mapper ioctl cmd 12 : No such device or address
Fatal : device-mapper : dm_task_run (DM_DEVICE_TABLE) failed
Y a t-il quelquechose qui m'a �chapp� � l'installation pour �viter ces d�sagr�ments ?
--- afmdg <[EMAIL PROTECTED]> wrote:
Salut,
Salut
J'essaie de mettre � jour le noyau debian sur le serveur IBM series 346. J'ai fait une installation avec un Raid 1 software et installer lilo qui est plus simple � installer dans les MBR de chaque disque. Par d�faut, j'ai un noyau 2.6.8-2-386. J'ai install� deux noyaux pour faire des tests et pour pouvoir utiliser les 2Go de RAM : Le 686 et l'EM64T-P4 mais comment booter dessus ? Quand je lis lilo.conf, il prend vmlinuz et l'initrd de la racine qui sont des liens sur /boot Vu que j'ai install� deux noyaux, j'ai maintenant vmlinuz qui pointe vers vmlinuz EM64T-P4 et vmlinuz-old vers le 686. De m�me pour initrd. Je voudrais de plus ajouter le menu de lilo.
J'ai lancer la commande lilo et j'ai le message suivant : device-mapper ioctl cmd 12 : No such device or address Fatal : device-mapper : dm_task_run (DM_DEVICE_TABLE) failed
Est-ce que tu peux nous envoyer ton /etc/lilo.conf
Lorsque j'ai reboot�, j'ai toujours le noyau 386 avec la commande uname -r ???
L'EM64T-P4 optimis� Xeon est disponible dans les noyau des plateformes i386, quelle est la diff�rence avec une installation pour plateforme i64 ? Quelle sont les packages a utilis� pour l'EM64T-P4 ?
D'avance merci,
Michel
# /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/md0
raid-extra-boot=mbr-only
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/mapper/system-racine
# 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
#
vga=normal
# 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=/vmlinuz
label=Linux
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
