Arm based system or?
Posts by LarsN
-
-
CPUs from the last 10 years are almost all amd64 (x64) based. The ram usage depends on what your needs are, so it can be from anywhere between 1GB to XX amount.
-
I would try to mount it via the terminal, to see if you can pinpoint what the problem could be.
https://linuxexpresso.wordpres…itions-in-terminal-fstab/ -
What does ifconfig say, when you run it on the host and what about dmesg?
-
I know this thread is old, but if anyone is looking for a different way to go about doing this then Duplicati is an option as well.
People are working on an Duplicati plugin for OMV. It's still in beta.
http://omv-extras.org/joomla/i…p/omv-plugins-3/3-testing (scroll down a bit) -
The plugin works fine.
As far as I understand, it uses the standard plex deb install, and puts most of the settings into the systemd script. -
sudo smbpasswd - a netz
sudo testparm
sudo reboot nowDon't type the brackets
-
I know the benchmark is nearly the same. with the i3 the investment costs are much cheaper therefore but the x265 encoding is pretty intresting for me as the Amazon Fire TV stick cannot play mi hi10p animes...therefore i thought for the G4560. But if it's still in beta...
You'll still be able to encode x265 files, just not with hardware but with software.
The i3 you looked at is also EOL in 3 months. -
The CPU performance is almost identical with passmark scores of around 5000.
The hardware encoding feature in Plex is still in beta, and not too sure if they'll ever use HW for x265 anytime soon, but I would still go with the newer hardware.
-
This folder might contain logs you can use:
/var/log. -
Has SMB worked at all for you?
I just set up a new build and have been having SMB problems too. The service shows it's online, but there's no response when I try to connect to samba.What I've done:
SSH login and run:
sudo smbpasswd -a {username}
sudo service smbd restart
sudo testparm
sudo reboot now.Change {username} to one of the usernames you want to allow SMB access to.
See if samba works now, if not check if OMV shows SMB as disabled (it did for me). If it does re-enable it and try to access your SMB share again.
-
-
First step is to check dmesg. SSH into your server and do a sudo dmsg.
It shows you the bootup and kernel errors.It might be better to ask here: https://community.wd.com/t/alt…ssie-synology-dsm6/156551
Also the first post on there talks about telnet into the device, if the device lights up red (purple) during boot.
-
The OMV3 image that is on SF does not have EFI support. If you need UEFI, you'll have to install Debian 8 manually and then install OMV3 with this guide:
Guide to install on Deb 8.x Jessie? -
thank you i will try....but this drivers work with i386 processors and i'm using a raspberry pi that has an arm processor....is it possible use them?
-
You can always download the deb directly from debian and install it manually.
Bashwget http://ftp.us.debian.org/debian/pool/main/c/curl/libcurl4-openssl-dev_7.38.0-4+deb8u5_amd64.deb dpkg -i libcurl4-openssl-dev_7.38.0-4+deb8u5_amd64.deb
It's hard to say why it fails with apt-get for you, but could be proxy related, if you're using a local deb server etc.
And Jackett is okay, but MONO apps usually consume a lot of memory and cpu overhead. There's a new app out there called Cardigann that basically does the same as Jackett.
-
What driver did you use?
This is the driver for your device:
http://www.canon.co.uk/support…ux%20(64-bit)&language=ENYou'll find a complete install guide inside the tar file (under the doc folder)
-
You can also hide files and folders you don't want samba users to see with veto files.
-
Check where you installed the database folder under the plex settings in OMV.
Then ssh into your server, cd into the folder and follow the guide here: http://forums.plex.tv/discussion/126254/rel-webtools/p1
-
It is an nginx setting. Look at this <a href="https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-links/blob/master/usr/share/openmediavault/mkconf/links#L167" class="externalURL" rel="nofollow" target="_blank">code</a>
Ah I see
But isn't this only for when building omv?
Doesn't configs in this folder:
/etc/nginx/conf.d/
get loaded by nginx?