Re: Volume group "vg00" not found
Ben c'est pas fini !
J'ai une entrée sur le noyau précédent : 2.6.26-1. Je l'ai utilisé et
la machine à booter sans Xorg, mais bon j'ai une sessiosn
Je lance un apt-get install --reinstall sur le paquet
linux-image-2.6.26-2-amd64 pas mieux avec la trace suivante
Dépaquetage de la mise à jour de linux-image-2.6.26-2-amd64 ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /vmlinuz-2.6.26-2-amd64 Found
kernel: /vmlinuz-2.6.26-1-amd64 Updating /boot/grub/menu.lst ... done
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools
Paramétrage de linux-image-2.6.26-2-amd64 (2.6.26-15) ...
Running depmod.
Running mkinitramfs-kpkg.
Deprecation WARNING: use update-initramfs(8)
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Not updating initrd symbolic links since we are being
updated/reinstalled (2.6.26-15 was configured last, according to dpkg)
Not updating image symbolic links since we are being
updated/reinstalled (2.6.26-15 was configured last, according to dpkg)
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ...
found: /boot/grub/menu.lst Searching for splash image ... none found,
skipping ... Found kernel: /vmlinuz-2.6.26-2-amd64
Found kernel: /vmlinuz-2.6.26-1-amd64
Updating /boot/grub/menu.lst ... done
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-toolsd'ouverte
Alors je suis passé brutal :
yan:~# update-initramfs -u -k 2.6.26-2-amd64
update-initramfs: Generating /boot/initrd.img-2.6.26-2-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Pas mieux au boot pas possible de démarrer => toujours pas
de /dev/md0...
Une nouvelle idée avant la réinstall de ce WE ?
Bonsoir
Yann.
Reply to: