Balrog

You can make custom installation ISO ESXi 6.5 and integrate newest needed drv. Look at https://www.v-front.de/p/esxi-customizer-ps.html The best manual in Russian here. I had problem with Realtek Net. Thank you for the informations, very useful!! I can't read Russian but the Google translator will do the work. But the question if I still need a different driver for the sata-ports under esxi 6.5 at the hp gen8 microserver is still unanswered.

Here is what I used on esxi 6.5, on a hp gen8 microserver : https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs It's jun's loader 1.01. Add drive and install. If you want to modify the grub cfg you need to set the boot drive as dependent or persistent before edit. But I see no need for abusing synology services, ..... Thank you very much for the infos! Do you have problems with slow data transfers to the hard disks connected to the internal sata ports with esxi 6.5 on a hp microserver gen8? I know that with esxi 6.0 there is a workaround by using the older sata-driver from hp for esxi 5.5 but I don't know if this currently needed at esxi 6.5 Btw: Thanks to all devs and all members who brings life into upgrading xpenology to a newer version! It begins to get better and better. My favorite solution is to stay at my current bare metal install at my gen 8 with VirtualBox on top but this is only possible with the sources. So I must look around for other solutions.

Thank your very much for the informations! Very handy.

@AllGamer: Thank you very much for this informations! Very useful.

Change the script so it matches the available powersave governor. Example: /usr/local/etc/rc.d/S99Powersaving.sh Script-content: #!/bin/sh echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor echo powersave > /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor Make the script executable (look above this thread or "chmod a+x scriptname.sh"). Afterwards run it or reboot.

@updateing: Very nice work! Thanks for posting your way through the function calls.

I am able to deinstall ipkg and install opkg with the following procedure: List all installed packages: ipkg list_installed remove packages step by step via: ipkg remove Afterwards I modified the /etc/rc.local to not mount /volume1/@optware # mount -o bind /volume1/@optware /opt The last step was to change the root back to the ash-shell in /etc/passwd root:x:0:0:root:/root:/bin/ash after a reboot I am without ipkg. Then I applied the steps in Post #1 and voila: opkg runs. The only package I miss till now is cpufrequtils which I couldn't install via opkg install cpufrequtils This is no real problem as I am able to set the cpu-gouvernour via echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor but maybe someone has a info how to install the package correctly via opkg

Thanks for the infos! Is there a little how-to for moving from ipkg to opkg? It would help if I can read how to delete/clean the ipkg installation. Afterwards I can use the informations from post #1.

Thanks very much for the update! The update from version 4.3.28-100309-1 to version 5.0.2-102096-2 runs without any issues. All VMs are up and running.

Try to reinstall the virtualbox-package again (just like the original installation with the same settings). I had a similar situation in the past and the reinstall solves the issue. Edit: and reinstall the Perl-package which is needed by virtualbox.

At my test-installation it isn't compatible with 5.2-5592 Update 2. After the upgrade from 5.2-5592 to 5.2-5592 Update 2 a lot of packages are not running anymore (e.g. the notestation). An installation with 5.2-5592 and an update to 5.2-5592 Update 1 went well: everything runs. So for me its save to stay currently with Update 1.

Thank you very much!

Thank you very much for the informations! It saves me much time for searching around.

Oh my, I feel like a total nob, I must have been blind not seeing it. Thanks for this. I was having problems with my VMs because they start so fast that they aren't able to get the correct time and date from the host DSM. So I changed that startup-script a little bit and build in a 15 second wait-timer for each VM: vi /var/packages/virtualbox/scripts/vboxinit.sh Search "start ()" and change the block to: start() { # Get all autostart machines MACHINES=$($su_command "$vboxmanage list vms | awk '{ print \$NF }' | sed -e 's/[{}]//g'") for UUID in $MACHINES; do STARTUP=$($su_command "$vboxmanage getextradata $UUID 'pvbx/startupMode'" | awk '{ print $NF }') if [ "${STARTUP}" == "auto" ]; then VMNAME=$($su_command "$vboxmanage showvminfo $UUID | sed -n '0,/^Name:/s/^Name:[ \t]*//p'") echo "$0: starting machine ${VMNAME} ... and waiting 15 seconds" sleep 15 $su_command "$vboxmanage startvm $UUID --type headless" >>$LOG fi done } The changed lines are: echo "$0: starting machine ${VMNAME} ... and waiting 15 seconds" sleep 15 Save the file (type :wq) and you are ready to go. The next time the server starts every VM with automatic start will wait 15 seconds. This works for me very good and the VMs have the correct time from the host-system (which gets the time from a ntp-server).

