Souci de boot à cause de MDADM

Bien le bonjour,

Je suis sous debian 7 depuis sa sortie, je n’ai jamais eu aucuns soucis jusqu’à la dernière mise à jour du noyau en version 3.*.
Quand je boot dessus, j’ai un joli message d’erreur :

[code]top … Begin: Assembling all MD arrays … mdadm: only give one device per ARRAY line: /dev/md/[ 4.244043] md: bind
1_0 and and
mda[ 4.252744] md: raid1 personality registered for level 1
dm: only give on[ 4.265296] bio: create slab at 1
e device per ARR[ 4.275941] md/raid1:md127: active with 2 out of 2 mirrors
AY line: /dev/md[ 4.289577] md127: detected capacity change from 0 to 4294901760
/1_0 and UUID
m[ 4.306132] md127: unknown partition table
dadm: ARRAY line /dev/md/1_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/1_0 and and
mdadm: only give one device per ARRAY line: /dev/md/1_0 and fe73bc77:ec90b8da:1f51fb89:78ee93fe
mdadm: ARRAY line /dev/md/1_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and with
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and UUID
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and ffeed7c0:f0821900:1f51fb89:78ee93fe
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: WARNING /dev/sda3 and /dev/sda appear to have very similar superblocks.
If they are really different, please --zero the superblock on one
If they are the same or overlap, please remove one from the
DEVICE list in mdadm.conf.
mdadm: /dev/m[ 4.513158] md: md126 stopped.
d/1_0 has been started with 2 dr[ 4.523632] md: bind
ives.
[ 4.532082] md: bind
[ 4.539316] md/raid1:md126: active with 2 out of 2 mirrors
[ 4.550313] md126: detected capacity change from 0 to 993761296384
mdadm: /dev/md/3[ 4.564078] md126: unknown partition table
_0 has been started with 2 drives.
Success: assembled all arrays.
[ 4.816213] device-mapper: uevent: version 1.0.3
done.
[ 4.828306] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
done.
Begin: Waiting for root file system … done.
Gave up waiting [ 35.058240] uhci_hcd: USB Universal Host Controller Interface driver
for root device. Common problem[ 35.073774] usbcore: registered new interface driver usbhid
s:

  • Boot args[ 35.087739] usbhid: USB HID core driver
    (cat /proc/cmdline)
    • Check rootdelay= (did the system wait long enough?)
    • Check root= (did the system wait for the right device?)
  • Missing modules (cat /proc/modules; ls /dev)
    ALERT! /dev/md1 does not exist. Dropping to a shell!

BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.

/bin/sh: can’t access tty; job control turned off
(initramfs)
[/code]

Je suis donc obligé de booter sous la version 2.* du noyau.

Voici le continue du fichier mdadm.conf :

[code]# mdadm.conf

Please refer to mdadm.conf(5) for information about this file.

by default, scan all partitions (/proc/partitions) for MD superblocks.

alternatively, specify devices to scan, using wildcards if desired.

DEVICE partitions

auto-create devices with Debian standard permissions

CREATE owner=root group=disk mode=0660 auto=yes

automatically tag new arrays as belonging to the local system

HOMEHOST

instruct the monitoring daemon where to send mail alerts

MAILADDR root

This file was auto-generated on Mon, 07 Feb 2011 11:46:50 +0000

by mkconf 3.1.4-1+8efb9d1

ARRAY /dev/md1 UUID=fe73bc77:ec90b8da:1f51fb89:78ee93fe
ARRAY /dev/md3 UUID=ffeed7c0:f0821900:1f51fb89:78ee93fe[/code]

Je suis un peu bloqué…
Pouvez-vous m’éclairez quelque peu ?

Merci à vous :slightly_smiling:

