Jump to content
XPEnology Community

viumden

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by viumden

  1. 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?
  2. CrystalDiskInfo or HD Tune running on windows?
  3. It seems this has been confirmed as a bug by synology? https://forum.synology.com/enu/viewtopic.php?f=269&t=122007&start=15
  4. 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...
  5. 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?
  6. 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?
  7. viumden

    DSM 6.1.x Loader

    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...
  8. viumden

    DSM 6.1.x Loader

    @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?
  9. 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.
  10. 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).
  11. viumden

    DSM 6.1.x Loader

    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?
  12. viumden

    DSM 6.1.x Loader

    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?
  13. viumden

    DSM 6.1.x Loader

    @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?
  14. 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?
  15. Is that so in VMWARE WORKSTAION, by using RDM, only disks smaller than 2 TB can be used? I added 2 4T WD NAS disks and add them by using SCSI interface, the disk can be detected, but seems cannot be read/write correctly, and in the end it causes disk break... (S.M.A.R.T warning emerged). And then I read below documentation: http://pubs.vmware.com/workstation-12/i ... 48D2F.html Anyone have similar experience? Or 2T disk will work totally OK?
  16. viumden

    DSM 6.1.x Loader

    Really thanks for the detailed instructions! I tried to download the source code and compile hyper-v related kernel modules, and managed to get the hv_balloon.ko, hv_utils.ko, hv_vmbus.ko, hv_netvsc.ko, hv_storvsc.ko and hyperv_fb.ko available, then modified /etc.defaults/rc.modules like below: EXTRA_MODULES="hyperv_fb mii mdio libphy usbnet atl1 atl1e atl1c alx cnic bnx2 bnx2x uio tg3 ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc igb ixgbe e1000 e1000e hv_utils hv_balloon hv_netvsc pcnet32 r8101 r8169 r8168 vmxnet3 ax88179_178a button evdev" DISK_MODULES="BusLogic hv_vmbus hv_storvsc vmw_pvscsi megaraid_mm megaraid_mbox megaraid megaraid_sas scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl mpt2sas" EXTRA_FIRMWARES="bnx2/bnx2-mips-06-5.0.0.j3.fw bnx2/bnx2-mips-06-6.2.1.fw bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-5.0.0.j3.fw bnx2/bnx2-mips-09-6.2.1a.fw bnx2/bnx2-mips-09-6.2.1b.fw bnx2/bnx2-rv2p-06-5.0.0.j3.fw bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-5.0.0.j3.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg357766.bin tigon/tg3.bin tigon/tg3_tso.bin tigon/tg3_tso5.bin bnx2x/bnx2x-e1-7.0.29.0.fw bnx2x/bnx2x-e1-7.8.17.0.fw bnx2x/bnx2x-e1-7.8.19.0.fw bnx2x/bnx2x-e1h-7.0.29.0.fw bnx2x/bnx2x-e1h-7.8.17.0.fw bnx2x/bnx2x-e1h-7.8.19.0.fw bnx2x/bnx2x-e2-7.0.29.0.fw bnx2x/bnx2x-e2-7.8.17.0.fw bnx2x/bnx2x-e2-7.8.19.0.fw bnx2x-e1-5.0.21.0.fw bnx2x-e1h-5.0.21.0.fw" Then repack the ramdisk, make it into bootable ISO (isolinux), the ramdisk loads successfully in hyper-v: Loading ../zImage... ok Loading ../ramdisk_new.lzma... ok early console in decompressing_kernel Decompressing Linux... Parsing ELF... done. Booting the kernel. Then nothing happened, I still cannot see the DSM IP available in my router DHCP lease list, seems network is still not up properly, not sure whether there are other things to be done to make everything work in Hyper-V. It seems further work in kernel patching/configuration is needed to hyper-v work? Whether there are still Xpenology developer to share what has been done in the official release which makes hyper-v work like a charm?
  17. viumden

    DSM 6.1.x Loader

    Compiling any disk adapter modules is not possible at the moment due to unexported syno_libata_get_index function (declared in libata-core). So only way to fix it is recompile kernel (we don't have latest kernel sources to do that) or somehow modify drive adapter sources to not depends on syno_libata_get_index function. Edit: Files moved to mega.nz from my webhosting. Awesome work, Arcao! Would be better you can share how this is compiled and how this ramdisk is repacked, so more people with linux experience would help to test more drivers. It would really perfect if you can help to compile and repack Hyper-V related drivers in ramdisk, something like in kernel configuration menu: Device Drivers --> Network device support --> Device Drivers --> Microsoft Hyper-V guest support --> Device Drivers --> HID Support --> Special HID Drivers --> A lot of people like me will be happy to test your work in Hyper-V. Thanks!
  18. viumden

    DSM 6.1.x Loader

    It's ICH8R - You need ata_piix.ko, which is not included, I will add it to bootimage. Will you kindly be able to pack Hyper-V network support module too?
  19. viumden

    DSM 6.1.x Loader

    I created Hyper-V virtual machine with EFI grub, kernel and ramdisk image properly configured in EFI partition and leave second linux partition available. The grub booted and I believe kernel and ramdisk is also properly loaded, but after that I see empty screen (I guess output is directed to serial output), and the machine IP doesn't show up in my router's DHCP list (I use the exact VM configuration to boot ubuntu live iso, the network is available with IP address assigned). So I am thinking is that so the kernel and ramdisk doesn't contain proper ethernet driver for Hyper-V? I am not able to see serial output, although I tried to use powershell to set version 2 Hyper-V machine's COM1: And no matter using piped.exe + secureCRT or Windbg, I cannot successfully get serial connection to the VM through "\\.\pipe\com1", secureCRT stays attaching status forever, and Windbg says access denied... I am wondering whether it is also because network driver issue, so it is just not possible to read any output from the VM. Anyone has ideas to proceed?
  20. viumden

    DSM 6.1.x Loader

    In hyper-V it boots and I can see VM screen: Then nothing else, and find.synology.me cannot connect in browser. Anyone can help and figure out the reason? Is that so the kernel and ramdisk has to be booted using EFI way? I dont know anything specific about Hyper-V, but in general, is is not possible to install this version with ISO only, but use ISO to load an installed version should be fine. The reason is DSM installer expect writable synoboot1/synoboot2 partitions, and I dont attemp to change this part of logic. Could you share more details about writable synoboot1/synoboot2 partitions? If I have an existing installation in VM with DSM5.2 on virtualized SCSI mounted disk, does that mean the condition is met? And in case I want to do a new install on SCSI disk (no matter it is real one or virtualized one), should I manually create such partitions first, and do you have specifications on how such partitions should be created?
  21. viumden

    DSM 6.1.x Loader

    Is it possible to use isolinux to boot the kernel and ramdisk? I put the provided zImage and ramdisk.lzm(a) and use isolinux to generated iso with syslinux.cfg something like below: In hyper-V it boots and I can see VM screen: Then nothing else, and find.synology.me cannot connect in browser. Anyone can help and figure out the reason? Is that so the kernel and ramdisk has to be booted using EFI way?
  22. viumden

    DSM 6.1.x Loader

    Anybody find way to make the loader adapted to run DSM6 in Hyper V?
  23. I am also very interested in when the traditional xpenology iso will be released for DSM6. There are solid works to make USB boot, ESXi and VMWare workstation work, what is still needed/missing to be modified to form a ready to use ISO?
  24. viumden

    Working DSM 6

    What is the side effect if we sticking with "Install" option as default boot choice to get the network support? Everything except brtfs will work well? Any methods to get the network driver work (compiled and integrated) in "Run" mode? I think there is some one claiming to have beta phase DSM6.0 kernel source, can we make benefit of that before Synology releases the complete sources? Posted via Xpenology.us
×
×
  • Create New...