Jump to content
XPEnology Community

jensmander

Moderator
  • Posts

    628
  • Joined

  • Last visited

  • Days Won

    32

Everything posted by jensmander

  1. The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  2. Synology announced the upcoming availability of their own enterprise hdds, from 8 to 16TB. Under the hood these are Toshiba hdds with a modified firmware. They shall gain better performance in heavy workloads and it will be possible to update the fw via DSM. The nasty things: they are much more expensive than the original Toshiba hdds (over 65%) and Synology will block other hdds of this class in their upcoming XS-series which will result in a complete vendor lock-in.
  3. The usual ones. Choose your loader (1.03b for DS3615 or DS3617, 1.04b for DS918+), create your boot stick, set up your bare-metal system with usb devices as the primary boot option, plug in your original Synology’s hdds in the new system, start it up and check which IP it received (DHCP needed in LAN). Alternative would be the Synology Assistant. Then connect to your XPenology using your browser. It will offer you migration install (keep all your data, users and apps) or a clean install. Choose the migration and usually it should work after the first reboot.
  4. If all hdds are detected within DSM, yes. 3 drives are the minimum for RAID 5.
  5. jensmander

    Hyper-V

    No, Hyper-V is not supported.
  6. It‘s only a simple pie chart summary of what each server consumes on disk space within HyperBackup‘s folder (which can be viewed with DSM‘s file explorer).
  7. jensmander

    Trip28

    2-3 Sekunden wohl eher aus dem Standby, kein richtiger cold boot. Sobald man konventionelle HDDs in einem System hat, ist die response time meist immer um einiges höher, da die erst ihren spin-up fahren müssen. Betreffend XPEnology und boot time: ja, wenn man nur SSDs verwendet geht es etwas schneller. Den timeout im Loader kannst du von 3 Sekunden (default) auf 1 Sekunde heruntersetzen, aber ob das nun der absolute Bringer ist... Wie Du die grub.cfg nachträglich bearbeiten bzw. den stick mounten kannst, ist hier beschrieben:
  8. Yes, in basic it‘s the correct way. You’ll have to reinstall DSM, install HyperBackup and restore everything with this app. Beside HyperBackup I would also make a backup from the DSM configuration from time to time.
  9. Next time be sure to read the forum rules. I moved your topic to general questions, this has nothing to do with tutorials and guides.
  10. Wrong forum section and you should be more specific in your question. I think you mean the use of Let‘s Encrypt (which is possible). Regarding the loader more informations are needed (mainboard, cpu, nic, etc.).
  11. For a R/W cache it‘s advisable to use two SSDs of the same size and model. But as @flyridesaid, the usual risks should be considered.
  12. The stick is only needed for the boot process and is not monitored. When the stick gets hot this means your mainboard is not well cooled and you should check your case, especially the cpu cooler and fan. If the cpu fan doesn’t work properly the heat is not blown away and concentraded around the socket. Usually systems shut down on temperatures above 90 degrees celsius, this would explain the improper shutdown.
  13. Solange die NAS nicht von außen erreichbar ist (Sicherheitsupdates) und keine Pakete meckern (bspw. Plex), sind die Updates kein Zwang.
  14. Did you modify this entry in the grub.cfg, maybe an unwanted line break or typo? Did you compare the appropiate line with the original grub.cfg? Any difference?
  15. Of course you can run this on original Synologys or even XPenologys. It’s a RAM test which can take many hours to complete. But for bare-metal XPenologys I would prefer the classic way with bootable tools like MemTest+ or anything similar.
  16. Wenn der B120i controller verbaut ist, muss bzw. sollte dieser auf AHCI im Bios umgestellt werden. Nicht den controller komplett deaktivieren.
  17. You could use a VPN solution or open the corresponding ports (NAT) on your firewall to your XPenology box in combination with a DDNS. Usually this would be 5000 (HTTP) or 5001 (HTTPS). But opening these ports is risky and should go along with additional security measurements.
  18. It seems that you didn’t read either the FAQ nor the forum rules.
  19. The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  20. With no output to the serial console it will be more than difficult to solve this 😕 Otherwise booting a live linux system would be the last ressort. If it’s „only“ SSL related you could try to mount the disks and exchange the certificate back to the original one located in /usr/syno/etc/certificate/system/default
  21. Since Let's Encrypt changed their API from v01 to v02 it isn't possible to request certificates when using DSM 6.1.X. Workaround: exchange the syno-letsencrypt module with a version from a DSM 6.2.X release. Preparations: enable SSH access on your box download this file (from an original DS920+, DSM 6.2.3-25426 Update 3), extract it and copy it to a shared folder of your NAS: https://mega.nz/file/889yCJ5S#Y3UtxPe_qQfRkpxQeALzsFEAIx_NDxLVx2FPLu9HT_I After you have downloaded the file mentioned open a SSH connection to your NAS Backup your current syno-letsencrypt module by sudo cp /usr/syno/sbin/syno-letsencrypt usr/syno/sbin/syno-letsencrypt.bak Copy the new syno-letsencrypt from your shared folder (for example: volume1/Downloads) to the sbin folder: sudo cp /volume1/Downloads/syno-letsencrypt /usr/syno/sbin/ Modify the file to execute it: sudo chmod 755 /usr/syno/sbin/syno-letsencrypt Open the letsencrypt.default with vi and modify it: sudo vi /usr/syno/etc.defaults/letsencrypt/letsencrypt.default Search for the string "https://acme-v01.api.letsencrypt.org/directory" Press "i" and change the 01 to 02 in this string (should be "https://acme-v02.api.letsencrypt.org/directory") To save and exit, press ESC, type :wq (ENTER) Reboot your NAS and Let's Encrypt should work again
  22. Die von Dir verwendete DSM-Version verwendet noch die 01-API von Let‘s Encrypt, welche nicht mehr unterstützt wird. Damit bleiben 2 Möglichkeiten: - Upgrade auf DSM 6.2.X - manueller Austausch des LE-Moduls via SSH Für das Upgrade von DSM gibt es hier im Forum entsprechende Anleitungen, für den Austausch des Moduls unter dieser Adresse ein HowTo: https://workit.kz/synology-dsm-6-1-xpenology-lets-encrypt-acmev1-to-acmev2/
  23. Hmmm... *glaskugelpolier*.... jaaa... ich glaube schon, dass da etwas nicht stimmt. Ein paar Informationen zu Deinem System wären hilfreich, bspw. Loader und DSM-Version. Welche Fehlermeldung erhältst Du beim Anfordern des Zertifikats? Port 80 und 443 sind im Router korrekt eingetragen beim NAT? Afaik gibt es mit älteren DSM-Versionen Probleme mit Let‘s Encrypt, da das alte Protokoll der Api nicht mehr unterstützt wird. DSM wird auf der 218+ aktueller sein?
  24. Data scrubbing is a process to detect and repair inconsistencies on the RAID. It should be performed on a regular basis but has the drawback of performance decrease (as you could see).
  25. Hm, one of SHR‘s drawbacks compared to classic RAID modes. But good to hear it’s not a dead drive or anything else like that 🙂
×
×
  • Create New...