Package: mdadm
Version: 1.9.0-2.1
Severity: normal
I will research this more when I get time, right now I think it is
important that I document it before I go out (and forgot the details).
Possible factors that might be relevant:
* udev
* devfs style names are used
* all raid paritions were up and running at the time on installation
(shouldn't madam be able to tell that they are already started and
not try to start them again?)
(Reading database ... 149051 files and directories currently installed.)
Unpacking mdadm (from .../mdadm_1.9.0-2.1_i386.deb) ...
Setting up mdadm (1.9.0-2.1) ...
Starting raid devices:
mknod: `hda': File exists
mknod: `hda1': File exists
mknod: `hda2': File exists
mknod: `hda3': File exists
mknod: `hda5': File exists
mknod: `hda6': File exists
mknod: `hda7': File exists
mknod: `hda8': File exists
mknod: `hda9': File exists
mknod: `hda10': File exists
mknod: `hdc': File exists
mknod: `hdc1': File exists
mknod: `hdc2': File exists
mknod: `hdc3': File exists
mknod: `hdc5': File exists
mknod: `hdc6': File exists
mknod: `hdc7': File exists
mknod: `hdc8': File exists
mknod: `hdc9': File exists
mknod: `hdc10': File exists
mknod: `md10': File exists
mknod: `md34': File exists
mknod: `md20': File exists
mknod: `md12': File exists
mknod: `md14': File exists
mknod: `md30': File exists
mknod: `md32': File exists
mknod: `/dev/md/0': File exists
mknod: `/dev/md/10': File exists
mknod: `/dev/md/12': File exists
mknod: `/dev/md/14': File exists
mknod: `/dev/md/20': File exists
mdadm: failed to add /dev/hdc2 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda2 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc5 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda5 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc6 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda6 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc7 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda7 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hda8 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hdc8 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from -1 drives - not enough to start the array.
mdadm: failed to add /dev/hdc9 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda9 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc10 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda10 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc2 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda2 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc5 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda5 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc6 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda6 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc7 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda7 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc8 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda8 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc9 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda9 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
mdadm: failed to add /dev/hdc10 to /dev/md/0: Device or resource busy
mdadm: failed to add /dev/hda10 to /dev/md/0: Device or resource busy
mdadm: /dev/md/0 assembled from 0 drives - not enough to start the array.
done.
Starting RAID monitor daemon: mdadm -F.
snoopy:~# cat /proc/mdstat
Personalities : [raid1]
md32 : active raid1 hdc9[1] hda9[0]
9827904 blocks [2/2] [UU]
md30 : active raid1 hdc8[1] hda8[0]
9827904 blocks [2/2] [UU]
md14 : active raid1 hdc7[1] hda7[0]
2999680 blocks [2/2] [UU]
md12 : active raid1 hdc6[1] hda6[0]
2999680 blocks [2/2] [UU]
md20 : active raid1 hdc2[1] hda2[0]
2999744 blocks [2/2] [UU]
md34 : active raid1 hdc10[1] hda10[0]
9829376 blocks [2/2] [UU]
md10 : active raid1 hdc5[1] hda5[0]
499840 blocks [2/2] [UU]
unused devices: <none>
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages mdadm depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii makedev 2.3.1-77 creates device files in /dev
-- debconf information:
* mdadm/autostart: true
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: root
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
