Has anyone else installed that kernel package and been able to boot that kernel?
After installing the package, 2 new entries were added to the grub menu as is normal.
Selecting any of those 2 entries gives
Loading Linux 3.2.0-4-686-pae... Error: file not found.
(1) 'edit' an entry, 'F2' to enter grub console, and
It lists the kernel file and the initrd file correctly - both versions 3 and 4 of the files are there.
(2) When I edit the first entry and replace 4 by 3, it boots version 3 ok
(3) When I edit the version-3 entry and replace 3 by 4 it gives the error again.
(4) I did a file system check on the filesystem in question - no problems reported
Here is my /boot/grub/grub.cfg: http://crunchbanglinux.org/pastebin/1888
BTW: this is a pure sid install - will take it further to Debian if necessary.
Last edited by xaos52 (2012-10-10 16:49:33)
a) Something gone wrong with the install itself? Maybe try reinstalling the kernel.
b) Did you try rebuilding the initramfs? I've had it not load lvm in time, but that doesn't seem to be the case here. Still, it might be pointing to a wrong file or something.
I installed it with smxi and saw nothing special.
I had done b) already, but forgot to mention it
Did a) now, and the remove gave me some errors about damaged links, but removed them.
xaos52@crunchie:~$ sudo apt-get remove linux-image-3.2.0-4-686-pae Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-3.2.0-4-686-pae linux-image-686-pae 0 upgraded, 0 newly installed, 2 to remove and 15 not upgraded. After this operation, 81.7 MB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 106964 files and directories currently installed.) Removing linux-image-686-pae ... Removing linux-image-3.2.0-4-686-pae ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae update-initramfs: Deleting /boot/initrd.img-3.2.0-4-686-pae run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-3-686-pae Found initrd image: /boot/initrd.img-3.2.0-3-686-pae Found Debian GNU/Linux (6.0) on /dev/mapper/vg01-cb--10--20110207 Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/vg01-testing Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/vg01-waldorf Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/vg01-waldorf20120927 done The link /vmlinuz is a damaged link Removing symbolic link vmlinuz You may need to re-run your boot loader The link /initrd.img is a damaged link Removing symbolic link initrd.img You may need to re-run your boot loader You have new mail in /var/mail/xaos52 xaos52@crunchie:~$
Anyhow, grub is not configured to use the links, it uses the files under /boot directly.
I then re-installed the new kernel manually. Everything seemed OK, but grub gives same error again.
Thanks, el_koraco. I will report a bug on Debian. See what they say.
Last edited by xaos52 (2012-10-10 11:35:52)
I somehow managed to create two logical volumes with the same UUID:
/dev/mapper/vg01-swap: UUID="d6623057-e536-40bd-b76b-8c696b8f115f" TYPE="swap" /dev/sda1: UUID="LvHROg-iV9s-BTwy-IVre-PIlH-TmyL-MZ2b73" TYPE="LVM2_member" /dev/mapper/vg01-waldorf: UUID="a3011c84-7886-48a0-9c3e-56bfcd14f117" TYPE="ext4" /dev/mapper/vg01-cb--10--20110207: UUID="492c58e3-5805-4eb8-ac8e-3bdae4cf5bab" TYPE="ext4" /dev/mapper/vg01-arch: UUID="5738a748-3e67-413a-bc10-cb3f0235779c" TYPE="ext4" /dev/mapper/vg01-sid: UUID="3c6bf205-af67-4c09-888e-1599de45418b" TYPE="ext4" /dev/mapper/vg01-waldorf20120927: UUID="d60e7872-4533-4ffa-83a1-ccd6ef2a5a33" TYPE="ext4" /dev/mapper/vg01-testing: UUID="3c6bf205-af67-4c09-888e-1599de45418b" TYPE="ext4" /dev/mapper/vg01-SidsHome: UUID="2ef2ce2a-fcf4-41ed-811e-d7ba41b62ac2" TYPE="ext4" /dev/sdd1: UUID="9820-444C" TYPE="vfat" /dev/sde5: LABEL="Hitachi5" UUID="d26ab4c9-799f-41e2-ade8-d8ec90058139" TYPE="ext4" /dev/sde6: LABEL="Hitachi6" UUID="0318fc18-1c71-4094-a4c8-22c6c0ad45f0" TYPE="ext4" /dev/sde7: UUID="807634de-f48d-4d33-84d8-1ee1487887ee" TYPE="ext4" /dev/sde8: UUID="da135743-a888-40fc-9861-e7e1a86a03ee" TYPE="ext4" /dev/sde9: UUID="013cb5c2-04f1-4769-aca8-26c76b818759" TYPE="ext4" /dev/sde10: UUID="7C840E24603A73EE" TYPE="ntfs" /dev/sde11: UUID="f2acfc56-3723-4e7a-9417-d1747de24d7f" TYPE="ext4" /dev/sde12: UUID="36c2d715-32c9-4176-9c14-78e062823dff" TYPE="ext4" /dev/sde13: UUID="F876-3257" TYPE="vfat"
vg01-sid and vg01-testing have the same UUID. How is that possible?
Removing the 'vg01-testing' logical volume and running update-grub solved my problem.
Reason: grub searches filesystems based on UUID. Apparently it found the vg01-testing LV first, which did not contain the new kernel. So it said 'file not found.", and rightly so.
Problem replaced by a new one: how can one create 2 LVM's with the same UUID?
Last edited by xaos52 (2012-10-10 16:50:25)
Reason: grub searches filesystems based on UUID.
Seems like another good reason to have a separate /boot. lvm shouldn't create two LVs with the same UUID in any case. This looks like a valid reason to file an upstream bug.
Woah, that was cool, and bad at the same time. I never knew one could have two volumes with the same UUID. How is this even possible? No need to try and recreate it, it was just an amazing fluke that I never knew existed.
Glad you have it sorted out.
( o< -Penguins rule!
Computers do not have problems, they have users. ~Cope57