All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: lists@xunil.at
Cc: linux-raid@vger.kernel.org
Subject: Re: Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm?
Date: Thu, 28 Jun 2012 16:32:05 +1000	[thread overview]
Message-ID: <20120628163205.2c6a1122@notabene.brown> (raw)
In-Reply-To: <4FE9BFC1.5070607@xunil.at>

[-- Attachment #1: Type: text/plain, Size: 3515 bytes --]

On Tue, 26 Jun 2012 15:57:21 +0200 "Stefan G. Weichinger" <lists@xunil.at>
wrote:

> 
> Greets,
> 
> I currently try to re-add 2 disks to a RAID6 array.
> 
> There were 4 disks in a Fujitsu Q800 NAS, the RAID6 was done via WebGUI.
> 
> 2 disks have been removed from the array and I am not able to re-add the
> old disks or add new disks via WebGUI.
> 
> The support told me to "re-insert disks, if it doesn't work, rebuild
> array" ... cool. What do I need a RAID for then ??
> 
> Anway.
> 
> Entered hacking mode ;-) at least in my terms.
> 
> sshed into box.
> 
> To get it short:
> 
> Currently the RAID6 array /dev/md0 is:
> 
> md0 : active raid6 sdc3[2] sdd3[3]
>       3903891200 blocks level 6, 64k chunk, algorithm 2 [4/2] [__UU]
> 
> So I would like to re-add sda3 and sdb3 ...
> 
> I get:
> 
> # mdadm /dev/md0 -a /dev/sda3
> mdadm: /dev/sda3 not large enough to join array
> 
> oops!
> 
> But the comparison shows:
> 
> [~] # fdisk -l /dev/sda
> 
> Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sda1               1          66      530125   83  Linux
> /dev/sda2              67         132      530142   83  Linux
> /dev/sda3             133      243138  1951945693   83  Linux
> /dev/sda4          243139      243200      498012   83  Linux
> 
> [~] # fdisk -l /dev/sdc
> 
> Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1               1          66      530125   83  Linux
> /dev/sdc2              67         132      530142   83  Linux
> /dev/sdc3             133      243138  1951945693   83  Linux
> /dev/sdc4          243139      243200      498012   83  Linux
> 
> -> identical partitions
> 
> ---
> 
> Could that relate to this issue:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500309

Nope.  It was an earlier bug fixed in 2.6.5 by

 http://neil.brown.name/git?p=mdadm;a=commitdiff;h=7a3be72fc621b4a7589e923cf065


> 
> The NAS seems to run some ubuntu:
> 
> # cat /proc/version
> Linux version 2.6.33.2 (root@NasX86-5) (gcc version 4.1.3 20070929
> (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Mon Sep 13 04:28:32 CST 2010

Does the "X86" in there suggest and x86 processor?  What does "uname -a" show?


> 
> and brings an older mdadm:
> 
> # mdadm --version
> mdadm - v2.6.3 - 20th August 2007
> 
> 
> If that is the issue, is there a way to use some newer binary (magically
> transferred to me by mail or URL ;-) ) of mdadm to re-add disks?

You mean the NAS didn't come with a complete build environment and sources
for all programs?  Outrageous.

If you have a machine with the same arch at the NAS, you could

  git clone git://neil.brown.name/mdadm -b mdadm-2.6.5
  cd mdadm
  make mdadm.static CWFLAGS=-Wall

and then use the "mdadm.static" on the NAS.

NeilBrown


> 
> I would really really like to avoid to rebuild that array ...
> 
> Thanks in advance, looking forward to your hints, Stefan!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2012-06-28  6:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 13:57 Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm? Stefan G. Weichinger
2012-06-27 10:17 ` Stefan G. Weichinger
2012-06-27 11:34   ` Stefan G. Weichinger
2012-06-27 11:38     ` Stefan G. Weichinger
2012-06-28  6:32 ` NeilBrown [this message]
2012-06-28  8:59   ` Stefan G. Weichinger
2012-06-28  9:14     ` Stefan G. Weichinger
2012-06-28  9:23       ` Stefan G. Weichinger
2012-06-28 11:22       ` NeilBrown
2012-06-28 15:56         ` Stefan G. Weichinger
2012-06-28 18:25           ` Stefan G. Weichinger
2012-06-28 21:36             ` NeilBrown
2012-06-29  8:18               ` Stefan G. Weichinger
2012-07-02  8:30                 ` Stefan G. Weichinger
2012-06-28 21:39           ` NeilBrown
2012-06-28  9:39     ` NeilBrown
2012-06-28  9:42       ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120628163205.2c6a1122@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@xunil.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.