On Mon, Jan 7, 2013 at 12:52 PM, Hendrik Boom <hend...@topoi.pooq.com> wrote: > On Mon, 07 Jan 2013 00:14:31 -0700, Bob Proulx wrote: >> Hendrik Boom wrote: >> Did you rebuild the initrd images for the booting kernel after having >> done this? >> >> Example: >> >> dpkg-reconfigure linux-image-3.2.0-4-amd64 > > dpkg-reconfigure linux-image-2.6.32-5-amd64 > > Different kernel version (this is squeeze, after all) > but it seemed to work. > > Next to reboot. > > OOPS > > Won't boot. Gets stick at the initramfs prompt after complaining > that it can't run /sbin/init > > I look with ls, and discover that /sbin exists, bit is totally > empty. that seems a good reason to be unable to run /sbin/init. > > And ls / clearly shows me a root directory which is *not* my > system's root directory. Presumably it's at the stage where it > hasn't gotten around to mounting the real root partition yet. > > It looks to me that dpkg-reconfigure linux-image-2.6.32-5-amd64 > has somehow built me an unusable initrd. Puzzling, because doesn't > is do that every time it upgrades the kernel anyway? And this is > Debiann stable I'm running. > > I tried booting with an old kernel, but this made no difference. > Puzzling, because why would dpkg-reconfigure linux-image-2.6.32-5-amd64 > mess with the initrds of other kernels? > > Maybe that's not the problem. > > Nor did it make a difference whether I booted with grub2 or lilo. > Annoying, since I maintain these two independent boot methods just > in case. > > Yes, it has recognised both RAIDs. > > Once I had to tell initramfs > > vgchange -a y > > to make sure it saw the logical volumes inside my RAIDs. > > Help!
Boot with "break=bottom" on the "linux" line and check whether your mdraid arrays and lvm volumes are assembled. -- 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/CAOdo=SxihnQ=zfr_thc8tvebe4ddessy32p0qwiw7u1qr3k...@mail.gmail.com
