Raid Gone After reboot.

Jousa11 · 23. August 2016

Hi All,
so i did a reboot and on coming back up the raid array did not mount and appeared to be missing.

cat /etc/fstab

UUID=6bc6fd5a-d569-419b-9325-00eacbb5703e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=f38a1cf1-4cad-45bd-827d-dc5e0fe8b929 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sdb1 /media/usb0 auto rw,user,noauto 0 0
# >>> [openmediavault]
UUID=edc193b2-856a-4c70-b16c-8b8a3a7b76a7 /media/edc193b2-856a-4c70-b16c-8b8a3a7b76a7 xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
# <<< [openmediavault]

cat /etc/mdadm/mdadm.conf
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

cat /proc/mdstat

Personalities :
unused devices: <none>

mdadm --detail --scan --verbose

Brings back no results.

Thanks for all your help in Advance

-Joe

ryecoaaron · 23. August 2016

There is more output we need - read

Jousa11 · 23. August 2016

Hi Thanks for the reply details requested listed below.
cat /proc/mdstat

Code

root@Storage-Server:~# cat /proc/mdstat
Personalities : 
unused devices: <none>

blkid

Code

root@Storage-Server:~# blkid
/dev/sda1: UUID="6bc6fd5a-d569-419b-9325-00eacbb5703e" TYPE="ext4" PARTUUID="00027e65-01"
/dev/sda5: UUID="f38a1cf1-4cad-45bd-827d-dc5e0fe8b929" TYPE="swap" PARTUUID="00027e65-05"
/dev/sdb: UUID="7d3af6ec-d2a8-7389-e2e1-1d5e80506fd9" UUID_SUB="f0e8d554-b62f-0617-6ae4-504a4e3a677d" LABEL="Storage-Server:MirrorRaid" TYPE="linux_raid_member"
/dev/sdc: UUID="7d3af6ec-d2a8-7389-e2e1-1d5e80506fd9" UUID_SUB="a9da859b-bb92-d6b6-e329-f217a57086d6" LABEL="Storage-Server:MirrorRaid" TYPE="linux_raid_member"

fdisk -l

Code

root@Storage-Server:~# fdisk -l


Disk /dev/sda: 59.6 GiB, 64023257088 bytes, 125045424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00027e65


Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048 119883775 119881728 57.2G 83 Linux
/dev/sda2       119885822 125044735   5158914  2.5G  5 Extended
/dev/sda5       119885824 125044735   5158912  2.5G 82 Linux swap / Solaris


Disk /dev/sdb: 4.6 TiB, 5000947302400 bytes, 1220934400 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 4.6 TiB, 5000947302400 bytes, 1220934400 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Alles anzeigen

cat /etc/mdadm/mdadm.conf

Code

root@Storage-Server:~# 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

Alles anzeigen

mdadm --detail --scan --verbose

Code

root@Storage-Server:~# mdadm --detail --scan --verbose
root@Storage-Server:~#

Drives being used
2x WD Elements 207C

Thank You in advance

ryecoaaron · 23. August 2016

Just to see if it works (won't be finished after this):

mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]

Jousa11 · 23. August 2016

That worked perfect

Code

root@Storage-Server:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 2 drives.

ryecoaaron · 23. August 2016

Now, execute the following and you should be ok:

omv-mkconf mdadm

Jousa11 · 23. August 2016

Hi Tried OMV-mkcon mdadm
and after a reboot I still had to use the code above to mount the array manually.

Code

root@Storage-Server:~# sudo omv-mkconf mdadm
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64

ryecoaaron · 23. August 2016

I wish I knew what caused this but it happens on some systems. What is the output of: cat /etc/mdadm/mdadm.conf

Jousa11 · 23. August 2016

no problem, I really appreciate the help
The output is.

Code

root@Storage-Server:~# 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/md127 metadata=1.2 name=Storage-Server:MirrorRaid UUID=7d3af6ec:d2a87389:e2e11d5e:80506fd9

Alles anzeigen

ryecoaaron · 23. August 2016

Everything looks right. I don't know why it isn't work at boot. Are they usb drives?

Jousa11 · 24. August 2016

Hi,
Sorry for the slow reply.
Yes they are both USB drives.

ryecoaaron · 24. August 2016

That is the problem. USB drives seem to start late sometimes and missing the mdadm (raid) assembly search. You can check your bios for usb start delays but not much I can do to fix this one.

Jousa11 · 24. August 2016

No problem,
Thanks for the command to mount it

Drake008 · 16. September 2016

Can somebody help me,too

My Stripeset (RAID0) is missing. Even in the raid managment it isn'T there anymore.

Please help me.

Code

W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.

That'S what I get when I type in

omv-mkconf mdadm

and that is in the

# 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

Raid Gone After reboot.

Jetzt mitmachen!

Tags