From: "Daniel L. Miller" <dmiller@amfes.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid-10 mount at startup always has problem
Date: Wed, 24 Oct 2007 07:22:58 -0700 [thread overview]
Message-ID: <471F5542.3020504@amfes.com> (raw)
In-Reply-To: <46E4A7C3.1040902@amfes.com>
Daniel L. Miller wrote:
> Richard Scobie wrote:
>> Daniel L. Miller wrote:
>>
>>> And you didn't ask, but my mdadm.conf:
>>> DEVICE partitions
>>> ARRAY /dev/.static/dev/md0 level=raid10 num-devices=4
>>> UUID=9d94b17b:f5fac31a:577c252b:0d4c4b2a
>>
>> Try adding
>>
>> auto=part
>>
>> at the end of you mdadm.conf ARRAY line.
> Thanks - will see what happens on my next reboot.
>
Current mdadm.conf:
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid10 num-devices=4
UUID=9d94b17b:f5fac31a:577c252b:0d4c4b2a auto=part
still have the problem where on boot one drive is not part of the
array. Is there a log file I can check to find out WHY a drive is not
being added? It's been a while since the reboot, but I did find some
entries in dmesg - I'm appending both the md lines and the physical disk
related lines. The bottom shows one disk not being added (this time is
was sda) - and the disk that gets skipped on each boot seems to be
random - there's no consistent failure:
[...]
md: raid10 personality registered for level 10
[...]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
[...]
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0xffffc20001428480 ctl 0xffffc200014284a0
bmdma 0x0000000000011410 irq 23
ata2: SATA max UDMA/133 cmd 0xffffc20001428580 ctl 0xffffc200014285a0
bmdma 0x0000000000011418 irq 23
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3160811AS 3.AA PQ: 0 ANSI: 5
ata1: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw
segs 61
scsi 1:0:0:0: Direct-Access ATA ST3160811AS 3.AA PQ: 0 ANSI: 5
ata2: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw
segs 61
ACPI: PCI Interrupt Link [LSI1] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LSI1] -> GSI 22 (level,
high) -> IRQ 22
sata_nv 0000:00:08.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:08.0 to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0xffffc2000142a480 ctl 0xffffc2000142a4a0
bmdma 0x0000000000011420 irq 22
ata4: SATA max UDMA/133 cmd 0xffffc2000142a580 ctl 0xffffc2000142a5a0
bmdma 0x0000000000011428 irq 22
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
ata4.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA ST3160811AS 3.AA PQ: 0 ANSI: 5
ata3: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw
segs 61
scsi 3:0:0:0: Direct-Access ATA ST3160811AS 3.AA PQ: 0 ANSI: 5
ata4: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw
segs 61
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: unknown partition table
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 2:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdc: unknown partition table
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: [sdd] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 3:0:0:0: [sdd] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdd: unknown partition table
sd 3:0:0:0: [sdd] Attached SCSI disk
[...]
md: md0 stopped.
md: md0 stopped.
md: bind<sdc>
md: bind<sdd>
md: bind<sdb>
md: md0: raid array is not clean -- starting background reconstruction
raid10: raid set md0 active with 3 out of 4 devices
md: couldn't update array info. -22
md: resync of RAID array md0
md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000
KB/sec) for resync.
md: using 128k window, over a total of 312581632 blocks.
Filesystem "md0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md0
Starting XFS recovery on filesystem: md0 (logdev: internal)
Ending XFS recovery on filesystem: md0 (logdev: internal)
--
Daniel
next prev parent reply other threads:[~2007-10-24 14:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 18:14 Raid-10 mount at startup always has problem Daniel L. Miller
[not found] ` <46D49F1A.7030409@tmr.com>
2007-09-10 1:53 ` Daniel L. Miller
2007-09-10 2:04 ` Richard Scobie
[not found] ` <46E4A5F0.9090407@sauce.co.nz>
2007-09-10 2:11 ` Daniel L. Miller
2007-10-24 14:22 ` Daniel L. Miller [this message]
2007-10-24 16:25 ` Doug Ledford
2007-10-24 20:01 ` Bill Davidsen
2007-10-25 5:43 ` Daniel L. Miller
2007-10-25 6:40 ` Doug Ledford
2007-10-26 9:15 ` Luca Berra
2007-10-26 16:53 ` Gabor Gombas
2007-10-27 7:57 ` Luca Berra
2007-10-26 19:26 ` Doug Ledford
2007-10-27 7:50 ` Luca Berra
2007-10-27 15:07 ` Gabor Gombas
2007-10-27 20:47 ` Doug Ledford
2007-10-28 13:37 ` Luca Berra
2007-10-28 17:55 ` Doug Ledford
2007-10-29 0:21 ` Bill Davidsen
2007-10-29 7:41 ` Luca Berra
2007-10-29 13:22 ` Bill Davidsen
2007-10-29 15:21 ` Doug Ledford
2007-10-29 15:54 ` Gabor Gombas
2007-10-29 14:31 ` Doug Ledford
2007-10-29 5:59 ` Daniel L. Miller
2007-10-29 8:18 ` Luca Berra
2007-10-29 15:47 ` Doug Ledford
2007-10-29 21:29 ` Luca Berra
2007-10-29 23:15 ` Doug Ledford
2007-10-30 0:03 ` Daniel L. Miller
2007-11-01 13:56 ` Bill Davidsen
2007-12-17 14:58 ` Daniel L. Miller
2007-10-29 17:08 ` Doug Ledford
2007-10-29 18:56 ` Richard Scobie
2007-10-25 6:12 ` Neil Brown
2007-10-25 6:51 ` Doug Ledford
2007-10-25 13:13 ` Daniel L. Miller
2007-10-25 13:33 ` Daniel L. Miller
2007-10-26 6:12 ` Neil Brown
2007-10-25 14:46 ` Bill Davidsen
2007-10-25 16:13 ` Daniel L. Miller
2007-10-26 5:59 ` 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=471F5542.3020504@amfes.com \
--to=dmiller@amfes.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).