From: Bill Davidsen <davidsen@tmr.com>
To: tjb@unh.edu
Cc: linux-raid@vger.kernel.org
Subject: Re: Any hope for a 27 disk RAID6+1HS array with four disks reporting "No md superblock detected"?
Date: Thu, 05 Feb 2009 18:57:14 -0500 [thread overview]
Message-ID: <498B7CDA.2090209@tmr.com> (raw)
In-Reply-To: <1233860358.1780.21.camel@localhost.localdomain>
Thomas J. Baker wrote:
> On Thu, 2009-02-05 at 13:49 -0500, Bill Davidsen wrote:
>
>> Thomas J. Baker wrote:
>>
>>> The array was made probably two years ago and had been working fine
>>> until recently. In reading the documentation for mdadm, it did seem like
>>> it should have required me to use the higher version but it never
>>> complained when I made it and worked fine.
>>>
>>>
>> What have you changed lately? Are the drives all on a single controller?
>> Are you using PARTITIONS in mdadm.conf and letting mdadm find things for
>> itself?
>>
>>
>
> The array is made up of two Dell PowerVault 220s in split bus
> configuration with two Adaptec 39160 Dual Channel SCSI controllers. Each
> half of each PowerVault (7 disks) is connected to one of the channels on
> the Adaptecs. Four channels in all.
>
> As far as changing things, what do you mean? The cause of the failure is
> likely heat as we've had some AC issues recently.
>
>
Well that's change, but if you can read the drives at all it doesn't
sound like the typical "fall down dead" heat issues, I would expect tons
of hardware errors at a lower level from the device controller. Did you
check the partition tables with fdisk or similar? Are the drives all in
the same physical box? IBM split their boxes, running four drives off
one power and four (or three+CD) off the other. They are likely to have
something in common, if you can find it you might fix it.
> I didn't use mdadm.conf at all. All disks are partitioned with one
> 'Linux raid autodetect' partition. mdadm had always found the array
> automatically at boot.
>
No kernel update or utilities update lately?
Given the choice of identify in hopes of a fixable problem or reinstall,
config, recover from backup, I'm trying to see if you can do the former
in preference to the latter.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2009-02-05 23:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 19:27 Any hope for a 27 disk RAID6+1HS array with four disks reporting "No md superblock detected"? Thomas J. Baker
2009-02-04 20:50 ` Joe Landman
2009-02-04 21:03 ` Thomas J. Baker
2009-02-04 21:17 ` Thomas J. Baker
2009-02-05 18:49 ` Bill Davidsen
2009-02-05 18:59 ` Thomas J. Baker
2009-02-05 23:57 ` Bill Davidsen [this message]
2009-02-06 0:08 ` Thomas Baker
2009-02-06 5:14 ` Neil Brown
2009-02-06 20:32 ` Thomas J. Baker
2009-02-06 21:01 ` NeilBrown
2009-02-06 21:47 ` Thomas J. Baker
2009-02-07 2:09 ` NeilBrown
2009-02-09 14:48 ` Thomas J. Baker
2009-02-10 16:58 ` Nagilum
2009-02-07 4:05 ` Mr. James W. Laferriere
2009-02-08 22:02 ` Thomas Baker
2009-02-09 11:47 ` Max Waterman
2009-02-10 8:55 ` Luca Berra
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=498B7CDA.2090209@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=tjb@unh.edu \
/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).