Package: mdadm Version: 2.6.7.2-3 Severity: normal
Tonight's checkarray triggered a slew of SATA errors, which finally caused the machine to lock up completely (see attached syslog). Possibly the hardware is flakey, but then I've been stressing it a lot in the last few weeks without any problems. Is it possible that checking multiple arrays in parallel does Bad Things(tm)? (The kernel is from backports.org (see below)) Thanks, Chris -- Package-specific info: -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mdadm depends on: ii debconf 1.5.24 Debian configuration management sy ii libc6 2.7-18 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-88 creates device files in /dev ii udev 0.125-7+lenny3 /dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4 4.69-9 metapackage to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-9 lightweight Exim MTA (v4) daemon ii module-init-tools 3.4-1 tools for managing Linux kernel mo mdadm suggests no packages. other: ii linux-image-2.6.30-bpo.2-amd64 2.6.30-7~bpo50+1 Linux 2.6.30 image on AMD64 -- debconf information: * mdadm/autostart: true * mdadm/mail_to: root mdadm/initrdstart_msg_errmd: * mdadm/initrdstart: /dev/md0 /dev/md1 /dev/md2 mdadm/initrdstart_msg_errconf: mdadm/initrdstart_notinconf: false mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: * mdadm/autocheck: false mdadm/initrdstart_msg_errblock: * mdadm/start_daemon: true
syslog.gz
Description: GNU Zip compressed data
