# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n"
"POT-Creation-Date: 2006-09-13 10:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "MD arrays needed for the root filesystem:"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "${msg}"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid ""
"Please enter a space-separated list of devices, 'all', or 'none'. You may "
"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid "for internal use - only the long description is needed."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If your system has its root filesystem on an MD array (RAID), it needs to be "
"started early during the boot sequence. If your root filesystem is on a "
"logical volume (LVM), which is on MD, all constituent arrays need to be "
"started."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you know exactly which arrays are needed to bring up the root filesystem, "
"and you want to postpone starting all other arrays to a later point in the "
"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to "
"simply start all available arrays."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you do not need or want to start any arrays for the root filesystem, "
"leave the answer blank (or enter 'none'). This may be the case if you are "
"using kernel autostart or do not need any arrays to boot."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid "An error occurred: device node does not exist"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:4001
msgid "An error occurred: not a block device"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:5001
msgid "An error occurred: not an MD array"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:6001
msgid "An error occurred: array not listed in mdadm.conf file"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid "Proceed with starting arrays not listed in mdadm.conf?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"The array you have specified (${array}) is not listed in the configuration "
"file ${config}. Therefore it cannot be started during boot, unless you "
"correct the configuration file and recreate the initial ramdisk."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend "
"to continue."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"This warning is only relevant if you need arrays to be started from the "
"initial ramdisk to be able to boot. If you use kernel autostarting, or do "
"not need any arrays to be started as early as the initial ramdisk is loaded, "
"you can simply continue. Alternatively, choose not to continue and enter "
"'none' when prompted which arrays to start from the initial ramdisk."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid "Do you want to start MD arrays automatically?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
msgid ""
"Once the base system has come up, mdadm can start all MD arrays (RAIDs) "
"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless "
"you have compiled multi-device (MD) support into the kernel and marked all "
"partitions part of MD arrays with type 0xfd (as those and only those will be "
"started automatically by the kernel), this is probably what you want."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"If your kernel supports it (>> 2.6.14), mdadm can periodically check the "
"redundancy of your MD arrays (RAIDs). This may be a resource-intensive "
"process, depending on your setup, but it could help prevent rare cases of "
"data loss. Note that this is a read-only check unless errors are found; if "
"errors are found, mdadm will try to correct them, which may result in write "
"access to the media."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"The default, if turned on, is to run the checks on the first Sunday of every "
"month at 01:06 o'clock."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid "Do you want to start the MD monitoring daemon?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure). You probably want to enable it."
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid "Recipient for email notifications:"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid ""
"Please enter the email address of the user who should get the email "
"notification for important MD events."
msgstr ""