It was a little disconcerting. Perhaps it was not kernel-upgrade related. I preferred to report it as precautionary measure.
Checking the dpkg logs I have found a couple of previous upgrades. Could the package "devicekit-disks" break my lvm partition?
Preparing to replace devicekit-disks 007-2ubuntu5 (using .../devicekit-disks_007-2ubuntu6_amd64.deb) ... Unpacking replacement devicekit-disks ... Processing triggers for man-db ... Setting up devicekit-disks (007-2ubuntu6) ... Log ended: 2010-04-01 22:43:44
The installation logs of kernel package:
Log started: 2010-04-01 22:47:22 Selecting previously deselected package linux-image-2.6.31-21-generic. Unpacking linux-image-2.6.31-21-generic (from .../linux-image-2.6.31-21-generic_2.6.31-21.59_amd64.deb) ... Done. Selecting previously deselected package linux-headers-2.6.31-21. Unpacking linux-headers-2.6.31-21 (from .../linux-headers-2.6.31-21_2.6.31-21.59_all.deb) ... Selecting previously deselected package linux-headers-2.6.31-21-generic. Unpacking linux-headers-2.6.31-21-generic (from .../linux-headers-2.6.31-21-generic_2.6.31-21.59_amd64.deb) ... Setting up linux-image-2.6.31-21-generic (2.6.31-21.59) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.31-21-generic Running postinst 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: /boot/vmlinuz-2.6.31-21-generic Found kernel: /boot/vmlinuz-2.6.31-20-generic Found kernel: /boot/vmlinuz-2.6.31-19-generic Found kernel: /boot/vmlinuz-2.6.31-17-generic Found kernel: /boot/vmlinuz-2.6.28-17-generic Found kernel: /boot/memtest86+.bin Replacing config file /var/run/grub/menu.lst with new version Updating /boot/grub/menu.lst ... done
Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.31-21-generic ESC[158G * nvidia (185.18.36)... ESC[158G nvidia (185.18.36): Installing module. ............ ...... ^MESC[152G[ OK ] run-parts: executing /etc/kernel/postinst.d/nvidia-common
Setting up linux-headers-2.6.31-21 (2.6.31-21.59) ... Setting up linux-headers-2.6.31-21-generic (2.6.31-21.59) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms * Running DKMS auto installation service for kernel 2.6.31-21-generic ESC[158G * nvidia (185.18.36)... ESC[158G nvidia (185.18.36): Already installed on this kernel. ^MESC[152G[ OK ] run-parts: executing /etc/kernel/header_postinst.d/nvidia-common
Log ended: 2010-04-01 22:48:36
There wasn't a failed boot, just a failed mount point. The /dev/mapper/vg0-lv0 simply didn't exist. Disconcerting.
Thanks.
It was a little disconcerting. Perhaps it was not kernel-upgrade related. I preferred to report it as precautionary measure.
Checking the dpkg logs I have found a couple of previous upgrades. Could the package "devicekit-disks" break my lvm partition?
Preparing to replace devicekit-disks 007-2ubuntu5 (using .../devicekit- disks_007- 2ubuntu6_ amd64.deb) ...
Unpacking replacement devicekit-disks ...
Processing triggers for man-db ...
Setting up devicekit-disks (007-2ubuntu6) ...
Log ended: 2010-04-01 22:43:44
The installation logs of kernel package:
Log started: 2010-04-01 22:47:22 2.6.31- 21-generic. 2.6.31- 21-generic (from .../linux- image-2. 6.31-21- generic_ 2.6.31- 21.59_amd64. deb) ... 2.6.31- 21. 2.6.31- 21 (from .../linux- headers- 2.6.31- 21_2.6. 31-21.59_ all.deb) ... 2.6.31- 21-generic. 2.6.31- 21-generic (from .../linux- headers- 2.6.31- 21-generic_ 2.6.31- 21.59_amd64. deb) ... 2.6.31- 21-generic (2.6.31-21.59) ... img-2.6. 31-21-generic 2.6.31- 21-generic 2.6.31- 20-generic 2.6.31- 19-generic 2.6.31- 17-generic 2.6.28- 17-generic +.bin grub/menu. lst with new version
Selecting previously deselected package linux-image-
Unpacking linux-image-
Done.
Selecting previously deselected package linux-headers-
Unpacking linux-headers-
Selecting previously deselected package linux-headers-
Unpacking linux-headers-
Setting up linux-image-
Running depmod.
update-initramfs: Generating /boot/initrd.
Running postinst 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: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Found kernel: /boot/memtest86
Replacing config file /var/run/
Updating /boot/grub/menu.lst ... done
Examining /etc/kernel/ postinst. d. postinst. d/dkms postinst. d/nvidia- common
run-parts: executing /etc/kernel/
* Running DKMS auto installation service for kernel 2.6.31-21-generic ESC[158G
* nvidia (185.18.36)... ESC[158G nvidia (185.18.36): Installing module.
............
......
^MESC[152G[ OK ]
run-parts: executing /etc/kernel/
Setting up linux-headers- 2.6.31- 21 (2.6.31-21.59) ... 2.6.31- 21-generic (2.6.31-21.59) ... header_ postinst. d. header_ postinst. d/dkms header_ postinst. d/nvidia- common
Setting up linux-headers-
Examining /etc/kernel/
run-parts: executing /etc/kernel/
* Running DKMS auto installation service for kernel 2.6.31-21-generic ESC[158G
* nvidia (185.18.36)... ESC[158G nvidia (185.18.36): Already installed on this kernel.
^MESC[152G[ OK ]
run-parts: executing /etc/kernel/
Log ended: 2010-04-01 22:48:36
There wasn't a failed boot, just a failed mount point. The /dev/mapper/vg0-lv0 simply didn't exist. Disconcerting.
Thanks.