From: Phil Turmel <philip@turmel.org>
To: o1bigtenor <o1bigtenor@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Advice requested
Date: Sun, 1 Nov 2015 15:55:15 -0500 [thread overview]
Message-ID: <56367C33.6060703@turmel.org> (raw)
In-Reply-To: <CAPpdf58rFk95KYGc3WkOQGg+ytJ3rcmWtu23ZU3-ss=vx_GfhQ@mail.gmail.com>
Hi Dee,
On 10/31/2015 07:55 AM, o1bigtenor wrote:
> Greetings
>
> I had a raid 10 array where one drive threw an error (seemingly in a
> superblock) and since I have not been able to get the array readable.
> It was suggested to me that I remove 2 of the drives leaving the two
> that were striped together.
[trim /]
What happened to the other two drives? If you still have them, please
supply "mdadm -E" report for them.
Also supply "smartctl -i -A -l scterc /dev/sdX" for each of your drives.
> Is there some way to take the 2 drives and convince mdadm that they
> are a raid 0?
Shouldn't be necessary. Whatever parts of your array that can be made
to run as originally is the safest way to proceed. Also, you haven't
provided any information about your original problem that suggests you
received good advice. (Probably not.)
You attempted a number of commands with invalid bracket syntax, so
received file not found errors that you ignored. You also attempted
filesystem diagnostics on md0 while it was inactive -- that's why those
failed.
You also attempted some operations after partial successes. When an
array is partially assembled but not running, before further attempts to
assemble you must stop the array:
mdadm --stop /dev/md0
Before I suggest anything else, I'd like to see the complete reports for
all four drives.
Please don't do anything else. Your report suggests you are trying
things almost at random in a desperate attempt to salvage your data.
Slow down. We can help if you don't ruin things in the meantime.
Phil
next prev parent reply other threads:[~2015-11-01 20:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 11:55 Advice requested o1bigtenor
2015-11-01 20:55 ` Phil Turmel [this message]
[not found] ` <CAPpdf5_PUpR7GhBHUaQfWb8Q+7FZenxXgFqbaN3f3r0r6NQNDA@mail.gmail.com>
2015-11-02 15:41 ` Phil Turmel
[not found] ` <CAPpdf59MFX1oVwLC-bmQBaQp9K_9-+h0v64OGMnV1-k=eCzO0w@mail.gmail.com>
[not found] ` <5637BCE4.8000006@turmel.org>
2015-11-02 23:49 ` o1bigtenor
2015-11-03 0:11 ` Phil Turmel
2015-11-03 0:44 ` o1bigtenor
2015-11-03 0:57 ` Phil Turmel
2015-11-03 1:02 ` o1bigtenor
2015-11-03 1:55 ` Phil Turmel
2015-11-03 4:03 ` o1bigtenor
2015-11-03 4:09 ` Phil Turmel
2015-11-03 4:28 ` o1bigtenor
2015-11-03 4:47 ` Phil Turmel
2015-11-03 12:45 ` o1bigtenor
2015-11-03 13:09 ` Phil Turmel
2015-11-03 13:36 ` o1bigtenor
2015-11-03 15:49 ` Adam Goryachev
2015-11-03 16:08 ` Phil Turmel
[not found] ` <CAPpdf59o0kf1-mgB29AcgH2cpdwBrhazf3NeQUYNa6m9+c6C+A@mail.gmail.com>
2015-11-04 4:05 ` o1bigtenor
2015-11-04 4:31 ` Brad Campbell
2015-11-03 18:02 ` Phil Turmel
2015-11-03 19:06 ` o1bigtenor
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=56367C33.6060703@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=o1bigtenor@gmail.com \
/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.