Re: Re: RAID broken after kernel upgrade.

[Doug <doug@ubutton.com>]

I have already done this multiple times and nothing seems to have changed. Here is a copy of mdadm.conf for your inspection.

# 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 Paratrix.net

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 name=Paratrix.net:0 UUID=18833bc1:19156612:646c4e56:43311524
# This file was auto-generated on Mon, 27 May 2013 16:41:43 -0400
# by mkconf 3.2.5-5

# 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 Paratrix.net

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 name=Paratrix.net:0 UUID=18833bc1:19156612:646c4e56:43311524

# This file was auto-generated on Mon, 27 May 2013 16:41:43 -0400
# by mkconf 3.2.5-5


Does this look right? Any other ideas? Thanks for the help!