jensmander

Yes, this might help. - Launch CMD as Admin with stick attached - run: diskpart - run: list disk - check the disk number of your stick - run: select disk <number of your stick> - run: clean - run: exit Check if it’s working with the HP tool after this. If not repeat the steps above and add these steps after „clean“: - run: create partition primary - run: active - run: format fs=fat32 quick - run: assign - run: exit

An affordable entry switch. As you said, you‘ll have to use SFP. I think that’s a thing which most (power) home users don’t have in their environment. But it would be a good addition to small racks or places where maybe two or more „servers“ sit together. Many newer (small budget middle class) switches have one or two SFP ports which can be used for uplinking.

Does your NIC indicate any activity when the system boots? If not then it’s not recognized by the drivers.

Schau mal in die Update Report Threads. Darin finden sich Angaben zu Board/Cpu/Nic usw. Die meisten Boards neuerer Bauart funktionieren, meist hapert es nur an den onboard Nics.

Bei solch einem alten Chipsatz offenbar nicht. Wahrscheinlich sitzt ein Intel P4x auf dem Board, dessen Southbridge schlichtweg nicht voll kompatibel ist, da bereits über 10 Jahre alt. Mit anderen Distros wie OpenMediaVault könnte es vielleicht besser klappen, da Debian eine umfassendere Treiberunterstützung mit sich bringt.

Yes, always advisable. You can choose your current setup/hardware with a simple procedure: - shut down Xpenology - unplug all HDDs/SSDs - insert a (small) unused HDD/SSD and plug in the cables - start your system with your current boot stick and install DSM on the test drive - reboot, set up the necessary features (user, password) and install (if an older pat file has been used) the newest update - if everything is still working after the reboot (especially the network) you‘re almost safe to update your production system - shut down the system, unplug the test drive, reconnect your HDDs/SSDs and proceed

The TS mentioned that his bootloader is bricked. This means that the NAS can not boot the normal way. @perroloko: afaik you‘ll have to do some „engineering“ on the flash module. The image is in the PAT file which can be extracted (PAT files are similar to TAR). Take a closer look on this thread: https://community.synology.com/enu/forum/17/post/69287

To be sure I would change the serial in the grub.cfg too. In my test the original Synology 918+ never had any issues after this.

You can assign a drive letter to the first partition of your boot stick with freeware tools. One of it is the MiniTool Partition Wizard (look at the thread Xpenology Tool for Windows...). Start the tool, right click on the first partition of your stick and choose „assign drive letter“. After that click on „apply“ on the upper left menu. Now you can browse into the grub folder, open, edit and save your grub.cfg. Once you‘re done go back to the Partition Wizard, right click the first partition, „assign drive letter“ -> none and apply. No rocket science 🙂

I made a test with a real 918+ I bought and a Xpenology (flashed the MACs to an Intel dual port NIC, serial and same MACs in grub.cfg). Only one system was online, never both of them. At first I could login to my Synology account within DSM on the Xpenology, but didn’t activate QC. Shut down the system and started the real 918+ for the first time. After a few hours I shut it down, powered on the Xpenology box and after that I couldn’t login to my Synology account within DSM anymore (login window displays a spinning circle forever). The same happened with a DS3615. So I think there are many ways for Synology to keep an eye on „fake“ boxes beside serial numbers and MACs.

Afaik the Z400 series supports UEFI even on older models. And most of them have the Intel AMT onboard (useful for remote power cycling/reset, etc.).

If you‘ve disabled the built-in admin account then it’s obvious why the SynoAssistant can’t connect/login. What do you mean by „new base IP“? Is it only a different IP or a different subnet? Subnet means the typical 192.168.xxx.yyy for private networks. If you’re on the same subnet as before then you should be able to login into DSM by entering the IP address of your Xpenology box in the browser‘s address bar. Afaik the SynoAssistant scans only the subnet you’re in and doesn’t hop or search other networks. However - if you’re on a different subnet now you should assign a static IP of your old subnet to your PC, login to DSM and change the IP according to the new subnet. For example: Old subnet: 192.168.0.0/24 New subnet: 192.168.10.0/24 If your Xpenology had 192.168.0.123 as the old address then you can change it to 192.168.10.123. This is only an example. Check on which subnet you are and which IP (last three digits) can be used/is free.

Yep. For apps like Video Station/Moments/Photostation a valid combo is required for video conversions and thumbnail creation.

I doubt that you can use a Rackstation as an expansion device. The expansion units have different boards inside the case which have nothing to do with the normal mainboards. You can think about iSCSI/LUNs in combination of Xpenology <> RS812.

Bei echten Servern solltest Du schauen, dass ein „it mode“-kompatibler Controller verbaut ist. Zwar werden einige RAID Controller erkannt, es empfiehlt sich jedoch der Einsatz von HDDs im AHCI Modus bzw. 1:1 Passthrough durch Host Bus Adapter. Einige RAID Controller mit LSI Chipsatz lassen sich in den besagten IT Mode flashen und agieren dann als HBA. Die NICs sollten neben der CPU (je nach gewünschtem Loader) natürlich auch passen, dann sollte alles klappen.

