From: Neil Brown <neilb@suse.de>
To: Jon@eHardcastle.com
Cc: jd_hardcastle@yahoo.com, linux-raid@vger.kernel.org
Subject: Re: sdc1 does not have a valid v0.90 superblock, not importing!
Date: Wed, 11 Aug 2010 21:06:03 +1000 [thread overview]
Message-ID: <20100811210603.065284c8@notabene> (raw)
In-Reply-To: <835034.72836.qm@web51302.mail.re2.yahoo.com>
On Wed, 11 Aug 2010 02:55:44 -0700 (PDT)
Jon Hardcastle <jd_hardcastle@yahoo.com> wrote:
> (my first attempt appears to have been bounced as the spam checker thought it had HTML in it?!)
odd... came through ok for me the first time.
>
> Help!
>
> Long story short - I was watching a movie off my RAID6 array. Got a smart error warning
> Aug 10 22:00:07 mangalore kernel: raid5: cannot start dirty degraded array for md4
This is the current problem. The array is dirty and degraded so there could
theoretically be undetectable corruption. Chance is quite low but it is
there so md won't start with out you acknowledging the risk by giving the
--force flag to mdadm --assemble.
Only do that if you are confident that your hardware is working correctly.
> It appears sdc has an invalid superblock?
>
> This is the 'examine' from sdc1 (note the checksum)
>
> /dev/sdc1:
.....
> Checksum : b335b4e3 - expected b735b4e3
Single bit error. That isn't good as it means some bit of memory or some bit
on some bus somewhere cannot be trusted.
It could be a transient thing and will never happen again. Or maybe not.
Given the smart errors and the fact that you have had problems with the drive
before it seem very likely that the problem is in that drive. I suggest
unplugging it and leaving it unplugged. Some memory buffer in the drive is
probably marginal. I don't think they use ECC memory.
>
> Anyways... I am ASSUMING mdadm has not assembled the array to be on the safe side? i have not done anything.. no force... no assume clean.. I wanted to be sure?
You assume correctly.
>
> Should i remove sdc1 from the array? It should then assemble? I have 2 spare drives that I am getting around to using to replace this drive and the other 500GB.. so should I remove sdc1... and try and re-add or just put the new drive in?
>
> atm I have 'stop'ped the array and got badblocks running....
>
Remove sdc and assemble the array with --force, and get a new device to
replace /dev/sdc as soon as possible.
NeilBrown
next prev parent reply other threads:[~2010-08-11 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 9:55 Sorry if Spamming! - sdc1 does not have a valid v0.90 superblock, not importing! Jon Hardcastle
2010-08-11 11:06 ` Neil Brown [this message]
2010-08-11 11:19 ` Jon Hardcastle
2010-08-11 11:34 ` Neil Brown
2010-08-11 12:29 ` Jon Hardcastle
2010-08-11 15:30 ` Jon Hardcastle
-- strict thread matches above, loose matches on Subject: below --
2010-08-10 21:35 Fw: " Jon Hardcastle
2010-08-11 22:01 ` Stefan /*St0fF*/ Hübner
2010-08-11 22:56 ` Neil Brown
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=20100811210603.065284c8@notabene \
--to=neilb@suse.de \
--cc=Jon@eHardcastle.com \
--cc=jd_hardcastle@yahoo.com \
--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).