Package: mdadm Version: 4.2+20230508-5devuan1 Severity: minor Since some days I get the following message every day: mdadm: DeviceDisappeared event detected on md device /dev/md/md3 mdadm: DeviceDisappeared event detected on md device /dev/md/md2 mdadm: DeviceDisappeared event detected on md device /dev/md/md1 mdadm: DeviceDisappeared event detected on md device /dev/md/md0 mdadm: NewArray event detected on md device /dev/md0 mdadm: NewArray event detected on md device /dev/md1 mdadm: NewArray event detected on md device /dev/md3 mdadm: NewArray event detected on md device /dev/md2
This come from cron and the command `mdadm --monitor --scan --oneshot`.
(Which produce the same message.)
I never had any md device under /dev/md/*. They was always under
/dev/mdX.
And my /etc/mdadm/mdadm.conf has the following entries:
ARRAY /dev/md0 metadata=0.90 UUID=xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx
ARRAY /dev/md1 metadata=1.0 name=ikki:1
UUID=xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx
ARRAY /dev/md2 metadata=1.0 name=ikki:2
UUID=xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx
ARRAY /dev/md3 metadata=1.0 name=ikki:3
UUID=xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx
/proc/mdstat has the following:
~> cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda6[3] sdb6[2]
419430260 blocks super 1.0 [2/2] [UU]
bitmap: 0/2 pages [0KB], 131072KB chunk
md3 : active raid1 sda7[0] sdb7[2]
419430208 blocks super 1.0 [2/2] [UU]
bitmap: 1/4 pages [4KB], 65536KB chunk
md1 : active raid1 sda5[0] sdb5[2]
1073741632 blocks super 1.0 [2/2] [UU]
bitmap: 0/8 pages [0KB], 65536KB chunk
md0 : active raid1 sdb1[1] sda1[0]
1998976 blocks [2/2] [UU]
unused devices: <none>
So it is strange where this "DeviceDisappeared" is coming from. Nowhere
in my system is a mentioning /dev/md/mdX.
-- Package-specific info:
IMPORTANT:
please do not forget to include all relevant system information with this
bug report. You could run
/usr/share/bug/mdadm/script 3>&1
as root and attach or include the output.
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux 6 (excalibur/ceres)
Release: 6
Codename: excalibur ceres
Architecture: x86_64
Kernel: Linux 6.1.12 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC,
TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.5.82
ii eudev [udev] 3.2.12-1
ii init-system-helpers 1.65.2devuan1
ii libc6 2.37-3
ii libeudev1 3.2.12-1
Versions of packages mdadm recommends:
ii kmod 30+20230519-1
Versions of packages mdadm suggests:
ii exim4-daemon-light [mail-transport-agent] 4.96-16
-- Configuration Files:
/etc/logcheck/ignore.d.server/mdadm [Errno 13] Permission denied:
'/etc/logcheck/ignore.d.server/mdadm'
/etc/logcheck/violations.d/mdadm [Errno 13] Permission denied:
'/etc/logcheck/violations.d/mdadm'
-- debconf information:
mdadm/initrdstart_msg_intro:
mdadm/autostart: true
* mdadm/autoscan: true
* mdadm/start_daemon: true
* mdadm/initrdstart: all
mdadm/initrdstart_notinconf: false
mdadm/init-system-not-systemd:
mdadm/initrdstart_msg_errconf:
* mdadm/mail_to: r...@ethgen.de
mdadm/initrdstart_msg_errmd:
mdadm/initrdstart_msg_errblock:
* mdadm/autocheck: false
mdadm/initrdstart_msg_errexist:
Gruß
Klaus
--
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
signature.asc
Description: PGP signature
