[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mdadm messages



On Mon, Nov 4, 2013 at 10:57 AM, François Patte
<francois.patte@mi.parisdescartes.fr> wrote:
> Le 04/11/2013 11:28, Holger Stein a écrit :
>> Am 04.11.2013 09:28, schrieb François Patte:
>>>
>>> I have these messages from mdadm:
>>>
>>> mdadm: cannot open /dev/md/4: No such file or directory
>>>  /dev/md/4 :
>>>  mdadm: cannot open /dev/md/5: No such file or directory
>>>  /dev/md/5 :
>>>
>>> Of course I haven't these directories, I have /dev/md[0-5] instead. Why
>>> does mdadm is searching there directories and how can I get rid of this
>>> message?
>>
>> under /dev/md/* are symlinks to /dev/md*. Do you have a folder /dev/md/?
>> What says mdadm --detail --scan & mdadm --examine --scan
>
> /dev/md/ is empty
>
>  mdadm --detail --scan
> ARRAY /dev/md0 metadata=0.90 UUID=beab96c1:465bb223:6b8acb57:6d51b072
> ARRAY /dev/md1 metadata=0.90 UUID=2e8294de:9b0d8d96:680a5413:2aac5c13
> ARRAY /dev/md2 metadata=0.90 UUID=eb8b5efe:5a8f9369:e940a0f3:83d63ad1
> ARRAY /dev/md3 metadata=0.90 UUID=95c11201:1509169a:860a8b84:c49f865c
> ARRAY /dev/md4 metadata=1.2 name=dipankar:4
> UUID=4a28174a:f38b4938:233f85f7:6ce585a8
> ARRAY /dev/md5 metadata=1.2 name=dipankar:5
> UUID=5240f249:7feb6832:6682805f:97c4abea
>
> mdadm --examine --scan
> ARRAY /dev/md2 UUID=eb8b5efe:5a8f9369:e940a0f3:83d63ad1
> ARRAY /dev/md3 UUID=95c11201:1509169a:860a8b84:c49f865c
> ARRAY /dev/md0 UUID=beab96c1:465bb223:6b8acb57:6d51b072
> ARRAY /dev/md1 UUID=2e8294de:9b0d8d96:680a5413:2aac5c13
> ARRAY /dev/md/4  metadata=1.2 UUID=4a28174a:f38b4938:233f85f7:6ce585a8
> name=dipankar:4
> ARRAY /dev/md/5  metadata=1.2 UUID=5240f249:7feb6832:6682805f:97c4abea
> name=dipankar:5

So the partitions in the v1.2 arrays refer to "/dev/md/X"...

Do you have "/lib/udev/rules.d/64-md-raid-rules" on your system and in
your initramfs?

Do you have any symlinks in "/dev/disk/{by-id,by-uuid}/" to your md devices?


Reply to: