NEWBIE: Failing to create RAID1 /w xfs using webgui

1st Official Post

    Dear,


    newbie user for OMV, but 22 years of Linux experience (e.g. I do accept help based on bash-commands). Trying to install a Zotac Mini-PC with AMD350 CPU and 2 x 4TB USB disks using OMV 0.5.9.


    I have defined mirrored disk /dev/md0 using the webgui based on my two USB disks. Both disks have been wiped in OMV first.



    This array is not visible after a reboot. As a result I cannot create a XFS filesystem and cannot create shares.


    Using command line I can start the array, create a filesystem and mount it temporarly:


    df -h:

    Code
    root@fob5:/etc/openmediavault# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             231G  827M  218G   1% /
tmpfs                 1.2G     0  1.2G   0% /lib/init/rw
udev                  1.2G  156K  1.2G   1% /dev
tmpfs                 1.2G     0  1.2G   0% /dev/shm
tmpfs                 1.2G     0  1.2G   0% /tmp
/dev/md0              3.7T  5.5M  3.7T   1% /mnt/tmp


    blkid:

    Code
    /dev/sda1: UUID="52092f26-87ff-4c2c-8b96-9a7bf5bb4a10" TYPE="ext4" 
/dev/sda5: UUID="a40006cf-d7a8-41a7-aef4-0fc8dc98f166" TYPE="swap" 
/dev/sdb: UUID="f7d96e8a-f5c3-106f-5b79-e67298f67ee3" LABEL="fob5:USBMIRROR" TYPE="linux_raid_member" 
/dev/sdc: UUID="f7d96e8a-f5c3-106f-5b79-e67298f67ee3" LABEL="fob5:USBMIRROR" TYPE="linux_raid_member"


    mount:

    Code
    /dev/sda1 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)
/dev/md0 on /mnt/tmp type xfs (rw)


    The array is not listed in /etc/fstab:


    and not in /etc/openmediavault/config.xml:


    Code
    root@fob5:/etc/openmediavault# grep md0 config.xml
root@fob5:/etc/openmediavault#


    Questions: how can I assemble the array automatically and get it visible in OMV?


    Thanks, -MN

    Sorry, mounting it to /mnt/tmp was a test...


    Unmounted, rebooted, array is still not showing up and requires

    Code
    mdadm --assemble /dev/md0

    .


    Thanks, -MN

    Reboot, waited 90 minutes. Same issue:


    • /dev/md0 is not available after reboot[/*]
    • mdadm --assemble /dev/md0 immediately shows /dev/md0 in the webgui[/*]
    • /dev/md0 is not available for filesystem creation[/*]
    • mkfs.xfs -f /dev/md0 brings up /dev/md0 as zfs filesystem in the webgui[/*]


    /dev/md0 has been created using the webgui, both disks wiped and then mirrored. Status clean.

    • Official Post

    It looks like the drives are in a usb enclosure(s)? If so, it probably needs more of a delay to initialize when booting. The system boots before the enclosure is ready and it does not see it. We have seen this issue before. Look for a usb delay in the bios.

    omv 7.0-11 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.1 | compose 7.0.1 | cputemp 7.0 | mergerfs 7.0


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thank you, ryecoaaron,


    this would explain why /dev/md0 becomes available after a manual mdadm --assemble /dev/md0. But it does not explain why I cannot create a filesystem, right?


    From my feeling the issue is one step before, during the creation of the /dev/md0 device. Should not the webgui add the newly created mirror into the <storage>-container in config.xml?

    • Official Post

    Are you clicking Save and then Apply? Any reason you are still using 0.5.9? I would update.

    omv 7.0-11 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.1 | compose 7.0.1 | cputemp 7.0 | mergerfs 7.0


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from "Morgennebel"

    From my feeling the issue is one step before, during the creation of the /dev/md0 device. Should not the webgui add the newly created mirror into the <storage>-container in config.xml?


    No, nothing is stored in the config.xml because MDADM and LVM devices are auto-detected by the system without any config done by OMV. The only config file that is modified is /etc/mdadm/mdadm.conf (this is done after the creation of the RAID via WebGUI).

    Upgraded to 0.5.49 - no change and no solution.


    Here is /var/log/kern.log after a reboot (without identified /dev/md0):



    This log proves that both USB disks are being identified and added during the boot process in correct order.


    However mdadm has issues assembling the array:



    Please note that the disks are 4TB in size.


    When I logged into the system and called fdisk /dev/md0 it complained about the partition size. gparted identified an msdos partition type using 512 Bytes blocks.
    Manually reconfiguring /dev/md0 with parted showed one partition 4 TB in size on 4KB block sizes.


    Please remember that /dev/md0 was created by selecting both disks in the webgui. No command tasks.


    May I ask if OMV supports 4 TB disks on USB correctly?


    Thanks, -MN

    • Official Post
    Quote from "Morgennebel"

    May I ask if OMV supports 4 TB disks on USB correctly?


    OMV does but that doesn't mean that the Debian Squeeze underlying OS does with the standard kernel. I would install the backports 3.2 kernel. Install omv-extras and there is a button to install it for you. This may help.


    When you upgraded to 0.5.49, did you delete the array and start over? Not saying you need to but this may fix the array not showing up to create a filesystem. If you don't want to create a new array and let it sync, you can just create a filesystem:


    mkfs.ext4 /dev/md0


    This will show up in the OMV web interface to be mounted - don't mount from the command line.

    omv 7.0-11 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.1 | compose 7.0.1 | cputemp 7.0 | mergerfs 7.0


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thank you, ryecoaaron,


    I have upgraded to 3.2 kernel and wiped both disks, destroyed the array and using the webgui are re-building a new RAID1 on 2 x 4TB USB disks. Unfortunately it takes 5 days to re-sync so I will post my result in a few days...


    Thanks everyone for the help and ideas,


    Ciao, -MN

    As advised I:


    • Installed kernel-3.2
    • Destroyed the array
    • Rebuilt the array using the webgui (about 25% faster)
    • Webgui still reports a zfs filesystem with many n/a n/a coloumns
    • Still the array is not visible on the webgui to create a new filesystem
    • Used mkfs.ext4 /dev/md0 to create a filesystem
    • Used webgui to mount /dev/md0 filesystem


    There seems to be a flaw between creating arrays and recognizing them to create a filesystem...


    Logfiles:

    Code
    root@fob5:~# cat /proc/mdstat 
Personalities : [raid1] 
md0 : active raid1 sdb[1] sdc[0]
      3907017424 blocks super 1.2 [2/2] [UU]

unused devices: <none>


    Those N/A colums will be shown because the information are only available once the filesystems are mounted.


    Greetings
    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

Participate now!

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

Register Yourself Login