On Tue, Sep 13, 2011 at 5:38 PM, NeilBrown <neilb@xxxxxxx> wrote: > On Tue, 13 Sep 2011 17:05:06 +1000 Andriano <chief000@xxxxxxxxx> wrote: > >> On Tue, Sep 13, 2011 at 4:44 PM, NeilBrown <neilb@xxxxxxx> wrote: >> > On Tue, 13 Sep 2011 16:33:36 +1000 Andriano <chief000@xxxxxxxxx> wrote: >> > >> >> > >> >> >> Hello Linux-RAID mailing list, >> >> >> >> >> >> I have an issue with my RAID6 array. >> >> >> Here goes a short description of the system: >> >> >> >> >> >> opensuse 11.4 >> >> >> Linux 3.0.4-2-desktop #1 SMP PREEMPT Wed Aug 31 09:30:44 UTC 2011 >> >> >> (a432f18) x86_64 x86_64 x86_64 GNU/Linux >> >> >> Gigabyte EP35C-DS3 motherboard with 8 SATA ports + SuperMicro >> >> >> AOC-SASLP-MV8 based on Marvel 6480, firmware updated to 3.1.0.21 >> >> >> running mdadm 3.2.2, single array consists of 10 2T disks, 8 of them >> >> >> connected to the HBA, 2 - motherboard ports >> >> >> >> >> >> I had some issues with one of the onboard connected disks, so tried to >> >> >> plug it to different ports, just to eliminate possibly faulty port. >> >> >> After reboot, suddenly other drives got kicked out from the array. >> >> >> Re-assembling them gives weird errors. >> >> >> >> >> >> --- some output --- >> >> >> [3:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdb >> >> >> [5:0:0:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdc >> >> >> [8:0:0:0] disk ATA ST32000542AS CC34 /dev/sdd >> >> >> [8:0:1:0] disk ATA ST32000542AS CC34 /dev/sde >> >> >> [8:0:2:0] disk ATA ST32000542AS CC34 /dev/sdf >> >> >> [8:0:3:0] disk ATA ST32000542AS CC34 /dev/sdg >> >> >> [8:0:4:0] disk ATA ST32000542AS CC34 /dev/sdh >> >> >> [8:0:5:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdi >> >> >> [8:0:6:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdj >> >> >> [8:0:7:0] disk ATA ST2000DL003-9VT1 CC32 /dev/sdk >> >> >> >> >> >> #more /etc/mdadm.conf >> >> >> DEVICE partitions >> >> >> ARRAY /dev/md0 level=raid6 UUID=82ac7386:a854194d:81b795d1:76c9c9ff >> >> >> >> >> >> #mdadm --assemble --force --scan /dev/md0 >> >> >> mdadm: failed to add /dev/sdc to /dev/md0: Invalid argument >> >> >> mdadm: failed to add /dev/sdb to /dev/md0: Invalid argument >> >> >> mdadm: failed to add /dev/sdh to /dev/md0: Invalid argument >> >> >> mdadm: /dev/md0 assembled from 7 drives - not enough to start the array. >> >> >> >> >> >> dmesg: >> >> >> [ 8215.651860] md: sdc does not have a valid v1.2 superblock, not importing! >> >> >> [ 8215.651865] md: md_import_device returned -22 >> >> >> [ 8215.652384] md: sdb does not have a valid v1.2 superblock, not importing! >> >> >> [ 8215.652388] md: md_import_device returned -22 >> >> >> [ 8215.653177] md: sdh does not have a valid v1.2 superblock, not importing! >> >> >> [ 8215.653182] md: md_import_device returned -22 >> >> >> >> >> >> mdadm -E /dev/sd[b..k] gives exactly the same Magic number and Array >> >> >> UUID for every disk, all checksums are correct, >> >> >> the only difference is - Avail Dev Size : 3907028896 is the same for >> >> >> 9 disks, and 3907028864 for sdc >> >> > >> >> > Please provide that output so we can see it too - it might be helpful. >> >> > >> >> > NeilBrown >> >> >> >> >> >> # mdadm --assemble --force --update summaries /dev/md0 /dev/sdc >> >> mdadm: --update=summaries not understood for 1.x metadata >> >> >> > >> > Sorry - I was too terse. >> > >> > I meant that output of "mdadm -E ...." >> > >> > NeilBrown >> > >> > >> >> >> >> > >> >> >> >> >> >> mdadm --assemble --force --update summaries /dev/sd.. - didn't improve anything >> >> >> >> >> >> >> >> >> I would really appreciate if someone could point me to the right direction. >> >> >> >> >> >> thanks >> >> >> >> >> >> Andrew >> >> >> -- >> >> >> 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 >> >> > >> >> > >> > >> > >> >> /dev/sdb: >> Magic : a92b4efc >> Version : 1.2 >> Feature Map : 0x0 >> Array UUID : 82ac7386:a854194d:81b795d1:76c9c9ff >> Name : hnas:0 (local to host hnas) >> Creation Time : Wed Jan 19 21:17:33 2011 >> Raid Level : raid6 >> Raid Devices : 10 >> >> Avail Dev Size : 3907028896 (1863.02 GiB 2000.40 GB) >> Array Size : 31256230912 (14904.13 GiB 16003.19 GB) >> Used Dev Size : 3907028864 (1863.02 GiB 2000.40 GB) >> Data Offset : 272 sectors >> Super Offset : 8 sectors >> State : active >> Device UUID : 4b31edb8:531a4c14:50c954a2:8eda453b >> >> Update Time : Mon Sep 12 22:36:35 2011 >> Checksum : 205f92e1 - correct >> Events : 6446662 >> >> Layout : left-symmetric >> Chunk Size : 64K >> >> Device Role : Active device 6 >> Array State : AAAAAAAAAA ('A' == active, '.' == missing) >> /dev/sdc: >> Magic : a92b4efc >> Version : 1.2 >> Feature Map : 0x0 >> Array UUID : 82ac7386:a854194d:81b795d1:76c9c9ff >> Name : hnas:0 (local to host hnas) >> Creation Time : Wed Jan 19 21:17:33 2011 >> Raid Level : raid6 >> Raid Devices : 10 >> >> Avail Dev Size : 3907028864 (1863.02 GiB 2000.40 GB) >> Array Size : 31256230912 (14904.13 GiB 16003.19 GB) >> Data Offset : 304 sectors >> Super Offset : 8 sectors >> State : clean >> Device UUID : afa2f348:88bd0376:29bcfe96:df32a522 >> >> Update Time : Tue Sep 13 11:50:18 2011 >> Checksum : ee1facae - correct >> Events : 6446662 >> >> Layout : left-symmetric >> Chunk Size : 64K >> >> Device Role : Active device 5 >> Array State : AAAAAA.AAA ('A' == active, '.' == missing) > (snip) > > Thanks. > > The only explanation I can come up with is that the devices appear to be > smaller for some reason. > Can you run > blockdev --getsz /dev/sd? > > and report the result? > They should all be 3907029168 (Data Offset + Avail Dev Size). > If any are smaller - that is the problem. > > NeilBrown > > Apparently you're right blockdev --getsz /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk 3907027055 3907027055 3907029168 3907029168 3907029168 3907029168 3907027055 3907029168 3907029168 3907029168 sdb, sdc and sdh - are smaller and they are problem disks So what would be a solution to fix this issue? thanks Andrew -- 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
