From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: sunruh@prismnet.com
Cc: linux-raid@vger.kernel.org
Subject: Re: please help - raid 1 degraded
Date: Thu, 12 Feb 2015 12:10:41 +1100 [thread overview]
Message-ID: <54DBFD91.7080507@websitemanagers.com.au> (raw)
In-Reply-To: <20150212010200.GA51009@eris.prismnet.com>
On 12/02/15 12:02, sunruh@prismnet.com wrote:
> ok, so now the really important questions: once done, what files/stats
> do i need to save off for the next time it craters?
I think the usual information requested is the following:
fdisk -lu /dev/sd?
mdadm --manage --query /dev/sd?
mdadm --manage --detail /dev/md*
mdadm --manage --examine /dev/sd?
cat /proc/mdstat
ls -l /dev/disk/by-id/
If you can keep a copy of all those things, then you will be much
further ahead than many people. Of course, RAID1 is just so much
easier/simpler than RAID5/RAID6, so usually you won't need any of that.
RAID1 is simple mirror, so if you have two disks, one with data, one
without, then you just need to decide which disk has the data, and start
with that.
It is even possible to start two MD arrays, one from each disk, and then
compare the contents to decide which one you want to keep.
Or, you can simply mount the device directly (skipping any MD data at
the beginning if needed).
Like I said, RAID1 is by far the simplest type of RAID if you want
redundancy and can fit your dataset onto a single device.
Glad you had a successful recovery :)
Regards,
Adam
--
Adam Goryachev Website Managers www.websitemanagers.com.au
next prev parent reply other threads:[~2015-02-12 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 18:04 please help - raid 1 degraded sunruh
2015-02-11 22:12 ` Adam Goryachev
2015-02-12 0:09 ` sunruh
2015-02-12 0:36 ` Adam Goryachev
2015-02-12 1:02 ` sunruh
2015-02-12 1:10 ` Adam Goryachev [this message]
2015-02-12 3:12 ` Eyal Lebedinsky
2015-02-12 10:11 ` Roaming
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=54DBFD91.7080507@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=sunruh@prismnet.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.