From: Phil Turmel <philip@turmel.org>
To: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@audi.de>,
"'linux-raid@vger.kernel.org'" <linux-raid@vger.kernel.org>
Subject: Re: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
Date: Mon, 17 Feb 2014 14:21:52 -0500 [thread overview]
Message-ID: <53026150.2080806@turmel.org> (raw)
In-Reply-To: <A2EC67620EC7424F9EC3DD49243E9060466EC088@AUDIINSX0328.audi.vwg>
On 02/17/2014 02:10 PM, Samer, Michael (I/ET-83, extern) wrote:
>> Good morning Michael,
>
> Hello Phil
>
>> On 02/17/2014 08:33 AM, Samer, Michael (I/ET-83, extern) wrote:
>>> Greetings to all
>>>
>>> As my thread from the 6.2.2014 didn't bring any hint or any reply or way out, I need >advise if my way is approved:
>>
>> I travel a lot, and didn't see your posts. Help from someone usually
>> pops up. Sorry it didn't work that way for you.
>
> I'd have asked more frequently and surely the case is not FAQ.
>
> That's the last --examine I did four weeks ago (before I recovered the part/volume table again:
>
> /dev/sda3:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 52d7d080:5c40de46:bc741f30:65cb5a0d
> Creation Time : Sun Jan 27 23:10:25 2013
> Raid Level : raid5
> Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
> Array Size : 13663619200 (13030.64 GiB 13991.55 GB)
> Raid Devices : 8
> Total Devices : 7
> Preferred Minor : 0
>
> Update Time : Sun Apr 21 14:14:49 2013
> State : active
> Active Devices : 7
> Working Devices : 7
> Failed Devices : 1
> Spare Devices : 0
> Checksum : 91564c42 - correct
> Events : 136
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 3 8 51 3 active sync /dev/sdd3
Ok. Stop here. This report shows /dev/sda3 where the metadata thought
it was /dev/sdd3. So your device names have been changing.
Please redo the --examine operation on all of the /dev/sdX3 partitions
and report again.
Also report an excerpt of "ls -l /dev/disk/by-id/" that shows the device
name vs. serial number for all of the drives involved.
Also report kernel and mdadm versions. The report format is an older style.
Phil
next prev parent reply other threads:[~2014-02-17 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 12:47 QNAP 8 port RAID5 md0 unmountable defective md superblocks Michael Samer
2014-02-06 11:16 ` QNAP 8 port RAID5 md0 recovery of missing MBR and " Samer, Michael (I/ET-83, extern)
2014-02-17 13:33 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-17 13:47 ` Phil Turmel
2014-02-17 19:10 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-17 19:21 ` Phil Turmel [this message]
2014-02-18 12:16 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-18 12:59 ` Phil Turmel
2014-03-13 10:43 ` AW: " Samer, Michael (I/ET-83, extern)
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=53026150.2080806@turmel.org \
--to=philip@turmel.org \
--cc=extern.michael.samer@audi.de \
--cc=linux-raid@vger.kernel.org \
/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).