From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon McNair Subject: Re: Linux software RAID assistance Date: Tue, 22 Feb 2011 18:36:22 +0000 Message-ID: <4D640226.5010505@gmail.com> References: <4D540F6C.6050904@gmail.com> <4D5C2260.3020800@gmail.com> <4D5C273E.7020609@turmel.org> <4D5C4176.80604@gmail.com> <4D5C4204.5020106@turmel.org> <1377706586882297883@unknownmsgid> <4D5C6016.6060809@turmel.org> <4D5D2723.1010101@turmel.org> <6037962689649361915@unknownmsgid> <4D5D52AE.8070602@turmel.org> <4D5FE208.5020700@turmel.org> <4D5FED98.6060407@turmel.org> <4D61707D.4040304@turmel.org> <4D61A64B.60907 08@turmel.org> <4D63FF1F.4030201@turmel.org> Reply-To: simonmcnair@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4D63FF1F.4030201@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Phil Turmel Cc: NeilBrown , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids 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=20 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=3Droot group=3Ddisk mode=3D0660 auto=3Dyes HOMEHOST MAILADDR root # ARRAY /dev/md/0 level=3Draid5 metadata=3D1.1 num-devices=3D10=20 UUID=3D0a72e40f:aec6f80f:a7004457:1a84a7a8 name=3Dpro=EF=BF=BDlox:0 ARRAY /dev/md/0 metadata=3D1.1 UUID=3D12c2af00:10681e10:fb17e449:140473= 9c=20 name=3Dproxmox:0 I'm afraid to do another reboot incase something else goes wrong ;-). =20 Just for my info, when I only have a single array there isn't much=20 chance of it being assigned anything other than md0, so could I not jus= t=20 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" oper= ations 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=3Dc3cbe096:fc43d939:8aa66230:708c5670 >> ARRAY /dev/md22 UUID=3D1438a239:aa03c3f9:68e051d7:b59a6219 >> ARRAY /dev/md21 UUID=3D4b47d0f6:16f0e352:c67a2185:feb0b573 >> ARRAY /dev/md20 UUID=3D7676c77e:6ae70f65:30a170a2:b1a1b242 > Yours probably needs to be updated with the new md0 uuid. Its not yo= ur boot drive, so your initramfs shouldn't matter. > > Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html