On Thu, 15 Oct 2009 00:56:20 -0400 Mitchell Laks <ml...@post.harvard.edu> wrote:
> On 00:05 Thu 15 Oct , Mitchell Laks wrote: > > How can I work around this and what to do? My old kernel 2.6.26 > > works fine.... How to force initrd to load the dm-mod and other > > device-mapper kernel modules? > > I have added > dm_mod > dm_log > dm_snapshot > dm_mirror > to > /etc/initramfs-tools/modules > file and then > did > dpkg-reconfigure linux-image-2.6.30-2-686-bigmen > and it regenerated the initrd.img file > but then when I selected this kernel in grub2 > it still could not find the > /dev/mapper/debian-root device. > > I was dumped by grub2 into Busybox > (initramfs) > and when I ran > (initramfs) cat /proc/modules > > sure enough these modules were now in the kernel. > However when I did ls /dev/mapper all I see is > /dev/mapper/control > and I cannot find the > /dev/mapper/debian-root > directory > > which exists when I boot into the vmlinuz-2.6.26-2-686 kernel. > > So why is grub2 failing to boot in the 2.6.30-2-686 kernel? > > Mitchell > > > > > Hi, Mitchell FWIW I have exactly the same problem... Whew !!! I didn't cause this mess....I hope!!! Thanks more that you know... BTW I haven't fix mine yet... But getting some help. Jack Jack -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
