linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Munger <michael@highpoweredhelp.com>
To: linux-raid@vger.kernel.org
Subject: [UU_] Won't go away
Date: Tue, 27 Oct 2015 08:17:26 -0400	[thread overview]
Message-ID: <562F6B56.9040901@highpoweredhelp.com> (raw)

It's my understanding, that an array running with [UU_] is degraded and
there is a disk problem.

I have been trying to create a RAID array using this command:

mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1
/dev/sdc1 /dev/sdd1

However, once it create it, it get this in /proc/mdstat:

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdd1[3] sdc1[1] sdb1[0]
      3906764800 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2]
[UU_]
      [>....................]  recovery =  0.1% (2611780/1953382400)
finish=1737.7min speed=18709K/sec
      bitmap: 0/15 pages [0KB], 65536KB chunk

I have done the following to "fix" the drive:

1. Smartmontools smartctl long and short tests. All passed.
2. Zeroed the first 1GB of the drive (overkill, I know I could just do
the first 512) with dd if=/dev/zero of=/dev/sdb count=250000 bs=4k
3. Re-partitioned the drive.
4. Re-create.

No joy.

Then, I swapped this hard drive out for another drive.

I am still getting [UU_].

Thoughts?
-- 
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help, Inc.
Microsoft Certified Professional
Microsoft Certified Small Business Specialist
Digium Certified Asterisk Professional
michael@highpoweredhelp.com

-- 
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help, Inc.
Microsoft Certified Professional
Microsoft Certified Small Business Specialist
Digium Certified Asterisk Professional
michael@highpoweredhelp.com

             reply	other threads:[~2015-10-27 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 12:17 Michael Munger [this message]
2015-10-27 12:23 ` [UU_] Won't go away Phil Turmel
     [not found]   ` <562F6DEA.3010409@highpoweredhelp.com>
2015-10-27 12:34     ` Phil Turmel
2015-10-27 12:24 ` Robin Hill

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=562F6B56.9040901@highpoweredhelp.com \
    --to=michael@highpoweredhelp.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).