Leon Woestenberg wrote: > On 4/24/07, Leon Woestenberg <leon.woestenberg@xxxxxxxxx> wrote: >> Hello, >> >> On 4/23/07, David Greaves <david@xxxxxxxxxxxx> wrote: >> > There is some odd stuff in there: >> > >> [root@localhost ~]# mdadm -v --assemble --scan >> --config=/tmp/mdadm.conf --force >> [...] >> mdadm: no uptodate device for slot 1 of /dev/md0 >> mdadm: no uptodate device for slot 2 of /dev/md0 >> [...] >> > So, the problem I am facing is that the slot number (as seen with > --examine) is invalid on two and therefore they won't be recognized as > valid drives for the array. > > Is there any way to override the slot number? I could not find > anything in mdadm or mdadm.conf to override them. Yes --create, see my original reply. Essentially all --create does is create superblocks with the data you want (eg slot numbers). It does not touch other 'on disk data'. It is safe to run the *exact same* create command on a dormant array at any time after initial creation - the main side effect is a new UUID. (Neil - yell if I'm wrong). The most 'dangerous' part is to create a superblock with a different version. If you wanted to experiment (maybe with loopback devices) you could try --create'ing an array with 4 devices to simulate where you were. Then do the --create again with 2 devices missing. This should end up with 2 devices with one UUID, 2 with another. Then do an --assemble using --force and --update=uuid. Report back if you do this... Cheers David - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