*double post*

I just make a very little manual: # Prerequisite: the bond must be already configured and running (on DSM and on LAN-Switch) # Login as "root" with SSH #open the config-file in vi: vi /etc/sysconfig/network-scripts/ifcfg-bond0 #search the line: BONDING_OPTS="mode=4 use_carrier=1 miimon=100 updelay=100 lacp_rate=fast" # press "i" to enter the "input-mode" from vi and change it to (all in one single line!): BONDING_OPTS="mode=4 xmit_hash_policy=layer3+4 use_carrier=1 miimon=100 updelay=100 lacp_rate=fast # press "esc" and then ":wq" (without the " of course ) (wq stands for "write and quit vi afterwards") # reboot and you're done Now I must test if the change results in an improvment of the speed.

Thank you very much for posting these discoveries! I will test this at my HP Microserver Gen 8 and make some new tests.

If you already have the actual boot-image (XPEnoboot 5.2-5565.2 (07/06/2015)) then you can do the update directly within the DSM like on real Synology. The first boot after the update might hang and you have to make a hard reset. If you want to make it safe, make a copy of /etc (e.g. with winscp) to your pc so you are able to recover important files if an error occours like at my installation (read a few posts up).

My second DSM installation under Hyper-V runs without any issues but there I have not enabled any ssl-services (not under web-services and not under DSM itself). So be careful at upgrading if you have enabled SSL!

After updating my HP Microserver Gen 8 (baremetal) there are problems with SSL. No https-service runs correct. It must have to do with the certififcates... I will investigate this later. EDIT: So first workaround is to disable SSL: - make a SSH connection and logon as root - edit /etc/synoinfo.conf with your favorite editor (vi or nano I asume) - search "runHTTPS" and "runWebHTTPS" and change both entries to "no" - save file and reboot After the reboot SSL is deactivated but you can login. Now to step 2 and howto make SSL work again.... EDIT2: I make SSL working again Something in the update-process has destroyed the contents of files under /etc/httpd/conf/extra so e.g. the file "httpd-ssl.conf-cipher" was totally filled with garbage. I copied the files from /etc.defaults/httpd/conf/extra (which has correct files) to /etc/httpd/conf/extra. To make it complete I copied /etc.defaults/httpd/conf to /etc/httpd/conf. The last step is to remake the internal SSL-certificates: cd /usr/syno/etc/ssl/ ./mkcert.sh wait till the new internal certificates are created and then reboot Voila, after the reboot all SSL-Sites are up and running again!

Have you enabled the SMB3 support in the settings of DSM (you find it under the protocols in a sub-menu)? The client must be also a win 8.x or win 2012 server with multiple nics. On the client side the SMB3 support is enabled by default.

I am glad to hear that the project is not dead and thanks very much for the links to the wayback-machine and @Sancomes download-url. I will stay tuned.

for question 2: Do you have installed the guest-tools for your vm (settings -> install guest additions)? There is no shared folder access without the tools.

I discovered only one little problem => manual mounting of the usb-stick doesn't work at my installation: DiskStation> mount -t vfat /dev/synoboot1 /volumeUSB1 mount: mounting /dev/synoboot1 on /volumeUSB1 failed: Invalid argument But this is not critical for me. I will investigate this later.

Thanks for the solution! I will try it and give feedback. EDIT: Yeah, it works very well!! Very good work as it makes the usb-unmount-script obsolete.