Hm and why not the Synology chat? It has some useful features and (together with emotions and hashtags, screenshots, etc.) some kind of „social media“ touch. It can be backed up with HyperBackup regular and is relatively good maintained.

1st) It‘s not necessary to double post the same question in different sections. You already asked this question here: Once you opened a thread you should wait until someone can give you an answer. Please read the forum rules and FAQ @Polanskiman set up. 2nd) There are some XMPP packages available in the synocommunity. But most of them are relatively old or do not provide click and run functionality. I doubt that you can achieve something simple in comparison to widely spread messengers like the one from FB. Another problem: a simple and available client for desktops and smartphones. And the willingness of your contacts to install and use it. In the end you have to rely on a web based solution which is usually not widely accepted by users. You could search the Docker repos for an appropriate solution, like prosody.

DSM creates a single system partition on every drive which is attached (except for external usb devices). This applies to bare-metal and virtual systems. You can assign all vmdks or real drives (passthrough) before the installation.

You're welcome ☺️

If you don’t allow VPN clients to access the network of your Synology (backup) site then you don’t have to care about subnets as the VPN network is usually different to the typical private subnets (10.x.x.x for VPN while most private networks use 192.168.x.x or 172...). You can’t use the VPN connection of Xpenology box1 for Xpenology box2 (and it makes no real sense to do that). Just setup the VPN connection on both Xpenology boxes. If you use HyperBackup or rsync you have to enter the IP of your Synology’s VPN server as the target (10.0.6.1 for example).

It's not a rocket science using VPN on both XPEnologys for this. Setup would be in short: - create or register a DDNS on your router on the "backup location" (if it's not capable of DDNS you can use DDNS on your real Synology) - for OpenVPN create a port forwarding rule (NAT) for port 1194 UDP on your router to the Synology - install the VPN Server package on the Synology - activate OpenVPN and (if desired) change the values for max. connections, etc. (can be left as it is) - in the VPN Server app choose which user has access to it (Priviliges) - be sure to activate "automatic blocking" - in the OpenVPN section export the config files - open the exported ZIP and extract the files, edit the "VPNConfig.ovpn" with notepad or notepad++ and edit the line "remote YOUR_SERVER_IP 1194" - replace YOUR_SERVER_IP with the registered DDNS name, save the file - now back in your XPEnologys go to the control panel -> Network -> Network connections -> Create -> VPN profile - choose OpenVPN (import via ...) - enter a name for the connection, the username and his password of the real Synology who has the privilege to connect and upload both the VPNConfig.ovpn and the ca.crt from your real box - activate the option to reconnect and finish it Repeat the last four steps on your second XPEnology and you're good to go 🙂

Hm in matters of legal things - not really a problem. But you would use Synology’s relay service. I found it rather slower than a direct VPN connection. I have 4 real Synology boxes (211, 1019, 3615 and a RS3617RPxs) on three different locations. I received fastest rsync and HyperBackup speeds with site to site IPSec (pfSense <> pfSense and OPNSense <> OPNSense routers), followed by OpenVPN connections (one OpenVPN on a SoftEther server, second one on a Synology VPN server while SoftEther was slightly faster). Compared to site to site QuickConnect dropped around 25-30% in speed.

Depends on what your goal is. Do you want a simple solution for a secure connection: internet -> your nas? Then you can install and use the VPN Server on DSM. But this requires DDNS and port forwarding (NAT) from your router to your Nas. Your router is capable to port forward, found here: https://portforward.com/icotera/i5800/ (skip to step 2) But I couldn’t find anything about DYNDNS. This leaves you with 3 options: 1) request a static ip from your provider 2) try to setup DDNS in DSM 3) you could use a Docker image, Raspberry or VM with „SoftEther VPN“ which is a free and powerful VPN with an integrated DYNDNS Or 4): get rid of your ISP‘s router and use your own hardware (if this is supported by your ISP)

You could try a „dirty“ workaround. Connect the second Nic (static ip or dhcp) and open jdownloader. In the advanced settings search for „custom proxy list“ and enter this (code between the ***, I‘m on mobile and the quote function is a pain): *** [ { "proxy" : { "address" : "eth1", "type" : "DIRECT" }, "rangeRequestsSupported" : true, "enabled" : true }, { "proxy" : { "type" : "NONE" }, "rangeRequestsSupported" : true, "filter" : { "type" : "WHITELIST", "entries" : [ ".*?jdownloader.org", ".*?appwork.org" ] }, "reconnectSupported" : true, "enabled" : true } ] *** eth1 in line 3 is your second Nic.

So all of your internet traffic is routed through the VPN? If you want the VPN only on your NAS you can create a VPN profile in DSM for your provider and set it as default gateway. The second thing is enabling DDNS on your router, not the NAS. So if you connect from the outside your router will handle the NAT and DDNS updates are updated correctly. If you enable DDNS on a device which uses VPN your DSL/cable IP will not be reachable from the outside since DDNS will point to your VPN IP.