RAID 0 Array disappears after every reboot

  • ok, so here goes attempt 2.


    I recently wiped my old OMV version 4 server and installed OMV 5 (5.5.2-1), which has been going great, until i discovered a bug i started having an issue in OMV 4 where my RAID 0 array would disappear after every reboot and would have run some commands just to make it come back.


    My hardware layout is as follows:


    - sda - 4TB Storage Disk

    - sdb - 3TB storage Disk

    - sdc - 2TB Storage Disk

    - sdd - random USB i had in the machine

    - sde - 2TB Storage Disk

    - sdf Boot Drive



    Also here are some command i ran which can hopefully help to speed up a fix :)



    cat /etc/mdadm/mdadm.conf





    fdisk -l | grep "Disk " | grep sd | sort


    Code
    Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk /dev/sdd: 7.5 GiB, 8053063680 bytes, 15728640 sectors
    Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk /dev/sdf: 111.8 GiB, 120040980480 bytes, 234455040 sectors




    cat /proc/mdstat


    Code
    Personalities : [raid0] [linear] [multipath] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : active raid0 sda[0] sde[3] sdc[2] sdb[1]
    10743784960 blocks super 1.2 512k chunks
    unused devices: <none>



    blkid

    Code
    /dev/sda: UUID="87674581-aa4a-abfe-9312-d183a8ed4906" UUID_SUB="02249442-0c9b-53e9-0680-f81e34c7a115" LABEL="cb-server.cb-server:CorePool" TYPE="linux_raid_member"
    /dev/sdc: UUID="87674581-aa4a-abfe-9312-d183a8ed4906" UUID_SUB="d81adc61-5679-43cb-44d4-897697ae6797" LABEL="cb-server.cb-server:CorePool" TYPE="linux_raid_member"
    /dev/sdb: UUID="87674581-aa4a-abfe-9312-d183a8ed4906" UUID_SUB="72eca10b-a959-b3d9-2cf3-31ba469ea87e" LABEL="cb-server.cb-server:CorePool" TYPE="linux_raid_member"
    /dev/sdd1: LABEL="OPENMEDIAVA" UUID="48A6-D0E3" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="cee497a1-4ba6-4a90-ac8e-e3d509963f8b"
    /dev/sdf1: UUID="0925-8731" TYPE="vfat" PARTUUID="8df33f5f-045b-40e0-9069-417541e8b206"
    /dev/sdf2: UUID="e82406a6-2d1e-40a6-8407-39e6244667a3" TYPE="ext4" PARTUUID="270da3fa-168e-4b5a-8660-ad5ee2087e92"
    /dev/sdf3: UUID="c7521f20-4245-4779-897a-a168f27daf98" TYPE="swap" PARTUUID="c33c815f-d140-411f-8be2-ebaadf671173"
    /dev/sde: UUID="87674581-aa4a-abfe-9312-d183a8ed4906" UUID_SUB="c21c472f-43f2-546f-a21f-e7f300d1d143" LABEL="cb-server.cb-server:CorePool" TYPE="linux_raid_member"
    /dev/md0: LABEL="CorePoolData" UUID="6286e1c0-da5a-481e-98e5-5efc57f0463c" TYPE="ext4"




    fdisk -l | grep "Disk "




    mdadm --detail --scan --verbose


    Code
    ARRAY /dev/md0 level=raid0 num-devices=4 metadata=1.2 name=cb-server.cb-server:CorePool UUID=87674581:aa4aabfe:9312d183:a8ed4906
    devices=/dev/sda,/dev/sdb,/dev/sdc,/dev/sde



    Any help would be greatly appreciated :)


    *Also yes i know RAID 0 is stupid with the 1 disk dying casing an entire loss of data problem but i have weekly backups which works fine for me*

  • also the way i am able to make the array appear after every reboot is by having to issue these 3 commands:


    echo 2 > /sys/module/raid0/parameters/default_layout


    then...


    mdadm --stop /dev/md0


    then...


    mdadm --assemble --force --verbose /dev/md0 /dev/sd[abce]



    and that brings the array back

  • SeaBee

    Added the Label OMV 5.x
  • here's the output from cat /etc/fstab


  • that gives some firmware missing warming:


    Code
    update-initramfs: Generating /boot/initrd.img-5.5.0-0.bpo.2-amd64
    W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
    W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169


    Also it looks like it could be some network firmware issue and just for some extra info, i don't have any wireless card installed, my server is just connected through the motherboards ethernet port.

  • Wan't expecting an output, the norm is to run that and reboot as what you entering to get the raid back is a module change. But using your first line from post 2 I found this this is beyond me as this seems to relate to Raid 0 and the number of drives within the array so the output from mdadm --detail /dev/md0 would give you more information

  • ok, so mdadm --detail /dev/md0 gives:


  • According to that output and that article the default layout should be 2, that should be set in /etc/default/grub again the article says there should be a line in grub that states GRUB_CMDLINE_LINUX_DEFAULT="raid0.default_layout=2"

  • ok so i found another thread that had a similar issue for one of the missing firmware issues (here) and found that:

    cd /lib/firmware/rtl_nic


    and


    wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtl_nic/rtl8125a-3.fw


    then i updated it again with


    update-initramfs -u


    but im still left with this one missing firmware issue:


    Code
    update-initramfs: Generating /boot/initrd.img-5.5.0-0.bpo.2-amd64
    W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
  • According to that output and that article the default layout should be 2, that should be set in /etc/default/grub again the article says there should be a line in grub that states GRUB_CMDLINE_LINUX_DEFAULT="raid0.default_layout=2"

    is it ok to sudo nano into the grub file, edit it and reboot?




    my current grub file looks like this:



    would it be safe to just replace the GRUB_CMDLINE_LINUX_DEFAULT="quiet" line with GRUB_CMDLINE_LINUX_DEFAULT="raid0.default_layout=2"

  • huh, ok so i took a chance and replaced the GRUB_CMDLINE_LINUX_DEFAULT="quiet" line with GRUB_CMDLINE_LINUX_DEFAULT="raid0.default_layout=2"


    then ran the update-grub command and rebooted the machine and it looks like it worked!


    the raid array is still present!


    also after running the update-initramfs -u command from before only one issue is present, should i make a new post somewhere else or keep trying in this thread?


    Code
    update-initramfs: Generating /boot/initrd.img-5.5.0-0.bpo.2-amd64
    W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
  • huh, ok so i took a chance

    Why I've just run this up on a VM Raid 0 with 4 drives, the config files are exactly the same as yours and it rebooted without issue, the missing firmware means for whatever reason that module is missing and would probably not affect your system anyway, but I've run that on the VM and it's fine no missing modules, and my kernel is the same.

  • SeaBee

    Added the Label resolved
  • Why I've just run this up on a VM Raid 0 with 4 drives, the config files are exactly the same as yours and it rebooted without issue, the missing firmware means for whatever reason that module is missing and would probably not affect your system anyway, but I've run that on the VM and it's fine no missing modules, and my kernel is the same.

    weird, might just be something up with my hardware or something.


    well at least the main issue is fixed.


    Thanks a ton for your help :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!