I was in the process of moving logical volume extents onto an raid 10 array assembled with mdadmin. One of the logical volumes moved was the root directory (debian testing system) which was previously on a single physical volume. The system is now unbootable. The error message reported in grub rescue is lvmid/ex....lognuuid/another long uuid not found.
I am guessing that the two disks not found are the two currently in the raid 10 array on which the root directory now resides. I am also guessing that this is because the array in not being assembled before the root local volume.
When I boot with the installer media and go into rescue mode, I can not boot the root directory. However, if I first choose the option to assemble an array, and then chroot into the root directory I succeed. I've tried everything I could think of over the past 24 hours. Including various combinations of changing /etc/mdadm/mdadm.conf, update-initramfs -u.
I even tried undoing pvmove, but couldn't because of an lvmetad.socket error. Something must be missing in the chroot rescue environment needed to go this route.
The fact that if I manually assemble the array prior to chrooting, I can get a working system indicates either that the array is not being assembled at all, or not in time (and hence not at all).
Can anyone suggest a fix I could try? I am guessing there is something I can do to get the system functional, but I'm at a loss as to how to proceed.