À froid, j’ai l’impression d’un problème de version (version 1.2, la syntaxe est ARRAY /dev/md/6 metadata=1.2 UUID=e96196b6:7f40daf1:46f34cbf:9105a9c8
version 0.9, c’est

Or dans ce que je lis, il attend des lignes /dev/md/1_0

Je pense que c’est un souci de ce genre… J’essaye de voir.
[edit: j’ai bien l’impression que c’est ça, peut être en rajoutant metadata=0.9 et en changeant /dev/md1 en /dev/md/1 dans mdadm.conf mais c’est cureiux]

Salutation et merci de m’apporter ton aide :slightly_smiling:

Je viens donc de tester avec tes conseils et j’ai toujours le même message d’erreur :

[code]Begin: Running /scripts/init-premount … done.
Begin: Mounting root file system …[ 4.277103] md: md127 stopped.
. Begin: Running /scripts/local-top … Begin: Assembling all MD arrays … mdadm: only give one[ 4.298939] md: md127 stopped.
device per ARRA[ 4.309506] md: bind
Y line: /dev/md/[ 4.315984] md: bind
1_0 and and
mda[ 4.324844] md: raid1 personality registered for level 1
dm: only give on[ 4.337280] bio: create slab at 1
e device per ARR[ 4.347957] md/raid1:md127: active with 2 out of 2 mirrors
AY line: /dev/md[ 4.361571] md127: detected capacity change from 0 to 4294901760
/1_0 and UUID
m[ 4.378800] md127: unknown partition table
dadm: ARRAY line /dev/md/1_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/1_0 and and
mdadm: only give one device per ARRAY line: /dev/md/1_0 and fe73bc77:ec90b8da:1f51fb89:78ee93fe
mdadm: ARRAY line /dev/md/1_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and with
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and UUID
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: only give one device per ARRAY line: /dev/md/3_0 and and
mdadm: only give one device per ARRAY line: /dev/md/3_0 and ffeed7c0:f0821900:1f51fb89:78ee93fe
mdadm: ARRAY line /dev/md/3_0 has no identity information.
mdadm: WARNING /dev/sda3 and /dev/sda appear to have very similar superblocks.
If they are really different, please --zero the superblock on one
If they are the same or overlap, please remove one from the
DEVICE list in mdadm.conf.
mdadm: /dev/m[ 4.585741] md: md126 stopped.
d/1_0 has been s[ 4.593910] md: bind
tarted with 2 dr[ 4.601254] md: bind
ives.
[ 4.610185] md/raid1:md126: active with 2 out of 2 mirrors
[ 4.621294] md126: detected capacity change from 0 to 993761296384
mdadm: /dev/md/3[ 4.635043] md126: unknown partition table
_0 has been started with 2 drives.
Success: assembled all arrays.
[ 4.880340] device-mapper: uevent: version 1.0.3
done.
[ 4.892411] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
done.
Begin: Waiting for root file system … done.
Gave up waiting for root device.[ 35.102987] uhci_hcd: USB Universal Host Controller Interface driver
Common problems:

  • Boot args[ 35.121202] usbcore: registered new interface driver usbhid
    (cat /proc/cmdl[ 35.135124] usbhid: USB HID core driver
    ine)
    • Check rootdelay= (did the system wait long enough?)
    • Check root= (did the system wait for the right device?)
  • Missing modules (cat /proc/modules; ls /dev)
    ALERT! /dev/md1 does not exist. Dropping to a shell!

BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.

/bin/sh: can’t access tty; job control turned off
(initramfs)
[/code]

Par contre je remarque qu’il solicite /dev/md/1_0 & /dev/md/3_0, je vais donc tester comme ceci :

ARRAY /dev/md/1_0 metadata=0.9 UUID=fe73bc77:ec90b8da:1f51fb89:78ee93fe ARRAY /dev/md/3_0 metadata=0.9 UUID=ffeed7c0:f0821900:1f51fb89:78ee93fe

Je fais un edit suite à cette tentative.

Je ne sais pas si cela à une importance mais regardez :

mdadm[ 4.192880] md: bind<sda1> : only give one [ 4.201651] md: raid1 personality registered for level 1 device per ARRAY[ 4.214198] bio: create slab <bio-1> at 1 line: /dev/md/1[ 4.224862] md/raid1:md127: active with 2 out of 2 mirrors _0 and and mdad[ 4.238504] md127: detected capacity change from 0 to 4294901760 m: only give one device per ARRAY line: /dev/md/1_0 and fe73bc77:ec90b8da:1f51fb[ 4.264199] md127: unknown partition table 89:78ee93fe mdadm: ARRAY line /dev/md/1_0 has no identity information. mdadm: only give one device per ARRAY line: /dev/md/3_0 and and mdadm: only give one device per ARRAY line: /dev/md/3_0 and with mdadm: ARRAY line /dev/md/3_0 has no identity information. mdadm: only give one device per ARRAY line: /dev/md/3_0 and and mdadm: only give one device per ARRAY line: /dev/md/3_0 and UUID mdadm: ARRAY line /dev/md/3_0 has no identity information. mdadm: only give one device per ARRAY line: /dev/md/3_0 and and mdadm: only give one device per ARRAY line: /dev/md/3_0 and ffeed7c0:f0821900:1f51fb89:78ee93fe mdadm: ARRAY line /dev/md/3_0 has no identity information. mdadm: WARNING /dev/sdb3 and /dev/sdb appear to have very similar superblocks. If they are really different, please --zero the superblock on one If they are the same or overlap, please remove one from the DEVICE list in mdadm.conf. mdadm: /dev/md/1_0 has been started with 2 drives. [ 4.462743] md: md126 stopped. [ 4.469936] md: bind<sda3> [ 4.477184] md: bind<sdb3> [ 4.483482] md/raid1:md126: active with 2 out of 2 mirrors [ 4.494457] md126: detected capacity change from 0 to 993761296384 mdadm: /dev/md/3[ 4.508494] md126: unknown partition table _0 has been started with 2 drives. Success: assembled all arrays.

Il semble qu’il prenne tout de même en compte cette ligne : mdadm: /dev/md/1_0 has been started with 2 drives.

J’avoue que pour le moment je sèche un peu.

[size=150]EDIT
[/size]
Je viens de tester ceci, au cas ou ?

ARRAY /dev/md1 UUID=fe73bc77:ec90b8da:1f51fb89:78ee93fe ARRAY /dev/md3 UUID=ffeed7c0:f0821900:1f51fb89:78ee93fe

Toujours le même message d’erreur. On dirait qu’il ne prend même pas en compte les modification que j’apporte au fichier mdadm.conf !

Bon et bien je n’ai toujours pas trouvé de solutions :frowning:

Je pense faire un backup de toutes mes données (sites, bdd, serveurs, etc…) basculer le tout sur une debian fraichement déployé chez moi et attendre les redirections pour refaire la bêbête.

Essaye en rajoutant «debug» dans la ligne de commande de grub pour voir lers messages. C’est tout de même curieux. Sinon essaye en refaisant l’initramfs, c’est lui qui est maitre lors de la construction dfe la racine