1 |
On Sun, May 4, 2014 at 2:48 PM, J. Roeleveld <joost@××××××××.org> wrote: |
2 |
> On Sunday, May 04, 2014 01:15:51 PM Neil Bothwick wrote: |
3 |
>> On Sat, 03 May 2014 20:40:47 +0200, J. Roeleveld wrote: |
4 |
>>>> |
5 |
>>>> * SystemRescueCD and the Gentoo minimal installation CD both start |
6 |
>>>> any raid arrays they find and apply their own names to them. It is |
7 |
>>>> then impossible, or so I thought, to resume an interrupted |
8 |
>>>> installation process. Of course, all I had to do was "mdadm |
9 |
>>>> --stop /dev/md127" etc. |
10 |
>>> |
11 |
>>> Yes, I noticed that annoyance myself. I would much prefer it to default |
12 |
>>> to more logical names. |
13 |
>> |
14 |
>> ISTR that's because of the hostname stored in the RAID, so when you plug |
15 |
>> the array into another computer, it doesn't clobber any existing array |
16 |
>> names. I had this happen when transplanting an array to a new system. |
17 |
>> There is a sequence of commands to reset the names but it was a while ago |
18 |
>> and all I remember is that the sequence started with "man lvm". |
19 |
> |
20 |
> Actually, the steps are: |
21 |
> 1) invalidate the RAID |
22 |
> 2) create a new, broken, RAID using the invalidatd disk |
23 |
> 3) copy data to new RAID |
24 |
> 4) delete md127 |
25 |
> 5) add other disk from md127 to md1 |
26 |
> |
27 |
> Or something to that effect. |
28 |
> A "rename" option or even a "I_KNOW_WHAT_I_AM_DOING_JUST_KEEP_THE_SAME_NAME" |
29 |
> option, which would be enabled by default when booting with sysresccd, would |
30 |
> be nice. |
31 |
|
32 |
There's an mdadm option to change the hostname ("--homehost=<hostname> |
33 |
--update=homehost") but in the case of 0.9 metadata it'll change the |
34 |
uuid. |
35 |
|
36 |
You can also set "HOMEHOST=none" in mdadm.conf before creating an |
37 |
array, but I'm not sure how the md device will be numbered if you then |
38 |
assemble it on a box with "HOMEHOST=system" set. |