linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: travis+ml-linux-raid@subspacefield.org
To: Chris Murphy <lists@colorremedies.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: bootsect replicated in p1, RAID enclosure suggestions?
Date: Thu, 25 Aug 2016 21:06:19 -0700	[thread overview]
Message-ID: <20160826040619.GR32250@subspacefield.org> (raw)
In-Reply-To: <20160826035850.GQ32250@subspacefield.org>

On Thu, Aug 25, 2016 at 08:58:50PM -0700, travis@subspacefield.org wrote:
> Yeah, *when I created this disk layout* I might have created a GPT in
> partition 1.
> 
> That was probably a year or more ago.
> 
> That has nothing to do with this crash, which is perhaps the fourth of
> its kind.
> 
> I haven't touched the box in weeks before this happened, when I was
> away on vacation.  Although, it could have lurked for some time,
> and only been uncovered by a crash or kpanic.

I certainly have not repartitioned the disks multiple times.  There's
no need for that.  It leads to these sort of problems.

The kernel does panic from time to time.

To repeat, this box was *completely unattended* for several weeks
before the crash.  No administration at all.  I simply rsync'd things
off it as necessary.  As a non-root user.

I am curious about the fact that /dev/sdd1 and /dev/sde1 were listed
together in this lvm cache, and those are the two disks that normally
get blasted every 6 months or so.  That's an odd coincidence, and my
best lead yet.
-- 
http://www.subspacefield.org/~travis/ | if spammer then john@subspacefield.org
"Computer crime, the glamor crime of the 1970s, will become in the
1980s one of the greatest sources of preventable business loss."
John M. Carroll, "Computer Security", first edition cover flap, 1977

  reply	other threads:[~2016-08-26  4:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  5:09 bootsect replicated in p1, RAID enclosure suggestions? travis+ml-linux-raid
2016-08-24  2:14 ` travis+ml-linux-raid
2016-08-24 17:15 ` Chris Murphy
2016-08-25  6:25   ` travis+ml-linux-raid
2016-08-25 21:06     ` Wols Lists
2016-08-25 22:32     ` Chris Murphy
2016-08-26  2:33       ` Phil Turmel
2016-08-26  2:48         ` Chris Murphy
2016-08-26  3:11           ` travis+ml-linux-raid
2016-08-26  2:50       ` travis
2016-08-26  3:21         ` Chris Murphy
2016-08-26  3:58           ` travis
2016-08-26  4:06             ` travis+ml-linux-raid [this message]
2016-08-26  4:25               ` Chris Murphy
2016-09-02  2:18                 ` travis+ml-linux-raid
2016-09-01 17:22 ` Wols Lists
2016-09-01 23:10   ` Chris Murphy

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=20160826040619.GR32250@subspacefield.org \
    --to=travis+ml-linux-raid@subspacefield.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.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 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).