hajuuk

Thanks for your answer, seems the misunderstanding is caused by I didn't tell you enough detail of my story. Here is the full story: I followed this link: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9 ... g!5kcjyJ7R the link is exactly from the first post of this topic. Then, here is two folder, v1.02a and v1.02a2 There are another subfolder under v1.02a2, named ds916p and ds3617xs. Under ds3617xs folder, I can find two files, 'synoboot.img' and 'modprobe'. However, I can't find any file related to vmware environment, such as vmx or ovf. So, I downloaded the full package of v1.02a, and replaced the 'synology.img' by the file downloaded from v1.02a2. Then, I got the vmware package of v1.02a2 img, and upload it to my ESXi server and boot it on, install DSM 6.1.1, then, BOMB. 'vmware package' means: ds3615.ovf - from DS3617xs 6.1 Jun's Mod V1.02-alpha.zip ds3615.vmx - from DS3617xs 6.1 Jun's Mod V1.02-alpha.zip synoboot.img - from v1.02a2\ds3617xs\synology.img synoboot.vmdk - from DS3617xs 6.1 Jun's Mod V1.02-alpha.zip

The time bomb is STILL EXIST in Jun's Loader v1.02a2 Running Hardware: HP Gen8 Microserver ESXi 6.5 The procedure of re-create the time bomb: 1. Download Jun's Loader v1.02a, exact it and replace the image by v1.02a2 2. Upload all files without .ovf to ESXi, and set up the Virtual Machine. 3. Start the virtual machine and install DSM 6.1.1 (6.1 have tested as well) 4. Keep it running for around 12 hours, then, reboot DSM in top right corner menu 5. Once it finished rebooting, the time bomb will be activated. Other things I tried: Set the serial number to a valid one, no use. Don't reboot the system, after 12 hours some function may not work, such the security panel in Settings Reboot system after around 4 hours, time bomb not activated. If needs more information for analysis, please let me know how to pull the log out, I'll try to do so, and upload it. Finally, appreciate for Jun's work. [spoiler=Clarification]Original Posted here, for more attraction, I pop it out from the long post, and re-organised some information. For clarification, the issue occurred under ESXi environment, not bare metal environment. Platform: ESXi 6.5 running on: HP Gen 8 Microserver CPU: Intel Xeon E3-1230 V2 Memory: 10 GB (2+8) Hard Drive: 4GB WD Red USB Thumb Boot into ESXi 6.5 Due to the Jun's Loader didn't provide vmware file with v1.02a2 release, so I self combined one: ds3615.vmx - from DS3617xs 6.1 Jun's Mod V1.02-alpha.zip synoboot.img - from v1.02a2\ds3617xs\synology.img synoboot.vmdk - from DS3617xs 6.1 Jun's Mod V1.02-alpha.zip Then, I upload all file listed upon to ESXi Storage. Create VM by ds3615.vmx and directly boot it on. For testing propose, I create a 100GB Virtual Hard Disk for this virtual machine, and didn't touch any file in synology.img. Then, boot the virtual machine, install DSM 6.1.1, skip all the things related Synology services, finally enter the desktop of DSM. Keep it running for around 4 hours, I reboot it for first time (the reboot option in DSM, not ESXi), everyhing works fine. Then, keep it running for around 12 hours, I reboot it for second time, then, the time bomb activated. For the reason I do the reboot: Previously, I tried to install DSM 6.1 on ESXi with Jun's Loader of DS3615xs and DS3617 v1.02a. After several hours (I didn't count it before, it could be 12, 24 or 48 hours), simply reboot DSM it will activate the time bomb. Then, I do the test after 12 hours of Jun's Loader v1.02a2, and it activated indeed. If there need any files for analysis, please let me know, I will try to extract it and upload it here. Thanks