From: Robin Hill <robin@robinhill.me.uk>
To: Patrice <mailinglist@pboenig.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: I was dump, I need help.
Date: Sun, 1 May 2016 12:30:34 +0100 [thread overview]
Message-ID: <20160501113034.GA24215@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <5725DCA9.9010901@pboenig.de>
On Sun May 01, 2016 at 12:38:33pm +0200, Patrice wrote:
> It has a Debian 7 installed and a RAID 5.
> Here some more Informations.
>
> Thank you and best regards.
> Patrice
>
>
>
>
> root@ReadyNAS:/proc# cat mdstat
> Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> md1 : active raid6 sda2[0] sdc2[3] sdb2[2] sdd2[1]
> 1046528 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4]
> [UUUU]
>
> md0 : active raid1 sda1[4] sdd1[3] sdc1[2] sdb1[5]
> 4190208 blocks super 1.2 [4/4] [UUUU]
>
> unused devices: <none>
>
This shows two RAID devices, both up and running without any issues.
> /dev/sda1:
> /dev/sdb1:
> /dev/sdc1:
> /dev/sdd1:
The info provided here is just for the first partition on each disk.
There's definitely at least 2 partitions on each disk (as the second one
is used for md1 above) - are there any others which should be being
assembled into another array? "fdisk -l" will show the partitions for
all disks - if there's more than 2 on sda/b/c/d then we'll need to see
the "mdadm -E" report for each of the others.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
next prev parent reply other threads:[~2016-05-01 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 10:38 I was dump, I need help Patrice
2016-05-01 11:30 ` Robin Hill [this message]
[not found] ` <5726128E.9090309@pboenig.de>
2016-05-02 12:41 ` Robin Hill
2016-05-05 10:00 ` Patrice
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 9:54 Patrice
2016-05-01 9:39 Patrice
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=20160501113034.GA24215@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglist@pboenig.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).