* mdadm --assemble --scan hassles....
@ 2003-10-08 11:17 Hendrik Visage
2003-10-16 3:45 ` Neil Brown
0 siblings, 1 reply; 11+ messages in thread
From: Hendrik Visage @ 2003-10-08 11:17 UTC (permalink / raw)
To: linux-raid
Right, now if md would do auto detecting on mds then my
problem would have disappeared, but alas....
Anycase, I'm trying to make use of mdadm (I've tried different options etc.
inside mdadm.conf from what I could see on the mailing list), but I'm still
stuck with the following issue:
(right after boot):
root@hvstress ~ # mdadm --assemble --scan
mdadm: no devices found for /dev/md/1
root@hvstress ~ # mdadm --examine --scan
ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
devices=/dev/md/0,/dev/md/0
root@hvstress ~ # mdadm --examine --scan --config=partitions
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
root@hvstress ~ # mdadm --assemble --scan
mdadm: no devices found for /dev/md/1
root@hvstress ~ # cat /etc/mdadm.conf
DEVICE /dev/md/* /dev/sd*
DEVICE /dev/sd[ab]
DEVICE /dev/md0
DEVICE /dev/md/0
ARRAY /dev/md/0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
ARRAY /dev/md/1 level=linear num-devices=2 UUID=c2a91233:5ffd5398:eac27773:e12945dd
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-08 11:17 mdadm --assemble --scan hassles Hendrik Visage
@ 2003-10-16 3:45 ` Neil Brown
2003-10-25 21:24 ` Hendrik Visage
0 siblings, 1 reply; 11+ messages in thread
From: Neil Brown @ 2003-10-16 3:45 UTC (permalink / raw)
To: Hendrik Visage; +Cc: linux-raid
On Wednesday October 8, hvisage@envisage.co.za wrote:
> Right, now if md would do auto detecting on mds then my
> problem would have disappeared, but alas....
>
> Anycase, I'm trying to make use of mdadm (I've tried different options etc.
> inside mdadm.conf from what I could see on the mailing list), but I'm still
> stuck with the following issue:
> (right after boot):
>
> root@hvstress ~ # mdadm --assemble --scan
> mdadm: no devices found for /dev/md/1
That would be because mdadm.conf describes /dev/md/1 as:
UUID=c2a91233:5ffd5398:eac27773:e12945dd
but mdadm --examine doesn't show any arrays with that uuid.
NeilBrown
> root@hvstress ~ # mdadm --examine --scan
> ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
> devices=/dev/md/0,/dev/md/0
> root@hvstress ~ # mdadm --examine --scan --config=partitions
> ARRAY /dev/md0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
> devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
> ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
> devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
>
> root@hvstress ~ # mdadm --assemble --scan
> mdadm: no devices found for /dev/md/1
> root@hvstress ~ # cat /etc/mdadm.conf
> DEVICE /dev/md/* /dev/sd*
> DEVICE /dev/sd[ab]
> DEVICE /dev/md0
> DEVICE /dev/md/0
>
> ARRAY /dev/md/0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
> devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
> ARRAY /dev/md/1 level=linear num-devices=2 UUID=c2a91233:5ffd5398:eac27773:e12945dd
>
>
> -
> 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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-16 3:45 ` Neil Brown
@ 2003-10-25 21:24 ` Hendrik Visage
2003-10-27 22:06 ` Neil Brown
0 siblings, 1 reply; 11+ messages in thread
From: Hendrik Visage @ 2003-10-25 21:24 UTC (permalink / raw)
To: Neil Brown; +Cc: Hendrik Visage, linux-raid
On Thu, Oct 16, 2003 at 01:45:04PM +1000, Neil Brown wrote:
> On Wednesday October 8, hvisage@envisage.co.za wrote:
> > Right, now if md would do auto detecting on mds then my
> > problem would have disappeared, but alas....
> >
> > Anycase, I'm trying to make use of mdadm (I've tried different options etc.
> > inside mdadm.conf from what I could see on the mailing list), but I'm still
> > stuck with the following issue:
> > (right after boot):
> >
> > root@hvstress ~ # mdadm --assemble --scan
> > mdadm: no devices found for /dev/md/1
>
> That would be because mdadm.conf describes /dev/md/1 as:
> UUID=c2a91233:5ffd5398:eac27773:e12945dd
> but mdadm --examine doesn't show any arrays with that uuid.
>
> NeilBrown
Then how do I fix it??
>
> > root@hvstress ~ # mdadm --examine --scan
> > ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
> > devices=/dev/md/0,/dev/md/0
> > root@hvstress ~ # mdadm --examine --scan --config=partitions
> > ARRAY /dev/md0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
> > devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
> > ARRAY /dev/md1 level=linear num-devices=2 UUID=8eb3a6c0:02e58fd9:a662938a:56f87147
> > devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
> >
> > root@hvstress ~ # mdadm --assemble --scan
> > mdadm: no devices found for /dev/md/1
> > root@hvstress ~ # cat /etc/mdadm.conf
> > DEVICE /dev/md/* /dev/sd*
> > DEVICE /dev/sd[ab]
> > DEVICE /dev/md0
> > DEVICE /dev/md/0
> >
> > ARRAY /dev/md/0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e2
> > devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/lun0/part1
> > ARRAY /dev/md/1 level=linear num-devices=2 UUID=c2a91233:5ffd5398:eac27773:e12945dd
> >
> >
> > -
> > 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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-25 21:24 ` Hendrik Visage
@ 2003-10-27 22:06 ` Neil Brown
2003-10-28 6:24 ` Hendrik Visage
0 siblings, 1 reply; 11+ messages in thread
From: Neil Brown @ 2003-10-27 22:06 UTC (permalink / raw)
To: Hendrik Visage; +Cc: linux-raid
On Saturday October 25, hvisage@envisage.co.za wrote:
> > That would be because mdadm.conf describes /dev/md/1 as:
> > UUID=c2a91233:5ffd5398:eac27773:e12945dd
> > but mdadm --examine doesn't show any arrays with that uuid.
> >
> > NeilBrown
>
> Then how do I fix it??
>
Edit /etc/mdadm.conf
NeilBrown
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-27 22:06 ` Neil Brown
@ 2003-10-28 6:24 ` Hendrik Visage
2003-10-28 11:30 ` rob
2003-10-30 1:18 ` Neil Brown
0 siblings, 2 replies; 11+ messages in thread
From: Hendrik Visage @ 2003-10-28 6:24 UTC (permalink / raw)
To: Neil Brown; +Cc: Hendrik Visage, linux-raid
On Tue, Oct 28, 2003 at 09:06:55AM +1100, Neil Brown wrote:
> On Saturday October 25, hvisage@envisage.co.za wrote:
> > > That would be because mdadm.conf describes /dev/md/1 as:
> > > UUID=c2a91233:5ffd5398:eac27773:e12945dd
> > > but mdadm --examine doesn't show any arrays with that uuid.
> > >
> > > NeilBrown
> >
> > Then how do I fix it??
> >
>
> Edit /etc/mdadm.conf
I've tried without any succes as yet :(
so what would the correct mdadm.conf look like in my case?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-28 6:24 ` Hendrik Visage
@ 2003-10-28 11:30 ` rob
2003-10-29 0:04 ` Neil Brown
2003-10-30 1:18 ` Neil Brown
1 sibling, 1 reply; 11+ messages in thread
From: rob @ 2003-10-28 11:30 UTC (permalink / raw)
To: Hendrik Visage; +Cc: Neil Brown, linux-raid
AFAIK you don't need DEVICE and ARRAY entries in mdadm.conf
I only use MAILADDR PROGRAM entries to monitor the array.
Hendrik Visage wrote:
>On Tue, Oct 28, 2003 at 09:06:55AM +1100, Neil Brown wrote:
>
>
>>On Saturday October 25, hvisage@envisage.co.za wrote:
>>
>>
>>>>That would be because mdadm.conf describes /dev/md/1 as:
>>>> UUID=c2a91233:5ffd5398:eac27773:e12945dd
>>>>but mdadm --examine doesn't show any arrays with that uuid.
>>>>
>>>>NeilBrown
>>>>
>>>>
>>>Then how do I fix it??
>>>
>>>
>>>
>>Edit /etc/mdadm.conf
>>
>>
>
>I've tried without any succes as yet :(
>
>so what would the correct mdadm.conf look like in my case?
>
>
>-
>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
>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-28 11:30 ` rob
@ 2003-10-29 0:04 ` Neil Brown
2003-10-29 5:47 ` Hendrik Visage
0 siblings, 1 reply; 11+ messages in thread
From: Neil Brown @ 2003-10-29 0:04 UTC (permalink / raw)
To: rob; +Cc: Hendrik Visage, linux-raid
On Tuesday October 28, rob@fantinibakery.com wrote:
> AFAIK you don't need DEVICE and ARRAY entries in mdadm.conf
>
> I only use MAILADDR PROGRAM entries to monitor the array.
>
It depends on what you want mdadm to do for you.
If you want it to assemble your arrays, then DEVICE and ARRAY help
alot.
If you only want it to monitor your arrays, then MAILADDR and PROGRAM
are all you need.
NeilBrown
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-29 0:04 ` Neil Brown
@ 2003-10-29 5:47 ` Hendrik Visage
0 siblings, 0 replies; 11+ messages in thread
From: Hendrik Visage @ 2003-10-29 5:47 UTC (permalink / raw)
To: Neil Brown; +Cc: rob, Hendrik Visage, linux-raid
On Wed, Oct 29, 2003 at 11:04:13AM +1100, Neil Brown wrote:
> It depends on what you want mdadm to do for you.
>
> If you want it to assemble your arrays, then DEVICE and ARRAY help
> alot.
> If you only want it to monitor your arrays, then MAILADDR and PROGRAM
> are all you need.
True,
But it still doesn't solve my original problem, being that mdadm
didn't picked up the md that should go into the next md :(
HEndrik
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-28 6:24 ` Hendrik Visage
2003-10-28 11:30 ` rob
@ 2003-10-30 1:18 ` Neil Brown
2003-10-30 5:56 ` Hendrik Visage
1 sibling, 1 reply; 11+ messages in thread
From: Neil Brown @ 2003-10-30 1:18 UTC (permalink / raw)
To: Hendrik Visage; +Cc: linux-raid
On Tuesday October 28, hvisage@envisage.co.za wrote:
> On Tue, Oct 28, 2003 at 09:06:55AM +1100, Neil Brown wrote:
> > On Saturday October 25, hvisage@envisage.co.za wrote:
> > > > That would be because mdadm.conf describes /dev/md/1 as:
> > > > UUID=c2a91233:5ffd5398:eac27773:e12945dd
> > > > but mdadm --examine doesn't show any arrays with that uuid.
> > > >
> > > > NeilBrown
> > >
> > > Then how do I fix it??
> > >
> >
> > Edit /etc/mdadm.conf
>
> I've tried without any succes as yet :(
>
> so what would the correct mdadm.conf look like in my case?
>
Show me:
- your current mdadm.conf
- the output of mdadm -Es -c partitions
- the output of mdadm -Ds
- the output of mdadm -Asv
And I'll try to tell you.
NeilBrown
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-30 1:18 ` Neil Brown
@ 2003-10-30 5:56 ` Hendrik Visage
2003-10-31 0:24 ` Neil Brown
0 siblings, 1 reply; 11+ messages in thread
From: Hendrik Visage @ 2003-10-30 5:56 UTC (permalink / raw)
To: Neil Brown; +Cc: Hendrik Visage, linux-raid
On Thu, Oct 30, 2003 at 12:18:44PM +1100, Neil Brown wrote:
>
> Show me:
> - your current mdadm.conf
> - the output of mdadm -Es -c partitions
> - the output of mdadm -Ds
> - the output of mdadm -Asv
>
> And I'll try to tell you.
root@hvstress ~ # mdadm -Es -c partitions
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e
2
devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/
lun0/part1
ARRAY /dev/md1 level=linear num-devices=2 UUID=4478ef04:f7b90666:6a122182:c6b44c
f4
devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
root@hvstress ~ # mdadm -Ds
ARRAY /dev/md1 level=linear num-devices=2 UUID=4478ef04:f7b90666:6a122182:c6b44c
f4
devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
ARRAY /dev/md0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96e
2
devices=/dev/scsi/host0/bus0/target2/lun0/part1,/dev/scsi/host0/bus0/target1/
lun0/part1
root@hvstress ~ # mdadm -Asv
root@hvstress ~ # cat /etc/mdadm.conf
DEVICE /dev/md/* /dev/sd[a-z] partitions /dev/md*
ARRAY /dev/md/0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96
e2
devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/
lun0/part1
ARRAY /dev/md/1 level=linear num-devices=2 UUID=c2a91233:5ffd5398:eac27773:e1294
5dd
devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: mdadm --assemble --scan hassles....
2003-10-30 5:56 ` Hendrik Visage
@ 2003-10-31 0:24 ` Neil Brown
0 siblings, 0 replies; 11+ messages in thread
From: Neil Brown @ 2003-10-31 0:24 UTC (permalink / raw)
To: Hendrik Visage; +Cc: linux-raid
On Thursday October 30, hvisage@envisage.co.za wrote:
> On Thu, Oct 30, 2003 at 12:18:44PM +1100, Neil Brown wrote:
> >
> > Show me:
> > - your current mdadm.conf
> > - the output of mdadm -Es -c partitions
> > - the output of mdadm -Ds
> > - the output of mdadm -Asv
> >
> > And I'll try to tell you.
>
> root@hvstress ~ # mdadm -Es -c partitions
..etc...
Thanks.
So you have to raid arrays:
md0 is raid0 from 2 scsi partitions and has
UUID=832ab839:9920da12:97991965:f9af96e2
md1 is linear from another scsi partitions and md0, and has
UUID=4478ef04:f7b90666:6a122182:c6b44cf4
So you want mdadm to scan all SCSI partitions and md0, and
to assemble md0 first, then md1. Identifying partitions
by UUID is easiest so:
DEVICE /dev/sd* /dev/md0
ARRAY /dev/md0 UUID=832ab839:9920da12:97991965:f9af96e2
ARRAY /dev/md1 UUID=4478ef04:f7b90666:6a122182:c6b44cf4
should do it. Having "level=xxx" and "num-devices=2" doesn't hurt,
but isn't necessary.
> root@hvstress ~ # cat /etc/mdadm.conf
> DEVICE /dev/md/* /dev/sd[a-z] partitions /dev/md*
>
> ARRAY /dev/md/0 level=raid0 num-devices=2 UUID=832ab839:9920da12:97991965:f9af96
> e2
> devices=/dev/scsi/host0/bus0/target1/lun0/part1,/dev/scsi/host0/bus0/target2/
> lun0/part1
> ARRAY /dev/md/1 level=linear num-devices=2 UUID=c2a91233:5ffd5398:eac27773:e1294
> 5dd
> devices=/dev/md/0,/dev/scsi/host0/bus0/target1/lun0/part2
I suspect the reason that this didn't work was the devices= lines.
The "/dev/scsi/..." doesn't match (as a string) any of the devices
listed in the DEVICE line. It is fairly rare that you would need to
want "devices=" entries in mdadm.conf
NeilBrown
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2003-10-31 0:24 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-10-08 11:17 mdadm --assemble --scan hassles Hendrik Visage
2003-10-16 3:45 ` Neil Brown
2003-10-25 21:24 ` Hendrik Visage
2003-10-27 22:06 ` Neil Brown
2003-10-28 6:24 ` Hendrik Visage
2003-10-28 11:30 ` rob
2003-10-29 0:04 ` Neil Brown
2003-10-29 5:47 ` Hendrik Visage
2003-10-30 1:18 ` Neil Brown
2003-10-30 5:56 ` Hendrik Visage
2003-10-31 0:24 ` Neil Brown
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).