On Sun, Oct 08 2017, Curt wrote: > On Sat, Oct 7, 2017 at 5:29 PM, Phil Turmel <philip@xxxxxxxxxx> wrote: >> On 10/07/2017 04:45 PM, Curt wrote: >> >> Hmm. Please run the assemble again, with the --verbose option, and >> paste all the output here so we can see what's happening. >> >> Also grab the corresponding tail of dmesg (however many lines cover the >> assembly attempt). >> >> Phil > > You wouldn't think reply all would be such a hard thing to remember to do. > > verbose didn't really add anything, here's my full command, maybe I > miss typed something and didn't notice. > > # mdadm --assemble --force --update=revert-reshape --verbose > /dev/md127 /dev/sda1 /dev/sdc1 /dev/sdd1 /dev/sdg1 /dev/sdf1 /dev/sdz1 > mdadm: looking for devices for /dev/md127 > mdadm: superblock on /dev/sdf1 doesn't match others - assembly aborted You get this because sdf1 says: Raid Devices : 7 Total Devices : 7 while sda1 (for example) says: Raid Devices : 8 Total Devices : 6 Preferred Minor : 127 Reshape pos'n : 3799296 (3.62 GiB 3.89 GB) Delta Devices : 1 (7->8) mdadm cannot reconcile this difference. It appears that sdf1 was never involved in any reshape. So you need to revert the reshape before trying to include sdf1 into the array. Clearly you need at least 6 devices that were involved in the reshape to do this. I haven't been following closely ... do you have 6 such devices? NeilBrown > > I've got nothing in dmesg or messages > > If I can't get the old drive to work. Is there any chance to still > getting some data from the other drives? Either running the above > without sdf or worse comes to worse the assume clean someone mentioned > before. > > Cheers, > Curt > -- > 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
Attachment:
signature.asc
Description: PGP signature
