linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "D. Lin" <dlbulk-mllr@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: help: re-add needed after each reboot
Date: Tue, 8 May 2012 06:49:14 +1000	[thread overview]
Message-ID: <20120508064914.18c39f80@notabene.brown> (raw)
In-Reply-To: <5d1b39dd26f138ed494e779218d21346.squirrel@anguish.kchang.net>

[-- Attachment #1: Type: text/plain, Size: 3844 bytes --]

On Mon, 7 May 2012 09:29:03 -0700 "D. Lin" <dlbulk-mllr@yahoo.com> wrote:

> Hi,
> 
> I am running 3.2.0 (ubuntu 12.04). My raid5 has 3 disks (sd[cbd]1) and no
> spares. The system boots off a non-raid device and auto discovers and
> mounts the raid device.
> 
> For some reason, sdc1 is not automatically detected and is always missed
> on each boot. I have to re-add it back. What could be causing this?
> 
> This did not happen while I was running 2.6.38.

Would it be equally accurate to say that it didn't happen when you were
running ubunutu 11.10??  My point is that maybe the important change is not
in the kernel.

What do you have in /etc/mdadm.conf ? (or maybe /etc/mdadm/mdadm.conf)
If you stop the array, then

  mdadm -Asvvv

what messages are generated, and what is the result?

NeilBrown


> 
> Thanks,
> 
> Dong Lin
> 
> 
> ; mdadm --misc --detail /dev/md0
> /dev/md0:
>         Version : 1.2
>   Creation Time : Fri Jul 22 22:39:40 2011
>      Raid Level : raid5
>      Array Size : 3907020800 (3726.03 GiB 4000.79 GB)
>   Used Dev Size : 1953510400 (1863.01 GiB 2000.39 GB)
>    Raid Devices : 3
>   Total Devices : 3
>     Persistence : Superblock is persistent
> 
>   Intent Bitmap : Internal
> 
>     Update Time : Mon May  7 09:21:29 2012
>           State : active
>  Active Devices : 3
> Working Devices : 3
>  Failed Devices : 0
>   Spare Devices : 0
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>            Name : disc:0
>            UUID : 4195aaa7:0ebd37ce:d4b9481e:1a68f4a8
>          Events : 230784
> 
>     Number   Major   Minor   RaidDevice State
>        4       8       33        0      active sync   /dev/sdc1
>        2       8       49        1      active sync   /dev/sdd1
>        3       8       17        2      active sync   /dev/sdb1
> 
> 
> ----------------------------
> 
> here is what happened on boot:
> 
> ; dmesg |grep md
> [    1.781917] md: linear personality registered for level -1
> [    1.789184] md: multipath personality registered for level -4
> [    1.797121] md: raid0 personality registered for level 0
> [    1.801681] md: raid1 personality registered for level 1
> [    1.820485] ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfa00
> irq 14
> [    1.820547] ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfa08
> irq 15
> [    1.920271] md: bind<sdb1>
> [    1.962482] md: bind<sdd1>
> [    2.300917] md: raid6 personality registered for level 6
> [    2.300980] md: raid5 personality registered for level 5
> [    2.301036] md: raid4 personality registered for level 4
> [    2.306171] md: raid10 personality registered for level 10
> [    2.329393] md/raid:md0: device sdd1 operational as raid disk 1
> [    2.329450] md/raid:md0: device sdb1 operational as raid disk 2
> [    2.329792] md/raid:md0: allocated 3228kB
> [    2.329921] md/raid:md0: raid level 5 active with 2 out of 3 devices,
> algorithm 2
> [    2.330235] created bitmap (15 pages) for device md0
> [    2.330706] md0: bitmap initialized from disk: read 1/1 pages, set 0 of
> 29809 bits
> [    2.362404] md0: detected capacity change from 0 to 4000789299200
> [    2.367990]  md0: unknown partition table
> 
> 
> 
> =======================================
> partition tables:
> 
> ; fdisk -l | egrep '^/dev/sd[cbd]'
> /dev/sdb1              63  3907024064  1953512001   fd  Linux raid autodetect
> /dev/sdc1              63  3907024064  1953512001   fd  Linux raid autodetect
> /dev/sdd1              63  3907024064  1953512001   fd  Linux raid autodetect
> 
> 
> --
> 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


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-05-07 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 16:29 help: re-add needed after each reboot D. Lin
2012-05-07 20:49 ` NeilBrown [this message]
     [not found] ` <20120508064914.18c39f80.458732@notabene.brown>
2012-05-08  6:41   ` D. Lin
2012-05-08  8:33     ` NeilBrown
     [not found]     ` <20120508183359.6646fe00.182869@notabene.brown>
2012-05-08 16:38       ` D. Lin
2012-05-15 13:27 ` Bill Davidsen

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=20120508064914.18c39f80@notabene.brown \
    --to=neilb@suse.de \
    --cc=dlbulk-mllr@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).