viumden

It is reported by others as well in this thread:

It seems if mailplus is enabled in xpenology (DSM6.1.3 U5), and synology account is logged in, hyber backup will fail when trying to backup mailplus server data, log saying: [Network][Full BAK] Failed to back up application [MailPlus Server]. Failed to connect to Synology Account. Please check your network connection and try again later. When synology account is logged off, no such problem anymore. I assume it is related to mailplus license mechanism, because when you try to purchase a license for mailplus through the webui, it will fail as well, xpenology is lacking some sort of UUID to purchase the license, which means purchasing a license for presto file station or mailplus added account number is not possible for xpenology at all. The thing is without synology account logged in, the video and photo station codec conversion will not work, if I want both codec conversion and daily hyper backup work automatically in a daily basis, it is not possible now. Any idea to fix or workaround it?

CrystalDiskInfo or HD Tune running on windows?

It seems this has been confirmed as a bug by synology? https://forum.synology.com/enu/viewtopic.php?f=269&t=122007&start=15

Thanks, logout synology account in control panel does work, and mailplus works with free license shown, but when I login again, the same issue occurred, which means I cannot get use mailplus properly when I have my account login? Yes,I think mailplus server check the synology account license online. So that generally means extending mailplus user number through purchased license from synology is not possible...

Thanks, logout synology account in control panel does work, and mailplus works with free license shown, but when I login again, the same issue occurred, which means I cannot get use mailplus properly when I have my account login?

Just did a mailplus server and mailplus update to 1.1.2-0250 and 1.1.2-0465, under VMWare using Jun's newest loader, with 6.0.2-08451 Update 4, then I cannot use mailplus any more, by entering mailplus server it prompts: Failed to authorize your MailPlus Server. Please make sure you have enough valid licence keys. Before the update, there is the free license to authorize 5 users and everything went fine for mailplus. I tried to restart mailplus and mailplus server, reboot DSM, reinstall mailplus and mailplus server, no luck with the same error. Does anyone else meet the same issue and has any resolutions?

I was asking myself the same thing and I have done some testing on my gen8 with jun's 1.0.1 I replaced only zImage and gen8 boot succesfully Before admin@gen8:/$ uname -a Linux gen8 3.10.77 #8451 SMP Wed Aug 17 05:12:41 CST 2016 x86_64 GNU/Linux synology_bromolow_3615xs After admin@gen8:~$ uname -a Linux gen8 3.10.77 #8451 SMP Wed Nov 9 13:45:32 CST 2016 x86_64 GNU/Linux synology_bromolow_3615xs So I think the kernel has been updated... but no version change!? What does it mean? After I tried to replace also ramdisk.lzma... the gen8 boot, stay up only few seconds (Synology Assistant show it) and then it shutdown... [edit] After rebooting the gen8 with correct ramdisk.lzma from jun's I can see this error on system events >> Abnormality detected on gen8. All volumes have been unmounted. ciao ema Maybe there is also something to be updated in ramdisk.lzma based on synology's new rd included in update 4 pat file. And we have to wait for jun's analysis and further update...

@jun Since the upgrade in DSM to update 4 will not actually update kernel, then that means some critical security fixes mentioned in update 3/4 will not be applied even after the update, correct? Can I just extract the zImage from the update 4 pat file, then replace the loader's zImage in synoboot1 partition, if it boots correctly, then I actually updated the kernel too? And the same logic applies to ramdisk, so I have to extract the rd file from pat, and repack it with community compiled kernel modules with driver supports?

I think in Jun's loader, vmw_pvscsi is loaded in VMWARE workstation, and the disks passed to DSM is with correct driver, just S.M.A.R.T information is not passed and maybe APM functionality is not possible through vmw_pvscsi, so disk spin-down is not possible when DSM is in idle for a long time. And I found 4T works in RDM too (identified and formatted with btrfs and RAID5 correctely), although in the document it claims only 2T and smaller is supported.

It works using Jun's newest loader on my Windows 10 with VMWARE workstation pro 12, choose VMWARE option in grub menu when it is boot in workstation. I use RDM to pass the hard disks to workstation, 3*4T (2 WD Red NASWARE 3.0+1 seagate es.3) RAID5, no S.M.A.R.T monitoring is available in xpenology (but you can check it by tools installed in Windows still). Although in vmware workstation documentation it says only hard disks below 2T is supported in RDM, but 4T works for me until now (although only 1.1T is in use currently).

Is that so the zImage (kernel) used in the DSM loader is extracted from a real DS3615xs with DSM6.02 installed? Or I can compile a kernel using beta source code and use it to boot DSM6.02 anyway, but maybe some necessary customization is needed?

Since there are considerable difference between beta source and the release version, I write and compile kernel modules instead, even the AMD kernel is a combination of the original kernel and the AMD support code compiled as module (sort of). I compile beta src kernel only to aid debugging, itself does not work properly, lacking required symbol etc, and I do not bother to fix it. Thanks for the reply, jun! I am trying to make hv_balloon.ko, hv_utils.ko, hv_vmbus.ko, hv_netvsc.ko, hv_storvsc.ko load correctly as kernel module, but I get unknown symbol error, by checking dmesg output, there are many unknown symbols, for example: [436076.774681] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0) [436076.774985] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0) [436076.775042] hv_vmbus: Unknown symbol pv_cpu_ops (err 0) [436076.775055] hv_vmbus: Unknown symbol x86_hyper (err 0) [440432.878847] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0) [440432.878871] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0) [440432.878885] hv_vmbus: Unknown symbol pv_cpu_ops (err 0) [440432.878914] hv_vmbus: Unknown symbol x86_hyper (err 0) [440463.877528] hv_utils: Unknown symbol vmbus_driver_unregister (err 0) [440463.877545] hv_utils: Unknown symbol vmbus_sendpacket (err 0) [440463.877556] hv_utils: Unknown symbol vmbus_prep_negotiate_resp (err 0) [440463.877568] hv_utils: Unknown symbol vmbus_close (err 0) [440463.877578] hv_utils: Unknown symbol vmbus_recvpacket (err 0) [440463.877600] hv_utils: Unknown symbol cn_netlink_send (err 0) [440463.877611] hv_utils: Unknown symbol vmbus_open (err 0) [440463.877625] hv_utils: Unknown symbol cn_del_callback (err 0) [440463.877700] hv_utils: Unknown symbol __vmbus_driver_register (err 0) [440463.877717] hv_utils: Unknown symbol cn_add_callback (err 0) [440706.396491] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0) [440706.396518] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0) [440706.396532] hv_vmbus: Unknown symbol pv_cpu_ops (err 0) [440706.396545] hv_vmbus: Unknown symbol x86_hyper (err 0) Then maybe let's start with pv_cpu_ops, I checked the reference and dependency of this symbol in below link: http://lxr.free-electrons.com/ident?v=3.17;i=pv_cpu_ops Any suggestions on how to make such symbol loadable as a kernel module based on above link's information?

@Jun Can you share the steps to recompile your patched kernel zImage? I can recompile the kernel with Hyper-V support, but it seems still not work, so I guess I missed the proper patch for DSM6.0.2?

S.M.A.R.T is not there in guest (xpenology), I use tools in windows to monitor S.M.A.R.T. But is 2T disk working well and stable under RDM in VMWARE WORKSTATION?