Phil,
phew I didn't know that:
"mdadm: /dev/sdo has wrong uuid.
mdadm: /dev/sdn1 has wrong uuid."
was just that the array UUID didn't match mdadm.conf, it would be nice
if it said:
"mdadm: /dev/sdo uuid does not match mdadm.conf.
mdadm: /dev/sdn1 uuid does not match mdadm.conf"
my mdadm.conf now reads
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
# ARRAY /dev/md/0 level=raid5 metadata=1.1 num-devices=10
UUID=0a72e40f:aec6f80f:a7004457:1a84a7a8 name=pro�lox:0
ARRAY /dev/md/0 metadata=1.1 UUID=12c2af00:10681e10:fb17e449:1404739c
name=proxmox:0
I'm afraid to do another reboot incase something else goes wrong ;-).
Just for my info, when I only have a single array there isn't much
chance of it being assigned anything other than md0, so could I not just
leave mdadm.conf empty ?
cheers
Simon
On 22/02/2011 18:23, Phil Turmel wrote:
On 02/22/2011 12:14 PM, Simon Mcnair wrote:
was this anything to do with the dist-upgrade that I performed ?
mdadm has upgraded again to
proxmox:~# mdadm -V
mdadm - v3.1.4 - 31st August 2010
No, but you probably can't do any more "--create --assume-clean" operations with that array.
As for the assembly errors, its probably an out-of-date mdadm.conf.
My server's looks like this:
DEVICE /dev/sd[a-z][1-9]
ARRAY /dev/md23 UUID=c3cbe096:fc43d939:8aa66230:708c5670
ARRAY /dev/md22 UUID=1438a239:aa03c3f9:68e051d7:b59a6219
ARRAY /dev/md21 UUID=4b47d0f6:16f0e352:c67a2185:feb0b573
ARRAY /dev/md20 UUID=7676c77e:6ae70f65:30a170a2:b1a1b242
Yours probably needs to be updated with the new md0 uuid. Its not your boot drive, so your initramfs shouldn't matter.
Phil
--
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
