linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ken D'Ambrosio" <ken@jots.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID MIA.  Again.  (Kinda.)
Date: Thu, 4 Mar 2010 17:00:10 -0500 (EST)	[thread overview]
Message-ID: <b305ada429c44b2b62b03c101f7ecf0a.squirrel@webmail.jots.org> (raw)
In-Reply-To: <20100305075016.51e98363@notabene.brown>

On Thu, March 4, 2010 3:50 pm, Neil Brown wrote:
> On Thu, 4 Mar 2010 11:12:29 -0500 (EST)
> "Ken D'Ambrosio" <ken@jots.org> wrote:

[bad things happened to Ken's RAID-5 here]

>
> You missed the bit where you provide concrete information rather than
> vaguaries.

Humble apologies; I'm not well-enough versed with the intricacies of Linux
RAID to know what's appropriate and not.

> I'm guessing that you created the array over whole-devices, and then
> partitioned the array - is that correct? If fdisk shows you an
> unpartitioned array, maybe just the partition table is corrupt.   Seems
> strange.

Actually, no.  These were created using /dev/sd[abcd]2 -- I saved off
space on sd[abcd]1 for swap, /tmp, etc.  Done via the Ubuntu installer, if
that makes a difference.  For the record, all the /dev/sd[abcd]1 non-RAID
partitions look fine.

> To so that I/we don't have to guess, please give exact commands that you
> run and the exact output so we have access to the same information as you.

Well, I rebooted, and was surprised that nothing RAID-esque came up. 
Since my OS is on one of the afore-mentioned non-RAIDed partitions, the
OS, itself, booted, but none of the RAID partitions mounted.  I tried to
mount, and failed.  That's when I checked the RAID device, /dev/md0. 
fdisk showed it lacking any partitions, but the mdadm.conf file hadn't
been touched for a couple of weeks, so I was pretty sure nothing there had
changed.  On the off chance that the SCSI drives had re-ordered
themselves, I went through all 24 permutations of
mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
since I wasn't sure if the drive order was significant.  All of them
"worked," inasmuch as they created /dev/md0, but in all cases it was
partitionless.  I also tried mdadm --detail --scan, to verify that it
matched UUIDs with those in the /etc/mdadm.conf file, and it did (the
array line looks thusly:
ARRAY /dev/md0 level=raid5 num-devices=4
UUID=1e89645a:7e24dcef:9e77d54f:077a6a6f  )


> Too much data is much much better than not enough.

Granted... but, sometimes -- especially when learning -- there can be a
bad signal:noise ratio.  Tends to make me hesitant when I'm a (relative)
newbie to a given topic.  That being said, I *think* I've figured out what
I should be doing, but I also think I did it.  Did I miss something?

Thanks!

-Ken

> NeilBrown
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


  reply	other threads:[~2010-03-04 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 16:12 RAID MIA. Again. (Kinda.) Ken D'Ambrosio
2010-03-04 20:50 ` Neil Brown
2010-03-04 22:00   ` Ken D'Ambrosio [this message]
     [not found]     ` <4877c76c1003041421s42717938he6567434b74ec125@mail.gmail.com>
2010-03-04 22:24       ` Michael Evans
2010-03-04 23:41       ` Ken D'Ambrosio
2010-03-05  1:22         ` Michael Evans
2010-03-05  1:30     ` Neil Brown
2010-03-05 15:24       ` Ken D'Ambrosio
2010-03-05 20:05         ` Michael Evans
2010-03-05 20:38           ` Neil Brown
2010-03-06  3:18             ` Michael Evans
2010-03-05 20:37         ` Neil Brown
2010-03-09 14:43           ` Ken D'Ambrosio
2010-03-09 16:29             ` John Robinson
2010-03-09 19:49             ` 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=b305ada429c44b2b62b03c101f7ecf0a.squirrel@webmail.jots.org \
    --to=ken@jots.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).