Posts by n1tr0usOx1d3
-
-
Hi, I have a similar problem of willowen100 , but my hard disk are connected to sata port (2 unit WD60EFRX with hardware in my signature) . The script here https://dn.odroid.com/5422/script/odroid.shutdown will continue to work or not?
-
Since you don't post what I ask, I give up.
Good luck.
sudo omv-showkey fstab
<fstab>
<!--
<mntent>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid >
<fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxx x-xxxx|/dev/xxx</fsname>
<dir>/xxx/yyy/zzz</dir>
<type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|.. .</type>
<opts></opts>
<freq>0</freq>
<passno>0|1|2</passno>
<hidden>0|1</hidden>
</mntent>
-->
<mntent>
<uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
<fsname>/dev/mmcblk0p1</fsname>
<dir>/</dir>
<type>ext4</type>
<opts>noatime,nodiratime,defaults,commit=600,errors=remount-ro</opts>
<freq>0</freq>
<passno>1</passno>
<hidden>1</hidden>
<comment></comment>
<usagewarnthreshold>85</usagewarnthreshold>
</mntent>
<mntent>
<uuid>b667270f-7c02-4f41-9ba0-2c1382ea9d9c</uuid>
<fsname>/dev/disk/by-uuid/27e56c23-d740-4314-b3c3-64e56b4d2421</fsname>
<dir>/srv/dev-disk-by-uuid-27e56c23-d740-4314-b3c3-64e56b4d2421</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<usagewarnthreshold>95</usagewarnthreshold>
<comment>RAID WD60EFRX</comment>
</mntent>
<mntent>
<uuid>2bfe9a24-8f24-4d3d-beca-99c6382762f2</uuid>
<fsname>/dev/disk/by-uuid/3b033dfa-6362-444c-943e-c7615ab68e80</fsname>
<dir>/srv/dev-disk-by-uuid-3b033dfa-6362-444c-943e-c7615ab68e80</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota. group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<usagewarnthreshold>95</usagewarnthreshold>
<comment></comment>
</mntent>
</fstab>
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 5.5T 0 disk
└─md0 9:0 0 5.5T 0 raid1 /srv/dev-disk-by-uuid-27e56c23-d740-4314-b3c3-64e56b4d2421
sdb 8:16 0 5.5T 0 disk
└─sdb1 8:17 0 5.5T 0 part /srv/dev-disk-by-uuid-3b033dfa-6362-444c-943e-c7615ab68e80
mmcblk1 179:0 0 14.6G 0 disk
mmcblk1boot0 179:32 0 4M 1 disk
mmcblk1boot1 179:64 0 4M 1 disk
mmcblk0 179:96 0 29.7G 0 disk
└─mmcblk0p1 179:97 0 29.4G 0 part /
n1tr0usOx1d3 It was joke on your "nitrous oxide" name, but not at your expense. But perhaps that was lost in translation.
You must admit there's been many twists and turns in your saga, making it very hard to follow.
Haven't you been told that OMV6 creates ext4 filesystems with ""user_xattr" already set? You can see that in 3 ways in OMV6.
1. contents of the file /etc/mke2fs.conf
2. contents of /etc/fstab
3. the output of a command like "cat /proc/fs/ext4/sda1/options | grep xattr"
I really don't why you are messing around with ENV VARIABLES or config.xml. By the way results of "omv-env get .... " are blank unless the specific env variable has been set by a OMV user.
ok, all 3 method conferm that user_xattr is setted... so, there doesn't be issue compiling and running cshatag
-
sudo omv-showkey fstab
lsblk
And what do you want to do with that attribute "user_xattr"? Add it to the options of the drive on fstab?
if I run sudo omv-showkey fstab it's present in opts xml element, with tune2fs -l /dev/sdb1 | grep 'Filesystem features', lsblk and cat /proc/mounts it's no showed ... even omv-env get OMV_FSTAB_MNTOPS_EXT4 don't show any value
-
copy off
reconfigure
copy on
You can't convert to a single drive without wiping the drive.
ok
-
I'll only reply to:
This command will remake the file /etc/fstab with the info taken from the /etc/openmediavault/config.xml
If you edited fstab, it will be overwritten.
If you changed anything on the <mntent> sections of the config.xml, they will be passed onto fstab.
Be VERY CAREFULL with what you change.
You can leave your system crippled and, even not able to boot.
The "Rule-OF-THUMB" is to make a backup copy of config.xml PRIOR to any editing on it.
ok, problem is that here https://docs.openmediavault.org/en/6.x/various/advset.html is write that to read env variables should run "omv-env get <VARIABLE_NAME>" where VARIABLE_NAME that interest me is "OMV_FSTAB_MNTOPS_EXT4" taken from here https://docs.openmediavault.or…/various/fs_env_vars.html. Running "omv-env get OMV_FSTAB_MNTOPS_EXT4" no values are showed, moreover running "tune2fs -l /dev/sdb1 | grep 'Filesystem features'" the feature "user_xattr" is not present even if it's present in /etc/openmediavault/config.xml file. I don't have any change in config.xml file, but however I want to be sure that running "omv-salt deploy run fstab" system will not be crippled.
very happy to make laugh to You, but making backup as suggested in the first post and using as main device one of the 2 disk, the other disk however will be turn on and however, as all mechanical hard disks, will increase cycle count even if his scope was backup only and not main use. So consider that however will be in function, then was better make raid. After I have think about the box to link to usb port that can be turned on only for backup scope, then I have choose to don't make raid and make simple backup adding, if possible, the silent data corruption check to ext4 file system so that, for each backup, immediately it's possible notify issue.
-
Stop spamming this thread with external links, please.
What you're trying to achieve is outside OMVs scope.
Just format the drives with btrfs and create subvolumes and use SNAPPER.
Either search the web or see my signature for some links.
Or just have a 3-2-1 backup and you will always have a failsafe copy of DATA
ok no more external links, just 2 things (I don't want use btrfs and I can't use zfs):
1. Can I encounter some issues running "omv-salt deploy run fstab"?
2. if I want remove array and use the only single unit actually in the raid (named md0) as simple disk what command I should use?
-
geaves here about silent data corruption
Silent data corruption really is real.2 months ago I ran cshatag [1] on around 500GiBs of data. Today I rsync'd it to a new drive and re-ran cshatag. I was shocked to discover 31 files...www.reddit.comHow to detect silent data corruption?Aside of filesystems like btrfs, ReFS or ZFS, are there any filesystem independent tools that can be used to detect silent data corruption or...www.reddit.com -
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
it's a way to save checksum of a file in the filesystem to detect silent data corruption in case of disk failure.
I have told what I' tryng to do: backup to other disks and save checksum inside filesystem. OMV can be configured adding user_xattr . It's just add an external utility for the checksum calculating, verifyng and store inside filesystem
-
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.
-
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?
-
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?
-
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 2019Thomas 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 -
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?
-
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)
-
Maybe I'm dumb but does the cp command works on DEV????
Shouldn't it be the /<mountpoint>?????
Isn't dev the mountpoint? if I have /dev/sda, at startup should be done the mount operation, true?
-
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?
-
I have found this tut https://delightlylinux.wordpre…-a-raid-array-with-mdadm/
but I don't know if I'm using an updated version of mdadm and can wrong something...moreover my mdadm.conf doesn't contain nothing under "# definitions of existing MD arrays".
I'll execute Your commands and see what does it happen
-
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?
-
running "mdadm --detail --scan --verbose" I'll get
ARRAY /dev/md/helios64:0 level=raid1 num-devices=1 metadata=1.2 name=helios64:0 UUID=cb884964:44860d40:ac28e0fc:89d0abb4
devices=/dev/sda