Your message dated Mon, 23 Aug 2021 10:49:20 -0700 with message-id <CAFHYt57yHQmvcbBGasz8G=yjpurffv16sgs8hj2ogfug+vx...@mail.gmail.com> and subject line mdadm: Default to mailing root has caused the Debian Bug report #668035, regarding mdadm: Default to mailing root 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 668035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668035 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mdadm Version: 3.1.4-1+8efb9d1+squeeze1 Severity: wishlist Hi, Just got this mail: /etc/cron.daily/mdadm: mdadm: No mail address or alert command - not monitoring. run-parts: /etc/cron.daily/mdadm exited with return code 1 Can't you default to mailing root or just using syslog? Greetings, Olaf -- Package-specific info: --- mdadm.conf DEVICES /dev/[hs]d* MAILADDR root --- /etc/default/mdadm INITRDSTART='all' AUTOSTART=true AUTOCHECK=true # modified by installimage START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md2 : active raid1 sda3[0] sdb3[1] 485764928 blocks [2/2] [UU] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 2096064 blocks [2/2] [UU] unused devices: <none> --- /proc/partitions: major minor #blocks name 8 16 488386584 sdb 8 17 2096128 sdb1 8 18 524288 sdb2 8 19 485765019 sdb3 8 0 488386584 sda 8 1 2096128 sda1 8 2 524288 sda2 8 3 485765019 sda3 9 0 2096064 md0 9 1 524224 md1 9 2 485764928 md2 --- LVM physical volumes: --- mount output /dev/md2 on / type ext4 (rw) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/md1 on /boot type ext3 (rw) --- initrd.img-2.6.32-5-amd64: 59834 blocks f4fbd9099399ab08ba9b9f6c71d77595 ./scripts/local-top/mdadm f7fccd32317e1181154b4b2be1394265 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid456.ko 905e5cc4a118149d0c340eb1883d9f9e ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid1.ko 37f132b3fc02c5ad1df693d23be302bb ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mod.ko a4fce63c3ebb84949e4016c2d4d5cb5b ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/multipath.ko 834b9d4179ff3e2922d6bf3b828fa773 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mirror.ko 79c5ac8b7e1f59b1790ae7c4c685fc01 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-snapshot.ko fc100da3ed5b0444211c5cf0f7df4d12 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid10.ko 89ca16f29eb641da1ba74a5b3338011a ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-log.ko 5aa427eb50c6a8ab1dff72076937a594 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/linear.ko 36f23df0903e301bde290c62177cadc1 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid0.ko ce0efe63e859281525eac75bdbc83375 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid6_pq.ko 506c233b2d6ea200ebd68c1a3cc28552 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-region-hash.ko 24a56a3b8e09dd3a05ba1586848d803b ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/md-mod.ko 3b6d47953414af29100899677cc3f168 ./etc/mdadm/mdadm.conf 79246b981b4d424653bcabc1192b7161 ./sbin/mdadm --- initrd's /conf/conf.d/md: MD_HOMEHOST='Debian-60-squeeze-64-minimal' MD_DEVPAIRS='/dev/md0:raid1 /dev/md1:raid1 /dev/md2:raid1' MD_LEVELS='raid1 raid1 raid1' MD_DEVS=all MD_MODULES='raid1' --- /proc/modules: dm_mod 53994 0 - Live 0xffffffffa01c1000 aacraid 64464 0 - Live 0xffffffffa01a0000 raid10 17825 0 - Live 0xffffffffa017b000 raid456 44516 0 - Live 0xffffffffa0169000 async_raid6_recov 5186 1 raid456, Live 0xffffffffa0162000 async_pq 3495 2 raid456,async_raid6_recov, Live 0xffffffffa015c000 raid6_pq 77179 2 async_raid6_recov,async_pq, Live 0xffffffffa0143000 async_xor 2494 3 raid456,async_raid6_recov,async_pq, Live 0xffffffffa013d000 async_memcpy 1198 2 raid456,async_raid6_recov, Live 0xffffffffa0130000 async_tx 1750 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy, Live 0xffffffffa012a000 raid1 18431 3 - Live 0xffffffffa011f000 raid0 5517 0 - Live 0xffffffffa0118000 md_mod 73936 7 raid10,raid456,raid1,raid0, Live 0xffffffffa00fb000 scsi_mod 126789 5 aacraid,3w_9xxx,3w_xxxx,sd_mod,libata, Live 0xffffffffa0038000 --- /var/log/syslog: --- volume detail: /dev/sda is not recognised by mdadm. /dev/sda1: Magic : a92b4efc Version : 0.90.00 UUID : 39cf2b9f:25a3c752:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB) Array Size : 2096064 (2047.28 MiB 2146.37 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Update Time : Sun Apr 8 14:51:50 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 1f7518ee - correct Events : 20 Number Major Minor RaidDevice State this 0 8 1 0 active sync /dev/sda1 0 0 8 1 0 active sync /dev/sda1 1 1 8 17 1 active sync /dev/sdb1 -- /dev/sda2: Magic : a92b4efc Version : 0.90.00 UUID : 475c0e8a:28e7dda5:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 524224 (512.02 MiB 536.81 MB) Array Size : 524224 (512.02 MiB 536.81 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Sun Apr 8 14:42:37 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 302e1433 - correct Events : 42 Number Major Minor RaidDevice State this 0 8 2 0 active sync /dev/sda2 0 0 8 2 0 active sync /dev/sda2 1 1 8 18 1 active sync /dev/sdb2 -- /dev/sda3: Magic : a92b4efc Version : 0.90.00 UUID : 65feb1a5:40fdc3f8:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 485764928 (463.26 GiB 497.42 GB) Array Size : 485764928 (463.26 GiB 497.42 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Update Time : Sun Apr 8 14:53:01 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 83d2cf99 - correct Events : 44 Number Major Minor RaidDevice State this 0 8 3 0 active sync /dev/sda3 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync /dev/sdb3 -- /dev/sdb is not recognised by mdadm. /dev/sdb1: Magic : a92b4efc Version : 0.90.00 UUID : 39cf2b9f:25a3c752:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB) Array Size : 2096064 (2047.28 MiB 2146.37 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Update Time : Sun Apr 8 14:51:50 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 1f751900 - correct Events : 20 Number Major Minor RaidDevice State this 1 8 17 1 active sync /dev/sdb1 0 0 8 1 0 active sync /dev/sda1 1 1 8 17 1 active sync /dev/sdb1 -- /dev/sdb2: Magic : a92b4efc Version : 0.90.00 UUID : 475c0e8a:28e7dda5:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 524224 (512.02 MiB 536.81 MB) Array Size : 524224 (512.02 MiB 536.81 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Sun Apr 8 14:42:37 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 302e1445 - correct Events : 42 Number Major Minor RaidDevice State this 1 8 18 1 active sync /dev/sdb2 0 0 8 2 0 active sync /dev/sda2 1 1 8 18 1 active sync /dev/sdb2 -- /dev/sdb3: Magic : a92b4efc Version : 0.90.00 UUID : 65feb1a5:40fdc3f8:776c2c25:004bd7b2 Creation Time : Thu Apr 5 09:41:43 2012 Raid Level : raid1 Used Dev Size : 485764928 (463.26 GiB 497.42 GB) Array Size : 485764928 (463.26 GiB 497.42 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Update Time : Sun Apr 8 14:53:01 2012 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : 83d2cfab - correct Events : 44 Number Major Minor RaidDevice State this 1 8 19 1 active sync /dev/sdb3 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync /dev/sdb3 -- --- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=c3c1e883-fbe9-4c76-ad4b-fc043787709e ro --- grub2: insmod raid set root='(md2)' insmod raid set root='(md1)' insmod raid set root='(md1)' linux /vmlinuz-2.6.32-5-amd64 root=UUID=c3c1e883-fbe9-4c76-ad4b-fc043787709e ro insmod raid set root='(md1)' linux /vmlinuz-2.6.32-5-amd64 root=UUID=c3c1e883-fbe9-4c76-ad4b-fc043787709e ro single --- udev: ii udev 164-3 /dev/ and hotplug management daemon 4a574fcd059040d33ea18a8aa605a184 /lib/udev/rules.d/64-md-raid.rules --- /dev: brw-rw---- 1 root disk 9, 0 Apr 5 10:21 /dev/md0 brw-rw---- 1 root disk 9, 1 Apr 5 10:21 /dev/md1 brw-rw---- 1 root disk 9, 2 Apr 5 10:21 /dev/md2 /dev/disk/by-id: total 0 lrwxrwxrwx 1 root root 9 Apr 5 10:21 ata-SAMSUNG_HD501LJ_S0MUJR0B900002 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD501LJ_S0MUJR0B900002-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD501LJ_S0MUJR0B900002-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD501LJ_S0MUJR0B900002-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 ata-SAMSUNG_HD502IJ_S13TJ1LS201706 -> ../../sdb lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD502IJ_S13TJ1LS201706-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD502IJ_S13TJ1LS201706-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 ata-SAMSUNG_HD502IJ_S13TJ1LS201706-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 md-uuid-39cf2b9f:25a3c752:776c2c25:004bd7b2 -> ../../md0 lrwxrwxrwx 1 root root 9 Apr 5 10:21 md-uuid-475c0e8a:28e7dda5:776c2c25:004bd7b2 -> ../../md1 lrwxrwxrwx 1 root root 9 Apr 5 10:21 md-uuid-65feb1a5:40fdc3f8:776c2c25:004bd7b2 -> ../../md2 lrwxrwxrwx 1 root root 9 Apr 5 10:21 scsi-SATA_SAMSUNG_HD501LJS0MUJR0B900002 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD501LJS0MUJR0B900002-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD501LJS0MUJR0B900002-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD501LJS0MUJR0B900002-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 scsi-SATA_SAMSUNG_HD502IJS13TJ1LS201706 -> ../../sdb lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD502IJS13TJ1LS201706-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD502IJS13TJ1LS201706-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 scsi-SATA_SAMSUNG_HD502IJS13TJ1LS201706-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 wwn-0x50000f0007900002 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50000f0007900002-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50000f0007900002-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50000f0007900002-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 wwn-0x50024e90010ea106 -> ../../sdb lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50024e90010ea106-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50024e90010ea106-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 wwn-0x50024e90010ea106-part3 -> ../../sdb3 /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 Apr 5 10:21 pci-0000:00:12.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-0:0:0:0-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-0:0:0:0-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Apr 5 10:21 pci-0000:00:12.0-scsi-1:0:0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-1:0:0:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-1:0:0:0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Apr 5 10:21 pci-0000:00:12.0-scsi-1:0:0:0-part3 -> ../../sdb3 /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 9 Apr 5 10:21 307e3db4-e6ba-44d5-bce2-989c91c2b1f1 -> ../../md1 lrwxrwxrwx 1 root root 9 Apr 5 10:21 3fdd5f25-187d-4ff1-acab-2d2684e56176 -> ../../md0 lrwxrwxrwx 1 root root 9 Apr 5 10:21 c3c1e883-fbe9-4c76-ad4b-fc043787709e -> ../../md2 /dev/md: total 0 Auto-generated on Sun, 08 Apr 2012 14:53:02 +0200 by mdadm bugscript 3.1.4-1+8efb9d1+squeeze1 -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable'), (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mdadm depends on: ii debconf 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii udev 164-3 /dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4-daemon-heavy [mail 4.72-6+squeeze2 Exim MTA (v4) daemon with extended ii module-init-tools 3.12-2 tools for managing Linux kernel mo mdadm suggests no packages. -- Configuration Files: /etc/cron.d/mdadm changed: 7 3 11 * * root if [ -x /usr/share/mdadm/checkarray ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi -- debconf information: mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: mdadm/autostart: true * mdadm/autocheck: false mdadm/initrdstart_msg_errblock: * mdadm/mail_to: root mdadm/initrdstart_msg_errmd: * mdadm/initrdstart: all mdadm/initrdstart_msg_errconf: mdadm/initrdstart_notinconf: false * mdadm/start_daemon: true
--- End Message ---
--- Begin Message ---Hi, As the new maintainer of this package in Debian, I agree with previous statements about MAILADDR in this bug report. I cannot answer the question about syslog. Closing this bug. Kind regards Felix Lechner
--- End Message ---
