Need some help, I'm a bit out of my depth

  • If you have a "pure" Linux network, then chances are that you want to use NFS. But then you most likely have no NTFS hard drives at all.


    NTFS is a proprietary Microsoft filesystem. Microsoft keeps the internals of NTFS a secret for business reasons. NTFS has been partially reversed engineered so it can be partially used in Linux, but performance may be bad and NTFS works very different from how "normal" Linux filesystems work. Some tools in Linux have problems working with NTFS. Like NFS and OMV.


    I think you can use NFS with NTFS, but only if you use Microsoft software. A form of feeble vendor lock-in.


    NFS, SMB and Linux filesystems are all Open Source. The internals are not kept secret. This means that they usually work together very well. For instance OMV has very good support for NFS, SMB and Linux filesystems like EXT4, BTRFS and others. But OMV does only have partial support for NTFS.


    Most of us have a mixed network. Perhaps a Linux based NAS running OMV and various clients running macOS, iOS, Android, Windows or Linux. Some of these can handle NFS. But all can handle SMB. So SMB is the most commonly used network filesystem in mixed environments.


    I use NFS between my Linux servers and computers. Because it is efficient and beautiful. It works like an extension of a Linux filesystem to the network.


    I also use SMB. It is necessary for Android and Windows clients. I think SMB is ugly and slow. But it works.


    So the pragmatic thing is to accept that SMB is the general standard network filesystem. And use it.


    And the pragmatic thing is to accept that NTFS doesn't work good with Linux and OMV and use EXT4 or BTRFS instead.

    Be smart - be lazy. Clone your rootfs.
    OMV 5: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

  • Macom, it's your 'Getting Started OMV 5' that i'm using. I'm half way down page 46, all OK so far. But then nothing appears in Network. At the top of the next page there's a link to follow if the share doesn't appear in Windows 10 which leads to a pdf call HOWTO-ConnectWin10toOMV. This guide starts talking about HomeGroup connections, these are not anywhere to be seen on my PC and I think Microsoft has now removed HomeGroup.

  • OK. New Question :):)


    Can I use OMV to copy files? I've remembered that I've got a couple of 2TB drives that used to be in someone's server. The PC running OMV has got enough connectors on the power supply to let me plug in up to 4 drives. If I attach one of these 2TB drives, wipe it and format it to ext4 then is there a way to copy all the data off the NFTS drive onto this new drive within OMV?

  • In the OMV5 instructions there's a bit I didn't understand so I didn't do it.


    It says i386/amd64 users (which I believe I am) it says to assign a static IP address to the new OMV server that is outside the range of my network's DHCP server


    I have no idea what my network's DHCP server is or how I find out what it's range is.


    I've also not got much idea about DNSSEC, Anycast or Netmask

  • Static IP is optional and even not recommended by some users.


    Instead you can tell your router to always give the same IP to your server. Or you just don't care about the IP and use the host name instead.


    If the host name of your server is "openmediavault" you can access it by


    openmediavault.local instead of the IP

  • Right, OK. (After a bit of googling I think my broadband router is my DHCP server - but not too important at the mo).


    New problem: I did have a problem installing some of the updates so I'd left them. Now when I go into Update Management all the uninstalled updates have disappeared and clicking on Check gives me a loooong error message.


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1' with exit code '100': Get:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Get:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:5 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Get:6 http://deb.debian.org/debian buster InRelease [122 kB] Get:7 http://linux.teamviewer.com/deb stable InRelease [9388 B] Ign:8 https://download.docker.com/linux/debian buster InRelease Get:9 http://httpredir.debian.org/debian buster-backports InRelease [46.7 kB] Ign:10 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease Get:11 http://packages.openmediavault.org/public usul InRelease [12.7 kB] Err:12 https://download.docker.com/linux/debian buster Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 13.224.239.84 443] Get:13 http://deb.debian.org/debian buster-updates InRelease [49.3 kB] Ign:14 https://dl.bintray.com/openmed…n-developers/usul-testing buster InRelease Get:15 https://openmediavault.github.io/packages usul InRelease [12.7 kB] Ign:16 https://dl.bintray.com/openmed…in-developers/usul-extras buster InRelease Err:17 https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 52.28.187.224 443] Err:18 https://dl.bintray.com/openmed…n-developers/usul-testing buster Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 52.28.187.224 443] Err:19 https://dl.bintray.com/openmed…in-developers/usul-extras buster Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 52.28.187.224 443] Reading package lists... E: The repository 'https://download.docker.com/linux/debian buster Release' does not have a Release file. E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release' does not have a Release file. E: Release file for http://security.debian.org/deb…/buster/updates/InRelease is not valid yet (invalid for another 415d 7h 4min 49s). Updates for this repository will not be applied. E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/usul-testing buster Release' does not have a Release file. E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/usul-extras buster Release' does not have a Release file. E: Release file for http://deb.debian.org/debian/dists/buster/InRelease is not valid yet (invalid for another 359d 0h 15min 32s). Updates for this repository will not be applied. E: Release file for http://linux.teamviewer.com/deb/dists/stable/InRelease is not valid yet (invalid for another 403d 22h 8min 14s). Updates for this repository will not be applied. E: Release file for http://httpredir.debian.org/de…uster-backports/InRelease is not valid yet (invalid for another 415d 15h 31min 27s). Updates for this repository will not be applied. E: Release file for http://packages.openmediavault…blic/dists/usul/InRelease is not valid yet (invalid for another 408d 7h 42min 25s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 415d 15h 31min 26s). Updates for this repository will not be applied. E: Release file for https://openmediavault.github.…ages/dists/usul/InRelease is not valid yet (invalid for another 408d 7h 42min 24s). Updates for this repository will not be applied.

  • Ah right. It said it was 14th Feb 2019. I did set the date/time myself on initial setup, but then I'm sure I had enabled NTP server. I wonder how I turned it off.


    Maybe it's been wrong for ages, that's why the updates wouldn't install.

  • OK. So I've put both of the other 2TB disks in, wiped them and set them up as EXT4 file systems and mounted them both.


    I've created a shared file on one, gone into Rsync and following the instructions in Rsync the Openmediavault Way: Sync Everything

    video.


    I've run the job and I get :

    Please wait, syncing </srv/dev-disk-by-label-TerrorData/TerrorData/> to </srv/dev-disk-by-label-covid19/BamBamcopy/> ...


    sending incremental file list


    sent 40 bytes received 12 bytes 104.00 bytes/sec

    total size is 0 speedup is 0.00


    The synchronisation has completed successfully.

    Done ...


    So, it doesn't look like it's copied anything. I'm stuck again.

  • /srv/dev-disk-by-label-TerrorData/TerrorData/

    I assume this is the source. The drive has the label "TerrorData" and then you have a folder on that drive called "TerrorData". Is that correct?

    Are there any data in that folder?

Participate now!

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