Your message dated Fri, 17 Nov 2006 09:53:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399015: mdadm: Unable to create new raid array
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mdadm
Version: 2.5.6-5
Severity: important
I'm trying to create a raid array, and mdadm is unable to find /dev/md0. I
originally installed my system on a single drive. I have now added a second
drive that I intend to mirror the first drive with. The first step of course
requires me to construct a raid array on the second drive, but mdadm isn't
able to.
I run:
mdadm --create /dev/md0 -l 1 -n 2 missing /dev/hdd1
to create a raid 1 array with 2 disks, 1 missing. The result I get is:
mdadm: error opening /dev/md0: No such file or directory
Perhaps this is a bug in udev instead? I have udev version 0.100-2.3
installed, the latest at this time. 0.100-2.2 didn't work any better hence
upgrading to the version in unstable.
-- Package-specific info:
--- mount output
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,nodev)
--- mdadm.conf
DEVICE partitions
MAILADDR jlquinn
--- /proc/mdstat:
Personalities : [linear] [multipath] [raid0] [raid1] [raid5] [raid4] [raid6]
[raid10]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
3 0 244198584 hda
3 1 241770186 hda1
3 2 2425815 hda2
22 64 244198584 hdd
22 65 241770217 hdd1
22 66 2425815 hdd2
--- initrd.img-2.6.17-1-k7:
21624 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.17-1-k7/kernel/drivers/md/md-mod.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/linear.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/multipath.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/raid0.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/raid1.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/xor.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/raid5.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/raid6.ko
lib/modules/2.6.17-1-k7/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm
--- /proc/modules:
dm_snapshot 15968 0 - Live 0xf2c49000
dm_mirror 19216 0 - Live 0xf2c32000
dm_mod 50520 2 dm_snapshot,dm_mirror, Live 0xf2c3b000
raid10 21120 0 - Live 0xf08e1000
raid6 102928 0 - Live 0xf090f000
raid5 30272 0 - Live 0xf08eb000
xor 14472 2 raid6,raid5, Live 0xf08c8000
raid1 20992 0 - Live 0xf08c1000
raid0 8000 0 - Live 0xf0802000
multipath 8448 0 - Live 0xf084b000
linear 5760 0 - Live 0xf0820000
md_mod 69524 7 raid10,raid6,raid5,raid1,raid0,multipath,linear, Live 0xf08cf000
--- volume detail:
--- /proc/cmdline
root=/dev/hda1 ro
--- grub:
kernel /boot/vmlinuz-2.6.17-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.17-1-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.16-2-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.16-2-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.16-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.16-1-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.15-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.15-1-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.14-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.14-1-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.12-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.12-1-k7 root=/dev/hda1 ro single
kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/hda1 ro
kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/hda1 ro single
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries
ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip
ii makedev 2.3.1-83 creates device files in /dev
Versions of packages mdadm recommends:
ii exim [mail-transport-agent] 3.36-18.1 An obsolete MTA (Mail Transport Ag
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
-- debconf information:
* mdadm/autostart: false
* mdadm/initrdstart: all
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/initrdstart_msg_errblock:
* mdadm/warning:
* mdadm/start_daemon: false
mdadm/mail_to: jlquinn
mdadm/initrdstart_msg_errmd:
mdadm/initrdstart_msg_errconf:
* mdadm/autocheck: true
--- End Message ---
--- Begin Message ---
also sprach Jerry Quinn <[EMAIL PROTECTED]> [2006.11.17.0707 +0100]:
> mdadm --create /dev/md0 -l 1 -n 2 missing /dev/hdd1
>
> to create a raid 1 array with 2 disks, 1 missing. The result I get is:
>
> mdadm: error opening /dev/md0: No such file or directory
It's sort of a bug, yes; but not really. Post-etch I hope to do
something about this. Until then, you have to use the --auto=yes
flag to the --create call. See the manpage.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
