create raid 1 on a blank disk, copy from a drive and grow the raid

    Quote from geaves

    The mdadm reference md0 md1 md127 doesn't matter, if you want to run your command, which you have obviously found from elsewhere, then run the commands I have provided that is up to you.

    ok, just for curiosity, is no more possible change 127 to 0?

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    • Official Post
    Quote from n1tr0usOx1d3

    ok, just for curiosity, is no more possible change 127 to 0

    Never tried it, and my understanding of it I posted earlier, I've had users whose mdadm reference has changed and it still works, so if want to try your command that's up to you.


    As I said the only reason it changed was because of a reboot and it wasn't set initially

    ok, I have executed the 2 commands, after reboot I have md0. I have tried "cp -aR /dev/sda/* /dev/md0" but output is always the same "zsh: no matches found: /dev/sda/*". What I wrong?

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    • Official Post
    Quote from n1tr0usOx1d3

    What I wrong

    TBH I don't know I've never used it, that's why I referred you to rsync instead but that requires the UUID of the drive, another option is to install Midnight Commander apt install mc then from the cli type mc, it's a file manager

    Quote from n1tr0usOx1d3

    cp -aR /dev/sda/* /dev/md0

    Maybe I'm dumb but does the cp command works on DEV????


    Shouldn't it be the /<mountpoint>?????



    linux cp command syntax at DuckDuckGo

    Quote from n1tr0usOx1d3

    Isn't dev the mountpoint?

    No, that's the device position.

    You need to read more about Linux and how it works:

    what is linux mount point - Google Suche


    To see the mountpoints, run:

    cat /etc/fstab

    lsblk


    To name a few

    Quote from macom

    n1tr0usOx1d3 please reconsider if you need RAID. It is adding an additional layer of complexity. Keep it simple, stupid.

    ok, I'm seriously thinking to make it simple... I have format in ext4 the sda2 drive at first post that now is called sdb1.... Should I run the following command to automount at boot to avoid the same issue for the raid procedure?


    omv-salt deploy run mdadm then

    update-initramfs -u


    p.s.: In the image above after 10637 / 44713 no more progress values are showed but only orizzontal scroll bar is moving... is format process ok? Seems that it has ended without errors after writing superblocks section (even in that case progress values have not reached the max value showed on interface)


    inodetables.png

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    or instead of omv-salt deploy run mdadm should replace another command to mdm considering that mdadm is for raid e nott for single disk?

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    • Official Post
    Quote from n1tr0usOx1d3

    or instead of omv-salt deploy run mdadm should replace another command to mdm considering that mdadm is for raid e nott for single disk?

    You don't have to do anything that command is simply to create an mdadm conf file, you also don't need the other command

    a little offtopic: add checksum field to ext4 system is sure running command tune2fs -O metadata_csum ?


    mkfs -O ^64bit,^metadata_csum -t ext4 in 2019
    Thomas Krenn recommends creating ext4 partitions like: https://www.thomas-krenn.com/de/wiki/FSCK_Best_Practices mkfs -O ^64bit,^metadata_csum -t ext4 what…
    serverfault.com

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    I'm interesting to this feature to be secure that files will not corrupted, I ve run tune2fs -l /dev/sdb1 | grep 'Filesystem features' and both file system features "64 bi"t and "metadata_csum" are present... "metadata_csum" work only for system files or for all files? how can I read the crc saved in file system to compare to crc that I'll get from reading files?

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    ok here I have found what I'm searching https://github.com/rfjakob/cshatag ... to do it, I should mount filesystem with option "user_xattr" enabled. After made a research, I have found this https://docs.openmediavault.or…/various/fs_env_vars.html and, running "omv-env get OMV_FSTAB_MNTOPS_EXT4" no values are showed.... my /etc/openmediavault/config.xml file include "user_xattr". Can I run "omv-salt deploy run fstab" or can encounter some issues?


    Another question: now I don't have choose nothing, to remove array and use the unit under mdadm as simple unit how can I do?

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    • Official Post

    The reason you have no response is because no one has any idea what you are doing at present, we have gone from creating a raid1 with one disk, which you seem to have started, to using one disk, then you start referring to external sites.


    Let's make one thing clear you either want our help or you don't, if we don't reference external sites that is because they are not necessary, but to come here and reference external sites means you really have no idea what you are doing.

    Quote from geaves

    The reason you have no response is because no one has any idea what you are doing at present, we have gone from creating a raid1 with one disk, which you seem to have started, to using one disk, then you start referring to external sites.


    Let's make one thing clear you either want our help or you don't, if we don't reference external sites that is because they are not necessary, but to come here and reference external sites means you really have no idea what you are doing.

    ok, You're right... I have think that, considering the hardware, I can add a box with some bays so some hdd are most time turned off and other are always turned on inside helios hardware. I turn on hdds in the box periodly only to make backup. However, when I write new files on the hard disk always turned on, I want be sure that there don't copy data damaged caused by a disk failure... so I have found cshatag utility and "user_xattr" option for ext4 file system because I don't want use btrfs and zfs.

    omv 6.1.5-2 (Shaitan) | arm v64 | Helios64 | 5.15.89-rockchip64 kernel

    • Official Post
    Quote from n1tr0usOx1d3

    so I have found cshatag utility and "user_xattr" option for ext4 file system

    ?( what is that!! that has nothing to do with OMV that is already added to a mounted file system on OMV


    OK I'm out of this thread, good luck with whatever you are trying to do

Participate now!

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

Register Yourself Login