Le 4846 Septembre 1993, martin f. krafft a tapoté: > It seems like a non-critical problem as it's just an error message, > but the actual operation is not affected. Thus, it will be unlikely > to have this fixed in etch, but I am not ruling it out either.
Well, init the init ramdisk I get a wrong conf/md.conf: MD_HOMEHOST='ancalagon' MD_DEVPAIRS='/dev/sdb2: /dev/sdb4: /dev/sdb5: /dev/md0:raid1 /dev/md1:raid1 /dev/md2:raid1' MD_LEVELS='raid1 raid1 raid1' MD_DEVS=all MD_MODULES='raid1' With your patch MD_DEVPAIRS is different: MD_HOMEHOST='ancalagon' MD_DEVPAIRS='/dev/md0:raid1 /dev/md1:raid1 /dev/md2:raid1' MD_LEVELS='raid1 raid1 raid1' MD_DEVS=all MD_MODULES='raid1' So I think it's not a non-critical problem, when we specify the DEVICE in /etc/mdadm/mdadm.conf, which is "DEVICE partitions" by default. > Could you try if the following patch against the hook script fixes > the problem? This patch fix the problem. Thanks a lot. -- Daniel 'NebuchadnezzaR' Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x2A408F69 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
