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
wh
> 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; whe
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
> constru
Hi again --
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
4 matches
Mail list logo
