staging.inyokaproject.org

Vorkonfiguration der Pakete ...
/tmp/mdadm.config.99011: 32: /etc/default/mdadm: ARRAY: not found
mdadm konnte nicht vorkonfiguriert werden, Exit-Status 127
bash (4.2-2ubuntu2.6) wird eingerichtet ...
update-alternatives: /usr/share/man/man7/bash-builtins.7.gz wird verwendet, um /usr/share/man/man7/builtins.7.gz (builtins.7.gz) im Auto-Modus bereitzustellen.
(Lese Datenbank ... 131893 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Ersetzen von mdadm 3.2.5-1ubuntu0.2 (durch .../mdadm_3.2.5-1ubuntu0.3_amd64.deb) ...
/etc/init.d/mdadm: 32: /etc/default/mdadm: ARRAY: not found
invoke-rc.d: initscript mdadm, action "stop" failed.
dpkg: Warnung: Unterprozess altes pre-removal-Skript gab den Fehlerwert 127 zurück
dpkg - stattdessen wird Skript aus dem neuen Paket probiert ...
/etc/init.d/mdadm: 32: /etc/default/mdadm: ARRAY: not found
invoke-rc.d: initscript mdadm, action "stop" failed.
dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/mdadm_3.2.5-1ubuntu0.3_amd64.deb (--unpack):
 Unterprozess neues pre-removal-Skript gab den Fehlerwert 127 zurück
/var/lib/dpkg/info/mdadm.config: 32: /etc/default/mdadm: ARRAY: not found
dpkg: Fehler beim Aufräumen:
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 127 zurück
Vorbereitung zum Ersetzen von mount 2.20.1-1ubuntu3 (durch .../mount_2.20.1-1ubuntu3.1_amd64.deb) ...
Ersatz für mount wird entpackt ...
Trigger für man-db werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/mdadm_3.2.5-1ubuntu0.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

# mdadm Debian configuration
#
# You can run 'dpkg-reconfigure mdadm' to modify the values in this file, if
# you want. You can also change the values here and changes will be preserved.
# Do note that only the values are preserved; the rest of the file is
# rewritten.
#

# AUTOCHECK:
#   should mdadm run periodic redundancy checks over your arrays? See
#   /etc/cron.d/mdadm.
AUTOCHECK=true

# START_DAEMON:
#   should mdadm start the MD monitoring daemon during boot?
START_DAEMON=true

# DAEMON_OPTIONS:
#   additional options to pass to the daemon.
DAEMON_OPTIONS="--syslog"

# VERBOSE:
#   if this variable is set to true, mdadm will be a little more verbose e.g.
#   when creating the initramfs.
VERBOSE=false

# MAIL_TO:
#   this variable is now managed in /etc/mdadm/mdadm.conf (MAILADDR).
#   Please see mdadm.conf(5).
MAIL_TO=[meine Mailadresse]

ARRAY /dev/md/NAS:0 metadata=1.2 spares=1 name=NAS:0 UUID=857a7b27:997b0dcc:83e571fb:a3ce3cec

#sudo mdadm --detail --scan
ARRAY /dev/md/NAS:0 metadata=1.2 spares=1 name=NAS:0 UUID=857a7b27:997b0dcc:83e571fb:a3ce3cec

/usr/share/mdadm/mkconf: 32: /etc/default/mdadm: ARRAY: not found

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR [meine Mailadresse]

# definitions of existing MD arrays
ARRAY /dev/md/NAS:0 metadata=1.2 UUID=857a7b27:997b0dcc:83e571fb:a3ce3cec name=NAS:0

# This file was auto-generated on Sat, 15 Oct 2011 01:19:21 +0200
# by mkconf $Id$
MAILFROM [meine Mailadresse]

#sudo mdadm --detail /dev/md0

/dev/md0:
        Version : 1.2
  Creation Time : Sun Mar  3 00:22:59 2013
     Raid Level : raid5
     Array Size : 9766914560 (9314.46 GiB 10001.32 GB)
  Used Dev Size : 1953382912 (1862.89 GiB 2000.26 GB)
   Raid Devices : 6
  Total Devices : 7
    Persistence : Superblock is persistent

    Update Time : Mon Jan  5 02:44:13 2015
          State : clean
 Active Devices : 6
Working Devices : 7
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 512K

           Name : NAS:0  (local to host NAS)
           UUID : 857a7b27:997b0dcc:83e571fb:a3ce3cec
         Events : 82255

    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc
       2       8       48        2      active sync   /dev/sdd
       3       8       64        3      active sync   /dev/sde
       5       8       96        4      active sync   /dev/sdg
       6       8       81        5      active sync   /dev/sdf1

       7       8      113        -      spare   /dev/sdh1

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=8378364a-4662-4b50-82a5-737decd2f50c /               ext4    errors=remount-ro 0       1
# /mnt/share/Video was on /dev/md0 during installation
UUID=fed696d7-3d71-4d46-9192-fafdf40b0ba9 /mnt/share/ ext4    defaults        0       2
# swap was on /dev/sda5 during installation
UUID=2171cba9-44d1-4290-98e8-60050ea1dc82 none            swap    sw              0       0
# USB-Backup-Disk
/dev/SeagateHDD /mnt/usb        ntfs    noauto,user,defaults    0       2