1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
Template: mdadm/initrdstart
Type: string
Default: all
_Description: MD arrays needed for the root filesystem:
${msg}
.
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".
Template: mdadm/initrdstart_msg_intro
Type: text
_Description: for internal use - only the long description is needed.
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.
.
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.
.
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.
Template: mdadm/initrdstart_msg_errexist
Type: text
_Description:
An error occurred: device node does not exist
Template: mdadm/initrdstart_msg_errblock
Type: text
_Description:
An error occurred: not a block device
Template: mdadm/initrdstart_msg_errmd
Type: text
_Description:
An error occurred: not an MD array
Template: mdadm/initrdstart_msg_errconf
Type: text
_Description:
An error occurred: array not listed in mdadm.conf file
Template: mdadm/initrdstart_notinconf
Type: boolean
Default: false
_Description: Proceed with starting arrays not listed in mdadm.conf?
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.
.
Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend
to continue.
.
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.
Template: mdadm/autostart
Type: boolean
Default: true
_Description: Do you want to start MD arrays automatically?
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 multiple 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.
Template: mdadm/autocheck
Type: boolean
Default: true
_Description: Should mdadm run monthly redundancy checks of the MD arrays?
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.
.
The default, if turned on, is to run the checks on the first Sunday of every
month at 01:06 o'clock.
Template: mdadm/start_daemon
Type: boolean
Default: true
_Description: Do you want to start the MD monitoring daemon?
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.
Template: mdadm/mail_to
Type: string
Default: root
_Description: Recipient for email notifications:
Please enter the email address of the user who should get the email
notification for important MD events.
|
