On Mon, 07 Jan 2013 03:40:07 -0500, Tom H wrote: > On Mon, Jan 7, 2013 at 3:19 AM, Tom H <tomh0...@gmail.com> wrote: >> On Sun, Jan 6, 2013 at 9:35 PM, Hendrik Boom <hend...@topoi.pooq.com> wrote: >>> ... ... >>> Any ideas where to look? Or how to work around the problem? >> >> Is the new array listed in mdadm.conf? >> >> Did you rebuild your initramfs?
No, and no, and that's probably the problem. > > Was the new gpt array built on the box where it isn't mounting? Yes. > If > not, you have to mount it whilst updating the hostname in the metadata > (I've forgotten the exact mdadm command). If the metadata doesn't have > the correct hostname, the "homehost", it either doesn't assemble and > mount the array or assembles and mounts it but starts the array > numbering at the other end of the spectrum, "md127" for the first > "foreign" array, "md126" for the second, etc. Interesting. Presumably to avoid the problem of moving hard drives with fragments of RAIDs from screwing up. -- hendrik -- 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/kceq97$1fn$3...@ger.gmane.org
