On Sun, 04 May 2014 20:48:05 +0200, J. Roeleveld wrote: > > ISTR that's because of the hostname stored in the RAID, so when you > > plug the array into another computer, it doesn't clobber any existing > > array names. I had this happen when transplanting an array to a new > > system. There is a sequence of commands to reset the names but it was > > a while ago and all I remember is that the sequence started with "man > > lvm". > > Actually, the steps are: > 1) invalidate the RAID > 2) create a new, broken, RAID using the invalidatd disk > 3) copy data to new RAID > 4) delete md127 > 5) add other disk from md127 to md1
It was far simpler than that and did not involve copying data. You can change the hostname using one of the mdadm management commands AFAIR (I meant man mdadm not man lvm of course). > A "rename" option or even a > "I_KNOW_WHAT_I_AM_DOING_JUST_KEEP_THE_SAME_NAME" option, which would be > enabled by default when booting with sysresccd, would be nice. You can specify device names for md devices on the kernel command line, but an option to ignore the hostname would be handy and just keep the current naming system, at your own risk, would be handy. -- Neil Bothwick .sig a .sog of sixpence.
signature.asc
Description: PGP signature
