1 files changed, 0 insertions, 61 deletions
diff --git a/debian/mdadm.templates b/debian/mdadm.templates
index ddf63c76..5a797c55 100644
--- a/debian/mdadm.templates
+++ b/debian/mdadm.templates
@@ -7,67 +7,6 @@
 # Even minor modifications require translation updates and such
 # changes should be coordinated with translators and reviewers.
 
-Template: mdadm/initrdstart
-Type: string
-Default: all
-#flag:translate!:2
-_Description: MD arrays needed for the root file system:
- ${msg}
- .
- Please enter 'all', 'none', or a space-separated list of devices such as
- 'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted).
-
-Template: mdadm/initrdstart_msg_intro
-Type: text
-_Description: for internal use - only the long description is needed.
- If the system's root file system is located on an MD array (RAID), it needs to be
- started early during the boot sequence. If it is located 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 file system,
- 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 file system, 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: Start arrays not listed in mdadm.conf?
- The specified array (${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.
- .
- 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/autocheck
 Type: boolean
 Default: true