• Content Count

  • Joined

  • Last visited

  • Days Won


haydibe last won the day on December 3 2018

haydibe had the most liked content!

Community Reputation

10 Good

About haydibe

  • Rank
    Super Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Do you have a KVM based VPS? Can you modify the KVM settings of your VPS? If so, the approach might be similar to Promox installation?
  2. haydibe

    Sicherheitslücke Umgang ?

    Wie kommst Du zu der Fragestellung? Wenn ich mir https://www.synology.com/en-global/security/advisory/Synology_SA_18_62#md-content ansehe, dann gibt es Fixes folgende Versionen: Upgrade to 6.2.1-23824-4 or above. Upgrade to 6.1.7-15284-3 or above. Upgrade to 5.2-5967-9 or above. Sollte Dein NAS über das Internet erreichbar sein, würde ich sofort update. Wenn das was über das Internet erreichbar ist in Docker-Containern oder VMs läuft, dann würde ich das update nicht als zwingend ansehen. Bevor ich update schau ich immer in die Update-Rückmeldungen für meine Betriebsplattform an.. Je nach Rückmeldungen (mehrzahl positiv? Hinweise zu erfolgreichem Update trotz Schwierigkeiten?) update ich oder eben nicht,
  3. haydibe

    Future for HP microservers?

    Ikea of computing 🤣 Actually, the fans spin quite slow and are barely noticable. If you WANT you can add more. You don't have to. I must admit I want my WD Red hard disks properly cooled. Also the harddisks are the main source of noise. Especialy when beeing accessed. Unless you don't go full SSD (Samsung PM1643 for instance) or NVME, that's something you have to live with.
  4. haydibe

    Unterschied zwischen 3615 und 3617xs

    Ich hab mir mir die module in DSM6.2.1 angesehen: Die igb.ko ist in beiden pat-Dateien enthalten und auch in etwa gleich groß. Bei einigen Treibern ist die 3615sx Variante deutlich größer, als die vom 3617sx, bspw. ist e1000e.ko fast 100kb größer. Der mpt3sas.ko Treiber steckt mitlerweile auch nur noch im 3617sx, aus meiner Erinnerung war das mal anders.
  5. haydibe

    Future for HP microservers?

    I can highly recomend to buy a dell t30 and change the case to Fractal Design Node 804 (due to dell pin headers some tinkering is involved). It commes with a okayish Xeon 1225-v5 CPU (capable of Hardware transcoding ;), which can be easily upgraded to a more powerfull model if required. If you try to upgrade the CPU with any non low voltage XEON version, you will have to modify a cpu heatsink as the messurements of the mounts on the mainboard are "special".
  6. haydibe

    Future for HP microservers?

    I am running two HP MS Gen8 with DSM6.2.1 update4 on ESXi6.7. Without an additional NIC, though I had to change th vnic to Intel E1000e in order to get things up and running.
  7. Wenn Du Dich im Forum umgesehen hättest, dann wärst Du auf folgendes Subforum gestoßen: https://xpenology.com/forum/forum/78-dsm-updates-reporting/ Dort werden Erfolge und Misserfolge von Installationen und Updates von Versionen gepostet. Wenn man in ESXi die VNic auf Intel E1000e stellt, kann sogar unproblematisch auf 6.2.1update4 gehen.
  8. haydibe

    DSM 6.2.1-23824 Update 4

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 2 - Loader version and model: Jun's Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7, VM - ESXi 6.5 - Additional comments: Intel E1000e, LSI9211-8i in passthrough mode, Update applied to two different machines
  9. haydibe

    DSM 6.2.1-23824 Update 4

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 2 - Loader version and model: Jun's Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7
  10. I feel like i miss the words "the GPU is to the DSM6.2.1 vm in passthrough mode" and "the bootloader is configured to use a proper serial number". Without those two, you won't be able to leverage Hardware transcoding for Videostation. If you want to use hardware transcoding in Plex you still need the GPU in passthrough mode and a plex pass (as in plex subscription). My applications are on docker since day 1 the packe for synology was released. I hate the messines of synologies packages. Also the overhead of running an application inside a container compared to a synology package is minimal. Docker provides lightweight application virtualization, which has nothing to do with heavyweight machine vartualization. Though, Docker is not a first class citizen in the Synology world... - the docker version inside the package is outdated: 17.05 on Synology, while the rest of the world uses 18.09 - due to the ui controlling every aspect of the docker engine, a lot of functions are crippled On the other hand it has the easist to use UI of all solutions I have seen so far and it is absolute sufficient to get allmost everything up and running.
  11. Ich verwende einen LSI-Controller im pass-through Modus unter ESXi. Da ich den ganzen Controller in die VM reinreiche, muss ich nichts weiter tun. Wenn man keinen Controller in die VM "reinreichen" kann, bleibt einem nur die Verwendung von RDM (Raw Device Mapping), um die Platte der VM zuweisen zu können. Hierzu kann ich nur empfehlen folgenden Thread und vorallem das dort eingebundene Video anzusehen:
  12. Update lief sauber durch, aber das Problem ist noch da? DSM6.2.1 geht definitiv NICHT auf dem Gen8. DSM6.2.0 habe ich nie installiert, deshalb kann ich dazu wenig sagen. Ich würde dringend empfehlen auf 6.1.7 zu bleiben ODER ESXi draufzuzimmern und dann in einre VM auf DSM6.2.1 zu gehen
  13. I assume you succesfully installed DSM6.2.1 and miss the ip in the build in web console of ESXi? Did you install the open-vm-tools package? Add this location http://spk.4sag.ru/ as a package source and install it from there Oh, and the vNIC needs to be E1000e, I missed the first E in my earlier post. When set to E1000 it will not work.
  14. If you take precautions things will play out nicely: - setup serial number and MAC in the grub.cfg of synoboot.img - be sure to set you vNIC to Intel 1000e, otherwise the DS3615SX bootloader 1.03b won't be able to find your nic on DSM6.2.1. - be sure synoboot is connected as SATA0:0 - if you want to attach additional vmdks, add another SATA controller and assign those vmdks to SATA1:x, starting from 0. If you don't use additional vmdks don't add the additional SATA controller. Your LSI-Controller is supported by DSM6.2.1. I have two ESXi hosts running DSM6.2.1 with the same controller passed in. Usualy it is not necessary to tinker arround with the settings for DiskIdxMap=0C or SataPortMap=1. If the controller SATA1 is added you might need to append values for the second controller.