MDADM Help

ChrispyChris

Member
Jul 8, 2016
13
0
21
32
I installed my Proxmox on a single SSD. I have to drives in my server that were RAIDed through OMV but I broke everything, so I am trying to go the more manual route this time and mount them via MDADM. When I apt-get install mdadm, it's asking me MD arrays needed for root file system, the default answer is all. I don't want to break anything again, so I'm unsure if I need to make it blank, or if I do all. Can anyone provide help please?

Thanks,
Chris
 
I ended up escaping out but still got some output. First this is my lsblk -l:
root@chrispychris:~# lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
sda1 8:1 0 1007K 0 part
sda2 8:2 0 127M 0 part
sda3 8:3 0 299.9G 0 part
pve-root 251:0 0 74.8G 0 lvm /
pve-swap 251:1 0 8G 0 lvm [SWAP]
pve-data_tmeta 251:2 0 104M 0 lvm
pve-data-tpool 251:4 0 201.1G 0 lvm
pve-data 251:5 0 201.1G 0 lvm
pve-vm--100--disk--1 251:6 0 2G 0 lvm
pve-data_tdata 251:3 0 201.1G 0 lvm
pve-data-tpool 251:4 0 201.1G 0 lvm
pve-data 251:5 0 201.1G 0 lvm
pve-vm--100--disk--1 251:6 0 2G 0 lvm
sdb 8:16 0 232.9G 0 disk
sdb1 8:17 0 232.9G 0 part
sdc 8:32 0 2.7T 0 disk
md127 9:127 0 2.7T 0 raid1
sdd 8:48 0 2.7T 0 disk
md127 9:127 0 2.7T 0 raid1

This is from installing mdadm to just typing mdadm after install. Then I escaped and it seemed to build a conf. Did I mess up or can I still get to those RAID drives?
root@chrispychris:~# apt-get install mdadm
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
mdadm
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 432 kB of archives.
After this operation, 1,233 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian/ jessie/main mdadm amd64 3.3.2-5+deb8u1 [432 kB]
Fetched 432 kB in 1s (330 kB/s)
Preconfiguring packages ...
Selecting previously unselected package mdadm.
(Reading database ... 39010 files and directories currently installed.)
Preparing to unpack .../mdadm_3.3.2-5+deb8u1_amd64.deb ...
Unpacking mdadm (3.3.2-5+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u5) ...
Setting up mdadm (3.3.2-5+deb8u1) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (215-17+deb8u5) ...
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.4.6-1-pve

Lastly, this is the conf file, it does have OpenMediaVault in there, so I'm wondering if this is good news since I created it through OMV in the first place.
root@chrispychris:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

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

# 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 root

# definitions of existing MD arrays
ARRAY /dev/md/mdadm metadata=1.2 UUID=2dd0a643:5cd003fc:89a63367:f1f14503 name=openmediavault:mdadm

# This configuration was auto-generated on Mon, 03 Oct 2016 21:41:03 -0700 by mkconf