Brauch ich mdadm?
Tach auch,
auf einem meiner Server ist wohl per default mdadm installiert (Server
bei Hetzner).
Der Server verfuegt kedoch ueber einen Hardware-Raid von 3ware, laeuft
auch soweit.
Nun bekomme ich seit einem der letzten (zugegeben automatisierten)
Security-Updates folgende Mails in's Postfach:
========[snip]==============
Heirloom mailx version 12.1 6/15/06. Type ? for help.
"/var/mail/mein_user": 5 messages
>O 1 Cron Daemon Sun Jun 1 01:06 21/874 Cron <root@Debian-40-etch-64-LAMP> [ -x /usr/share/mdadm/checkarray ] && [ $(date +%d) -le 7 ] && /usr/
O 2 Cron Daemon Sun Jun 1 06:25 24/1161 Cron
<root@Debian-40-etch-64-LAMP> test -x /usr/sbin/anacron || ( cd / &&
run-parts --report /etc/cron.
O 3 root Fri Jun 6 09:23 20/607
O 4 Cron Daemon Sun Jun 8 06:25 24/1161 Cron
<root@Debian-40-etch-64-LAMP> test -x /usr/sbin/anacron || ( cd / &&
run-parts --report /etc/cron.
O 5 Cron Daemon Mon Jun 9 23:00 74/3358 Cron
<root@Debian-40-etch-64-LAMP> /root/cronjobs/security-update.sh
? 1
Message 1:
>From root@XXX.com Sun Jun 1 01:06:01 2008
Return-Path: <root@XXX.com>
X-Original-To: root
Delivered-To: root@XXX.com
From: root@XXX.com (Cron Daemon)
To: root@XXX.com
Subject: Cron <root@Debian-40-etch-64-LAMP> [ -x
/usr/share/mdadm/checkarray ] && [ $(date +%d) -le 7 ] &&
/usr/share/mdadm/checkarray --cron --all --quiet
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
Date: Sun, 1 Jun 2008 01:06:01 +0200 (CEST)
Status: RO
checkarray: W: no active MD arrays found.
checkarray: W: (maybe uninstall the mdadm package?)
========[snap]==============
und
========[snip]==============
>From root@XXX.com Mon Jun 9 23:00:58 2008
Return-Path: <root@XXX.com>
X-Original-To: root
Delivered-To: root@XXX.com
From: root@XXX.com (Cron Daemon)
To: root@XXX.com
Subject: Cron <root@Debian-40-etch-64-LAMP> /root/cronjobs/security-update.sh
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Date: Mon, 9 Jun 2008 23:00:10 +0200 (CEST)
Status: RO
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
The directory /lib/modules/2.6.18-6-amd64 still exists. Continuing as directed.
Done.
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Hmm. The package shipped with a symbolic link
/lib/modules/2.6.18-6-amd64/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.18-6-amd64/source
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
Not updating initrd symbolic links since we are being updated/reinstalled
========[snap]==============
Also ich hab mdadm nicht installiert (muss wohl default drauf gewesen
sein). Brauch ich das Teil ueberhaupt (bei 'nem eingerichteten
Hardware-Raid)? Oder kann ich's via Aptitude einfach wegwerfen, ohne
mir was zu zerschiessen?
Ach ja:
Wenn mir jemand erklaeren koennte, auf was ich $TERM setze (reicht da
einfach ein "export TERMINFO=vt100" fuer Batch-Jobs?), damit der
Aptitude-Batch ohne die Meckerei von debconf durchlaeuft, wuerde das
bestimmt sein Karma verbessern ;)
Gruss
Gregor
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
Reply to: