• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by jensmander

  1. X1 Slot und Dual-Port wird schwierig. Da gibts meistens nur Exoten, Chinakarten mit Intel-Chip. Ob die dann wirklich laufen... Aber die CT geht eigentlich immer.
  2. „Beide“? 😂 Schizo bin ich noch nicht 😋
  3. Uuuh... PPTP - the weakest VPN solution. I would rather setup the VPN-Server package in DSM and use OpenVPN. It‘s no miracle and much more secure than PPTP. Only thing to do on your router is to open the corresponding port (usually 1194 UDP) for DSM (NAT rule/port forwarding). You can decide if users can connect only to the NAS or the entire subnet.
  4. This was questioned several times. In theory: everything is possible. But why should somebody invest many, many hours of work and reverse engineering to bring XPEnology to life on such low-end systems without S-ATA connections, reliable Gbit NIC speeds, USB 3.0 and low-cpu features? Use RPi as a DLNA? There are several good working OOTB solutions (LibreElec/Kodi, etc.).
  5. Kommt auf Deine Hardware an, zu der Du nichts geschrieben hast. Ab Haswell CPUs ist der 1.04b lauffähig, für ältere Hardware der 1.03b.
  6. Afaik Plex stores it‘s meta files in it‘s own folder. I have the same setup on a bare-metal machine and it runs without problems.
  7. Hm, die CT sollte eigentlich laufen. Es gibt seltene Mainboard/Chipset Kombos, wo C1E im BIOS trotzdem aktiviert sein muss, um die Karten für DSM erkennbar zu machen. Eine Alternative ist die i340-t2. Dual Port, gebraucht für ca. 25€.
  8. Yes, I would install the last update to 5055 and then continue with the upgrade. Some users had problems with the direct update to 5.2-5967 and the best solution was the manual one by one upgrade. Reverting back a bricked system in case of failure will take more time than install some updates 🙂
  9. First check if DSM 5.1 is on the latest patch level. Then create a boot stick for DSM 5.2. Be sure to include things like MAC address from your old stick. Boot with the new stick and check if the system comes up. If it does you should download and install all updates for DSM 5.2 manually one after another. Don’t use the automatic update function. If 5.2 is fully updated you can follow polanskiman‘s tutorial to upgrade to 6.1 and after that to 6.2. If possible backup your data and your system config before any upgrade.
  10. It‘s also possible that the Synology Assistant needs another search run. I encountered this several times. Had to run another search once the program had opened. And be sure to allow firewall access for the assistant.
  11. Shutdown DSM, plug in the boot stick to your workstation, start MiniTool Partition Wizard Free (or a similar software), assign a drive letter to the first partition of the stick. Then open the grub.cfg and modify the serial and/or MAC. Save your changes, go back to your partition software and unassign the drive letter from the stick. A serial and MAC from a DS115j won't work for other Synology models (AFAIK). You'll have to do a short google search for images of a DS36XX or DS918+, depending on your loader... ;)
  12. jensmander

    USB stick

    Unlike HDDs there is no frequent access on the stick. And it has no mechanical parts like a spinning HDD. So it's unlikely that your stick will take any damage when the system is switched on or off.
  13. Migration is the safe way to keep your data. But don’t let it download the newest DSM version from Synology. Use the PAT linked in the forum.
  14. If you have a spare HDD left try a fresh install only on this drive with your current stick and see if it‘s coming up again after the first reboot. If it works you can shut down the system, add the old drives and power it on again.
  15. I doubt that the loader/DSM will recognize the controller. I would also stay with soft RAID whenever possible. The usual low-end controllers have no benefits. There are several drawbacks compared to soft RAID: - DSM will not be able to detect failing drives - if your controller dies you’ll have to find and buy a compatible spare part to regain access to the RAID - you’ll have no speed advantages A soft RAID can be mounted in any other Linux system in case of failure. Unless you‘re not playing around with large ssd arrays including an adequate controller (like Avago‘s 9361-8i for example) you‘re doing yourself not a favor. Just my 2 cents.
  16. You can use an external drive for HyperBackup but it must be large enough. Usually the individual user storage setups are much larger than the typical usb hdd. So that would lead to the solution @flyride mentioned above: an additional system for backups (either another Xpenology or an rsync compatible system like OpenMediaVault etc.). A backup or copy of your current usb boot stick (or the synoboot.img you modified) and regulary backups of the system configuration (can be done from Dsm‘s control panel) are an additional step. A simple approach for testing updates would be a separate hdd/ssd. Install the current stable and working version for your system on it and in case of an update thought just use only this drive and disconnect the current drives (as mentioned before in your other thread). So you could play around with the update and see if it works. Unfortunately there is no simple out of the box one-click solution for Xpenology.
  17. A new usb drive won‘t help because of DSM‘s system partitions on each hdd which contain the „new“ system. There are several methods to get back in business. 1st) Boot a live linux, mount the raid and try to modify the text file which contains the version info (you‘ll have to search the forum for the exact name and path). 2nd) Disconnect all hdds, connect a new one, install the older version of DSM on it, shut down the system, reconnect the old drives and start it again. DSM should recognize the old RAID. 3rd) Hardcore method: delete each system partition (first partition) and reinstall DSM after that. Normally DSM should recognize the RAID array after the initial setup but with no warranty. In case of 2 & 3 all your settings will be lost.
  18. Try to wipe the vdisks and start over. Error 35 usually occurs if there‘s a partition layout which can‘t be deleted.
  19. DSM‘s firewall is disabled by default. Did you define any custom HTTPS ports? Or just the standard setup? I‘m not familiar with EdgeRouters but several NAT errors consist of improper rules. Did you try to use <your-ddns-address>:9901 in DS Cam or just the ddns-address/external IP?
  20. With such equipment I would use a Hypervisor. Would make more sense. You‘ll have enough power to run Dsm along with other VMs. I have a similar system with Dsm, 4x Win10, 5x Debian and one W2019 nano.
  21. I don’t know if it works ootb with 1.02b but you won’t be able to use the 1.02b with DSM 6.2 (or I missed something). Usually Mellanox cards of this series are supported by Synology.
  22. Should work as any other network card but it depends on the model and if it’s supported by the built-in drivers.
  23. Afaik this card is supported without extra drivers with 1.03b and 1.04b.
  24. I had a similar setup in a bare-metal system. Before I could expand the storage pool the SSD cache had to be removed. Otherwise DSM threw up an error.
  25. Did you unmount the SSD Cache before you added the new hdd?