Re: Towards a working initrd.img file
Thanks for all the helpful ideas, all! As it turns out, the solution to my problem was straightforward: I needed to do a dpkg-reconfigure mdadm, and specify that all multi-drive arrays need to be started in order to access root. Once that was completed, update-initramfs produced an initrd.img which permits booting on my computer. Like the man said about sharpening and aligning a plane, "None of this is rocket science, but at the same time you're not born knowing it!" -PT
RE: Towards a working initrd.img file
> On Fri, 3 Dec 2010 07:15:38 -0500 wrote: > > On Fri, Dec 3, 2010 at 1:12 AM, Peter Tenenbaum > wrote: > > > > I've been having a problem since migrating my file system to RAID-1, which > > is that when I run update-initramfs, it produces an initrd.img file which > > doesn't work correctly; when I replace it with the initrd.img file which was > > constructed by the OS installer, I can boot correctly in my newly-RAIDified > > system. > > > > So my question: how do I configure update-initramfs so that it > > automatically includes the kernel modules I need? I note that there is a > > file, /etc/initramfs-tools/modules, which in my case has no module names in > > it; presumably I can look at /proc/modules and copy the names of all the > > modules shown in the latter into the former. Would that solve my problem? > > Is there a better way? > > I assume that this won't return anything but what do you get when you run > gzip --decompress --standout /boot/initrd.img-non-working | cpio > --list | grep mdadm > gzip --decompress --standout /boot/initrd.img-non-working | cpio > --list | grep '/md/' > > I have an mdadm'd install of sid in which there isn't anything > mdraid-related in "/etc/initramfs-tools". > > Does "/usr/share/initramfs-tools/hooks/mdadm" exist? > FYI. This is my output of the given command, and mdadm works in my system. gzip --decompress --stdout /boot/initrd.img-2.6.32-5-xen-amd64 | cpio --list | grep mdadm 57966 blocks scripts/local-top/mdadm etc/mdadm etc/mdadm/mdadm.conf sbin/mdadm Wish I could have been of more help. Good luck. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/bay148-w34842ebf314d23bc07aff6ef...@phx.gbl
Re: Towards a working initrd.img file
On Fri, Dec 3, 2010 at 1:12 AM, Peter Tenenbaum wrote: > > I've been having a problem since migrating my file system to RAID-1, which > is that when I run update-initramfs, it produces an initrd.img file which > doesn't work correctly; when I replace it with the initrd.img file which was > constructed by the OS installer, I can boot correctly in my newly-RAIDified > system. > > So my question: how do I configure update-initramfs so that it > automatically includes the kernel modules I need? I note that there is a > file, /etc/initramfs-tools/modules, which in my case has no module names in > it; presumably I can look at /proc/modules and copy the names of all the > modules shown in the latter into the former. Would that solve my problem? > Is there a better way? I assume that this won't return anything but what do you get when you run gzip --decompress --standout /boot/initrd.img-non-working | cpio --list | grep mdadm gzip --decompress --standout /boot/initrd.img-non-working | cpio --list | grep '/md/' I have an mdadm'd install of sid in which there isn't anything mdraid-related in "/etc/initramfs-tools". Does "/usr/share/initramfs-tools/hooks/mdadm" exist? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimmuar2saeka4cr_ky6w-pwjdbwj1drsjg9z...@mail.gmail.com
