All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Krol <admin@domeny.pl>
To: linux-raid@vger.kernel.org
Subject: Deleting mdadm RAID arrays
Date: Tue, 5 Feb 2008 11:42:19 +0100	[thread overview]
Message-ID: <200802051142.19625.admin@domeny.pl> (raw)

Hello everyone,

I have had a problem with RAID array (udev messed up disk names, I've had RAID on
disks only, without raid partitions) on Debian Etch server with 6 disks and so I decided 
to rearrange this. 

Deleted the disks from (2 RAID-5) arrays, deleted the md* devices from /dev,
created /dev/sd[a-f]1 Linux raid auto-detect partitions and rebooted the host.

Now the mdadm startup script is writing in loop a message like "mdadm: warning: /dev/sda1 and 
/dev/sdb1 have similar superblocks. If they are not identical, --zero the superblock ... "

The host can't boot up now because of this.

If I boot the server with some disks, I can't even zero that superblock:

% mdadm --zero-superblock /dev/sdb1
mdadm: Couldn't open /dev/sdb1 for write - not zeroing

It's the same even after:

% mdadm --manage /dev/md2 --fail /dev/sdb1
mdadm: set /dev/sdb1 faulty in /dev/md2


Now, I have NEVER created /dev/md2 array, yet it show up automatically!

% cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid1]
md2 : active(auto-read-only) raid1 sdb1[1]
      390708736 blocks [3/1] [_U_]

md1 : inactive sda1[2]
      390708736 blocks

unused devices: <none>


Questions:

1. Where this info on array resides?! I have deleted /etc/mdadm/mdadm.conf 
and /dev/md devices and yet it comes seemingly out of nowhere.

2. How can I delete that damn array so it doesn't hang my server up in a loop?


-- 
Marcin Krol


             reply	other threads:[~2008-02-05 10:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 10:42 Marcin Krol [this message]
2008-02-05 11:43 ` Deleting mdadm RAID arrays Moshe Yudkowsky
2008-02-06  9:35   ` Marcin Krol
2008-02-05 12:27 ` Janek Kozicki
2008-02-05 13:52   ` Michael Tokarev
2008-02-05 14:33     ` Moshe Yudkowsky
2008-02-05 15:16       ` Michael Tokarev
2008-02-05 14:47     ` Auto generation of mdadm.conf (was: Deleting mdadm RAID arrays) Janek Kozicki
2008-02-05 15:34       ` Auto generation of mdadm.conf Michael Tokarev
2008-02-05 18:39         ` Janek Kozicki
2008-02-05 20:12 ` Deleting mdadm RAID arrays Neil Brown
2008-02-06  9:55   ` Marcin Krol
2008-02-06 10:11     ` Peter Rabbitson
2008-02-06 10:32       ` Marcin Krol
2008-02-06 10:43     ` Neil Brown
2008-02-06 12:03       ` Marcin Krol
2008-02-07  2:36         ` Neil Brown
2008-02-07  9:56           ` Marcin Krol
2008-02-07 21:35             ` Bill Davidsen
2008-02-08  9:35               ` Marcin Krol
2008-02-08 12:44                 ` Bill Davidsen
2008-02-08 12:52                   ` Marcin Krol
2008-02-06 19:03   ` Bill Davidsen
2008-02-06 11:22 ` David Greaves
2008-02-06 11:56   ` Marcin Krol

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=200802051142.19625.admin@domeny.pl \
    --to=admin@domeny.pl \
    --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 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.