gros probleme de boot sur debian sarge
Bonjour,
Pour essayer de faire marcher un composant de ma carte mère
avec lm-sensor, je me suis dit que je pouvais peut-etre mettre le noyau 2.6.16.
J'ai mis celui de backports.
J'ai vu apres que j'avais un erreur de devfs, qd je bootais sur le noyau 2.6.16
donc je rebootais sur le 2.6.8 qui marchait tjs nikel.
J'avais lu qu'il fallait utilser plutot udev avec le noyau 2.6.16 donc hop j'ai
installé, mais ca n'a rien changé.
Je me suis dit d'au lieu de mettre le udev de sarge que j'allais aussi mettre le
"udev" de backports.
La, il m'a dit qu'il allait virer le kernel-image-2.6.8 et hotplug.
PS: J'utilise de la LVM, même sur / (qui correspond au LV: /dev/mapper/VG0-SLASH, et mon VG c'est Vh0)
Je me suis dit que c'etait pas grave car au pire, je reinstallerai ce noyau en
chrootant sur la debian mais voila, même en virant depuis le chroot udev, et en
ayant remis hotplug, kernel-image-2.6.8, j'ai ce message d'erreur là
unable to find volume group "VG0"
pivot_root no such file or directory
/sbin/init: 432: cannnot open /dev/console
kernel panic: attemptd to kill unit!
--------------------------------------------------------------------------
j'ai aussi esayé manuellement:
mkinitrd -o /boot/initrd.img-2.6.8-2-386 /lib/modules/2.6.8-2-386
Voila un exemple d'execution de la reinstall du paquet:
-----------------------------------------------------------------------------
Knoppix:/# aptitude reinstall kernel-image-2.6.8-2-386
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages will be REINSTALLED:
kernel-image-2.6.8-2-386
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0B/14.1MB of archives. After unpacking 0B will be used.
Writing extended state information... Done
(Reading database ... 65447 files and directories currently installed.)
Preparing to replace kernel-image-2.6.8-2-386 2.6.8-16sarge1 (using
.../kernel-image-2.6.8-2-386_2.6.8-16sarge1_i386.deb) ...
The directory /lib/modules/2.6.8-2-386 still exists. Continuing as directed.
Unpacking replacement kernel-image-2.6.8-2-386 ...
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /vmlinuz-2.6.16.060810
Found kernel: /vmlinuz-2.6.8-2-386
Updating /boot/grub/menu.lst ... done
Setting up kernel-image-2.6.8-2-386 (2.6.8-16sarge1) ...
File descriptor 3 left open
File descriptor 4 left open
File descriptor 5 left open
File descriptor 6 left open
File descriptor 7 left open
Finding all volume groups
Finding volume group "VG0"
Not touching initrd symlinks since we are being reinstalled (2.6.8-16sarge1)
Not updating image symbolic links since we are being updated (2.6.8-16sarge1)
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
Searching for splash image... none found, skipping...
Found kernel: /vmlinuz-2.6.16.060810
Found kernel: /vmlinuz-2.6.8-2-386
Updating /boot/grub/menu.lst ... done
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Knoppix:/#
--------------------------------------------------------------------------------
Voila mon menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
fallback 1
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/mapper/VG0-SLASH ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=false
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.16.060810
root (hd0,1)
kernel /vmlinuz-2.6.16.060810 root=/dev/mapper/VG0-SLASH ro
initrd /initrd.img-2.6.16.060810
savedefault
boot
title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,1)
kernel /vmlinuz-2.6.8-2-386 root=/dev/mapper/VG0-SLASH ro
initrd /initrd.img-2.6.8-2-386
savedefault
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
----------------------------------------------------------------------------------------------------------------------
le pb vient bien de linitrd, car avec celui d'un pote ca va
un peu plus loin quand même, enfin il bloque apres, pq c'est pas le même VG.
C'est peut-etre l'environnement de knoppix, qui est moins adapté, peut-etre?
Je sais pas si ca joue qd on chroote.
J'avais fait ceci:
mount -t ext3 -rw /dev/VG0-SLASH /mnt/debian
mount -t ext3 -rw /dev/md1 /mnt/debian/boot
mount -o bind /dev /mnt/debian/dev
mount -t proc proc /mnt/debian/dev/proc
chroot /mnt/debian
Je sais pas si avec le cd d'install de sarge, je peux me regénérer un bon initrd sans du tout reinstaller quoique ce soit:-(?
Je viens aussi d'essayer de recompiler mon noyau avec make-kpkg et l'option --initrd, mais ca fait exactement pareil...
Une idée? :-(
Merci bcp.
Reply to: