Public bug reported:
Binary package hint: mdadm
at 1/10 time, mdadm says :
mdadm : No devices listed in conf file were found.
i just have to CTLR+ALT+DEL or push the reset button and it's OK, the
approximatively next 10 boots work finely !?!
i am on Feisty up to date, kernel based on x86_64.
the content of mdadm.conf :
$ cat /etc/mdadm/mdadm.conf
# md0>/boot ; md1>LVM ; md2>swap
DEVICE /dev/sda*
DEVICE /dev/sdb*
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=46c0fc49:6a912381:61f75e68:2a1e43ae
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=6b41f1de:db3d4408:b1f2e1cb:9f30c639
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=3aea7d28:cc86726b:d1872f7b:5ba40b17
MAILADDR root
i found UUIDs with this command :
$ sudo /usr/share/mdadm/mkconf
# 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 <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=46c0fc49:6a912381:61f75e68:2a1e43ae
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=6b41f1de:db3d4408:b1f2e1cb:9f30c639
ARRAY /dev/md3 level=raid1 num-devices=2
UUID=3aea7d28:cc86726b:d1872f7b:5ba40b17
My PC is not a server, so it's not very important, but i don't understand why
it doesn't work sometimes...
Thanks for your help, and VIVA UBUNTU ;-)
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
mdadm : boot failed sometimes, no devices found
https://bugs.launchpad.net/bugs/120504
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
