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 if that's important. Simon On 22 February 2011 17:12, Simon Mcnair <simonmcnair@xxxxxxxxx> wrote: > Phil, > I thought it was fixed, but every time I do a reboot it disappears > again. I did the: > pvcreate --restorefile 'simons-lvm-backup' --uuid > 9fAJEz-HcaP-RQ51-fV8b-nxrN-Uqwb-PPnOLJ /dev/md0 and the vgcfgrestore > > the only piece of your advice that I didn't follow was "zero the > superblock on the removed drive" as I thought re-adding it to the > array would do that anyway. Did this cause me problems ? > > proxmox:~# mdadm --assemble --scan -v > mdadm: looking for devices for /dev/md/0 > mdadm: cannot open device /dev/dm-2: Device or resource busy > mdadm: /dev/dm-2 has wrong uuid. > mdadm: cannot open device /dev/dm-1: Device or resource busy > mdadm: /dev/dm-1 has wrong uuid. > mdadm: cannot open device /dev/dm-0: Device or resource busy > mdadm: /dev/dm-0 has wrong uuid. > mdadm: /dev/sdo1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdo > mdadm: /dev/sdo has wrong uuid. > mdadm: /dev/sdn1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdn > mdadm: /dev/sdn has wrong uuid. > mdadm: /dev/sdm1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdm > mdadm: /dev/sdm has wrong uuid. > mdadm: /dev/sdl1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdl > mdadm: /dev/sdl has wrong uuid. > mdadm: /dev/sdk1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdk > mdadm: /dev/sdk has wrong uuid. > mdadm: /dev/sdj1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdj > mdadm: /dev/sdj has wrong uuid. > mdadm: /dev/sdi1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdi > mdadm: /dev/sdi has wrong uuid. > mdadm: /dev/sdh1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdh > mdadm: /dev/sdh has wrong uuid. > mdadm: /dev/sdg1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdg > mdadm: /dev/sdg has wrong uuid. > mdadm: /dev/sdf1 has wrong uuid. > mdadm: no RAID superblock on /dev/sdf > mdadm: /dev/sdf has wrong uuid. > mdadm: cannot open device /dev/sdc1: Device or resource busy > mdadm: /dev/sdc1 has wrong uuid. > mdadm: cannot open device /dev/sdc: Device or resource busy > mdadm: /dev/sdc has wrong uuid. > mdadm: cannot open device /dev/sdb1: Device or resource busy > mdadm: /dev/sdb1 has wrong uuid. > mdadm: cannot open device /dev/sdb: Device or resource busy > mdadm: /dev/sdb has wrong uuid. > mdadm: cannot open device /dev/sda2: Device or resource busy > mdadm: /dev/sda2 has wrong uuid. > mdadm: cannot open device /dev/sda1: Device or resource busy > mdadm: /dev/sda1 has wrong uuid. > mdadm: cannot open device /dev/sda: Device or resource busy > mdadm: /dev/sda has wrong uuid. > > I'm getting frustrated now. It seems like it's fixzed, then next > reboot, BAM, it's gone again. I'm so out of my depth here. > > Please can you help me fix this once and for all ? > > cheers > Simon > > On 20 February 2011 23:39, Phil Turmel <philip@xxxxxxxxxx> wrote: >> On 02/20/2011 06:17 PM, Simon Mcnair wrote: >>> Phil, >>> You are a god amongst men :-) >> >> Heh. I read that out loud to my wife.... >> >>> I seem to have the vast majority of my data. I can't see anything in >>> lost+found and the fsck log doesn't list any filenames etc of missing >>> data. Is there any way for me to find anything that I've lost ? >> >> Not that I know of, short of a list of names from before the crash. >> >> Glad to hear that the family treasures are safe. >> >> 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
