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