Hi all.
I posted in another thread but I wasn't getting any replies so I decided to make my own thread. My system froze recently and I had to hard to reset it. Its a new system with not much on the system but I would like to get this resolved so I can continue adding drives etc.
Below I have attached what I believe is needed (seen from other posts) but I can provide whatever else that is needed. Thanks all.
blkid
root@DAMONSTER:~# blkid
/dev/sda1: UUID="e5477dd0-ed1e-49a3-9705-cee63a271343" TYPE="ext4"
/dev/sda5: UUID="ba0e7955-8967-4430-8341-d70262c209cf" TYPE="swap"
/dev/sdb: UUID="daa561f3-03dd-1a2a-0dce-1874ecf7b928" UUID_SUB="1d11c96e-610c-fa41-d3b1-9273e355deb4" LABEL="DAMONSTSER:RAID6" TYPE="linux_raid_member"
/dev/sdc: UUID="daa561f3-03dd-1a2a-0dce-1874ecf7b928" UUID_SUB="3dd12876-70ab-456a-4553-2048d8d0b4e0" LABEL="DAMONSTSER:RAID6" TYPE="linux_raid_member"
/dev/sde: UUID="daa561f3-03dd-1a2a-0dce-1874ecf7b928" UUID_SUB="59e40195-e490-6c01-0090-c072e61ad717" LABEL="DAMONSTSER:RAID6" TYPE="linux_raid_member"
/dev/sdf: UUID="daa561f3-03dd-1a2a-0dce-1874ecf7b928" UUID_SUB="3e2c8010-65fb-789e-b722-89f9fbdda2b0" LABEL="DAMONSTSER:RAID6" TYPE="linux_raid_member"
/dev/sdg: UUID="daa561f3-03dd-1a2a-0dce-1874ecf7b928" UUID_SUB="3a91410e-bf2e-b40f-7177-5bc7be998ab6" LABEL="DAMONSTSER:RAID6" TYPE="linux_raid_member"
root@DAMONSTER:~#
lsmod | grep raid
root@DAMONSTER:~# lsmod | grep raid
raid456 48453 0
async_raid6_recov 12574 1 raid456
async_memcpy 12387 2 async_raid6_recov,raid456
async_pq 12605 2 async_raid6_recov,raid456
async_xor 12422 3 async_pq,async_raid6_recov,raid456
async_tx 12604 5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
raid6_pq 82624 2 async_pq,async_raid6_recov
md_mod 87742 1 raid456
raid_class 12832 1 mpt2sas
scsi_mod 162321 8 scsi_transport_sas,libata,libsas,mvsas,raid_class,mpt2sas,sd_mod,sg
root@DAMONSTER:~#
/etc/mdadm/mdadm.conf
root@DAMONSTER:~# cat /etc/mdadm/mdadm.conf
# 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.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
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>
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=DAMONSTSER:RAID6 UUID=daa561f3:03dd1a2a:0dce1874:ecf7b928
# instruct the monitoring daemon where to send mail alerts
MAILADDR ...@gmail.com
MAILFROM root
root@DAMONSTER:~#
/etc/default/mdadm
root@DAMONSTER:~# cat /etc/default/mdadm
# INITRDSTART:
# list of arrays (or 'all') to start automatically when the initial ramdisk
# loads. This list *must* include the array holding your root filesystem. Use
# 'none' to prevent any array from being started from the initial ramdisk.
#INITRDSTART='none'
# AUTOSTART:
# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically
# during boot?
AUTOSTART=true
# 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
root@DAMONSTER:~#