Wurstpilot Posted April 2, 2017 Share #76 Posted April 2, 2017 Works like a charm on my N54L. Anyone have any idea when the AMD option will be added to the alpha loader?Or how to put the option in as it was in the DSM6.0 one. Keen to get my N40L updated to 6.1 same as my main Synology. Link to comment Share on other sites More sharing options...
gpowa Posted April 2, 2017 Share #77 Posted April 2, 2017 Hello, i have an issue with Btrfs-System on 2 SATA-HDDs. When i format the Volume with this system, i am not able to install anny app from Package-Center. It says "Download failed". After i reformat in ext4, all work fine. But i want to format in the new format, what can i do? "2017-04-02T10:44:42+02:00 Modstation synoscgi_SYNO.Core.Package.Thumb.Server_1_get[30387]: pkgcurltool.cpp:579 Failed to download https://global.download.synology.com/do ... umb_72.png, code=28, err=Error 2017-04-02T10:44:42+02:00 Modstation synoscgi_SYNO.Core.Package.Thumb.Server_1_get[30391]: pkgcurltool.cpp:579 Failed to download https://global.download.synology.com/do ... umb_72.png, code=28, err=Error" gpowa Link to comment Share on other sites More sharing options...
worms Posted April 2, 2017 Share #78 Posted April 2, 2017 I'm the only one that can't upgrade from quicknik to this? And I'm on baremetal Microserver G8 Link to comment Share on other sites More sharing options...
gpowa Posted April 2, 2017 Share #79 Posted April 2, 2017 I'm the only one that can't upgrade from quicknik to this? And I'm on baremetal Microserver G8 I have a HP Microserver Gen8 too, and the Installation work fine. First Time i test the 1.02a Loader and RS3617xs/6.1/15047 and this don`t work for me. Then I tested DS3615xs/6.1/15047 and this don`t work too. So I tested 1.01 and DS3615xs/6.02 and this work, so after this i tested 1.02a and DS3615xs/6.1/15047. This Time it worked fine for me. The Only Fault is that i can`t use Btrfs-System and must use ext4-System. gpowa Link to comment Share on other sites More sharing options...
worms Posted April 2, 2017 Share #80 Posted April 2, 2017 Oh, I came from quicknick 6.0.2 and it was fine. Could you share your grub.cfg? I can't make it working.. maybe the sataportmap? I tried 1, 4,44,422,42. But when I put in "reinstall" he work. Link to comment Share on other sites More sharing options...
gpowa Posted April 2, 2017 Share #81 Posted April 2, 2017 Oh, I came from quicknick 6.0.2 and it was fine. Could you share your grub.cfg? I can't make it working.. maybe the sataportmap? I tried 1, 4,44,422,42. But when I put in "reinstall" he work. Ok, now it work on me too. I have format in ext4 and reinstall the DSM and then i have to recall Factory-Defaults and install in Btrfs-System, and the went all good. The only Issue i have is the LAN/DHCP Prob. So i have to change to manual, but is ok for me. gpowa Link to comment Share on other sites More sharing options...
worms Posted April 2, 2017 Share #82 Posted April 2, 2017 I relaly can't made it work. I used this serial generator https://xpenology.github.io/serial_gene ... r_new.html Use MAC Address 001132d80976 and didn't work. What i'm missing abount? I can see the interface only selecting "reinstall" but no activity on normal boot Link to comment Share on other sites More sharing options...
mesa57 Posted April 2, 2017 Share #83 Posted April 2, 2017 (edited) There where many post on getting a migration work under vmware (no network after migration). These we're the steps I performed to update my virtual machine from dsm 6.0 to dsm 6.1 with Jun's loader v1.02a : Copy dsm6.0 vm to new folder Copy synoboot.img, synoboot.vmdk to new vm folder Boot machine Start syno, install and migrate. After migrate wait at least 5 minutes, the system will not be reachable any more. Shutdown Prepare a bootable (liliboot) Linux live cd with gparted. Boot to EFI to boot from usb. Goto gparted terminal Mount raid system partition: sudo mdadm -AU byteorder /dev/md0 /dev/sdb1 cd /mnt sudo mkdir md0 sudo mount /dev/md0 md0 sudo cd md0 Do the copy modules trick : sudo cp lib/modules/update/* /lib/modules/ Reboot, you should be able to connect Edited April 3, 2017 by Guest Link to comment Share on other sites More sharing options...
Barrow1990 Posted April 2, 2017 Share #84 Posted April 2, 2017 Hi Ive got this working on ESXi and fully updated (DSM 6.1-15047 Update 2) in which is there a OpenVM tools for this? It was a clean install. Link to comment Share on other sites More sharing options...
zhenfu Posted April 3, 2017 Share #85 Posted April 3, 2017 Request to join support for hyper-v, thanks Link to comment Share on other sites More sharing options...
worms Posted April 3, 2017 Share #86 Posted April 3, 2017 I relaly can't made it work.I used this serial generator https://xpenology.github.io/serial_gene ... r_new.html Use MAC Address 001132d80976 and didn't work. What i'm missing abount? I can see the interface only selecting "reinstall" but no activity on normal boot Ok, solved. I need to do a clean install, not a migration. On Microserver g8 used sataportmap=1 Link to comment Share on other sites More sharing options...
Moredhel Posted April 4, 2017 Share #87 Posted April 4, 2017 Works like a charm on my N54L. Anyone have any idea when the AMD option will be added to the alpha loader?Or how to put the option in as it was in the DSM6.0 one. Keen to get my N40L updated to 6.1 same as my main Synology. Wurstpilot, which loader are you using? I've tried the DS3615xs 1.02a loader from the Mega share but there is no AMD option and the default won't boot on an N36L. Link to comment Share on other sites More sharing options...
RainbowShaggy Posted April 4, 2017 Share #88 Posted April 4, 2017 I tried this loader on my older computer with AMD where I install and running ESXi 4.1 and it looks, it works great Link to comment Share on other sites More sharing options...
Barrow1990 Posted April 4, 2017 Share #89 Posted April 4, 2017 Hi I seem to have a problem where DSM is unaccessible by GUI and the Dockers that are should be running are not available. This is running the v1.02a Bootloader on ESXi 6.0 I can ssh and telnet into the Nas but not visiable through Synology Assistant I read to run sudo cat /var/log/nginx/error.log which has multiple lines of the following. 2017/04/04 14:31:06 [crit] 9487#9487: *21 connect() to unix:/run/synoscgi.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.149, server: _, request: "POST /webman/login.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.0.210:5001" Also tried sudo synoservice --start DSM Ive also tried restarting nginx Using a port scanner and see both 5000 & 5001 available. On the serial port of the vm (serial.out) i get the following: [ 494.437583] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.440310] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 494.466552] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.469878] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 494.617507] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 494.620294] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 498.202643] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.205411] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 498.208177] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.210801] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 498.433474] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 498.436180] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 501.920509] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a213c0, ffff88007b7c3e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 501.923177] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-104 [ 501.942865] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff88007d3641c0, ffff880077423e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 501.945481] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-104 [ 501.984353] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 501.985716] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a213c0, ffffffffa0bef440) failed, ret=-22 [ 502.004551] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 502.005931] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff88007d3641c0, ffffffffa0bef250) failed, ret=-22 [ 502.229572] iSCSI:target_core_rodsp_server.c:677:rodsp_remote_client_login_init rodsp_msg_recv(ffff880078a83bc0, ffff88007b527e78, RODSP_SERVER_RECV_TIMEOUT_MSEC) failed, ret=-104 [ 502.232164] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-104 [ 502.292824] iSCSI:target_core_rodsp_server.c:721:rodsp_remote_client_login_init errcode(1) [ 502.294213] iSCSI:target_core_rodsp_server.c:756:rodsp_server_remote_client_login_handle rodsp_remote_client_login_init(ffffffffa0bfae00, ffff880078a83bc0, ffffffffa0bef620) failed, ret=-22 Link to comment Share on other sites More sharing options...
mpftc Posted April 4, 2017 Share #90 Posted April 4, 2017 Has anyone facing a frequent wake up (every 30 mins) problem with 6.1? I tried pull out cable&disable all packges . Problem still exsits. 7-04-04T02:47:05+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 02:45:00] 2017-04-04T03:07:41+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 03:07:11] 2017-04-04T03:27:52+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 03:27:21] 2017-04-04T03:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 03:41:41] 2017-04-04T05:41:20+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 05:36:25] 2017-04-04T06:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 06:40:24] 2017-04-04T07:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 07:07:12] 2017-04-04T07:47:10+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 07:28:06] 2017-04-04T08:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 08:12:53] 2017-04-04T08:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 08:27:54] 2017-04-04T09:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 09:07:12] 2017-04-04T09:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 09:32:00] 2017-04-04T10:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 10:14:44] 2017-04-04T10:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 10:27:54] 2017-04-04T11:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 11:07:13] 2017-04-04T11:32:35+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 11:28:11] 2017-04-04T11:47:05+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 11:45:53] 2017-04-04T12:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 12:07:14] 2017-04-04T12:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 12:28:11] 2017-04-04T13:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 13:07:13] 2017-04-04T13:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 13:28:06] 2017-04-04T14:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 14:16:26] 2017-04-04T14:34:45+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 14:28:06] 2017-04-04T14:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 14:45:26] 2017-04-04T15:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 15:07:13] 2017-04-04T15:32:42+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 15:28:06] 2017-04-04T15:46:58+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 15:43:19] 2017-04-04T16:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 16:07:12] 2017-04-04T16:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 16:31:54] 2017-04-04T17:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 17:07:14] 2017-04-04T17:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 17:28:07] 2017-04-04T18:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 18:07:12] 2017-04-04T18:33:23+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 18:28:06] 2017-04-04T18:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 18:44:18] 2017-04-04T19:17:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 19:07:12] 2017-04-04T19:47:05+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 19:42:30] 2017-04-04T20:47:08+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 20:38:20] 2017-04-04T21:35:40+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 21:32:45] 2017-04-04T21:47:30+08:00 Home scemd: event_disk_hibernation_handler.c:42 The internal disks wake up, hibernate from [Apr 04 21:46:15] And also bunch synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T06:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T06:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T07:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T07:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T07:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T08:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T08:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T08:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T09:47:28+08:00 Home kernel: [46857.647367] perf interrupt took too long (2501 > 5000), lowering kernel.perf_event_max_sample_rate to 50000 2017-04-04T09:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T09:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T09:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T10:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T10:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T10:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T11:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T11:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T11:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T12:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T12:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T12:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T13:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T13:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T13:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T14:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T14:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T14:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T15:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T15:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T15:56:31+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T16:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T16:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T16:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T17:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T17:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T17:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T18:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T18:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T18:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T19:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T19:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T19:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T20:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T20:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database 2017-04-04T20:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: check_sync.cpp:36 Failed to get license info 2017-04-04T21:52:52+08:00 Home synoscgi_SYNO.Core.User_1_set[4427]: user_set.c:911 libsynolocalaccount send SIG_KILL_MANUTILD 2017-04-04T21:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_json.cpp:23 Failed to get license from database 2017-04-04T21:56:32+08:00 Home synoddsmd_SYNO.License_1_check_sync[12552]: get_license_info.cpp:11 Failed to get license from database Link to comment Share on other sites More sharing options...
Benoire Posted April 5, 2017 Share #91 Posted April 5, 2017 Does anybody know how to mod the VMDK image for esxi to hide the ide boot device? I know the command, just don't know how to edit the files to change the grub lines. Link to comment Share on other sites More sharing options...
seeiis Posted April 5, 2017 Share #92 Posted April 5, 2017 Update to version 6.1 with loader 1.02a, I detect the network without problems, install the PAT, but after restarting I can no longer see it on the network, for any of my 2 LAN Cards, I see that there is activity because the HDD indicator is constantly blinking, any idea if I can do something to make it work? Link to comment Share on other sites More sharing options...
Polanskiman Posted April 5, 2017 Share #93 Posted April 5, 2017 seeiis said: Update to version 6.1 with loader 1.02a, I detect the network without problems, install the PAT, but after restarting I can no longer see it on the network, for any of my 2 LAN Cards, I see that there is activity because the HDD indicator is constantly blinking, any idea if I can do something to make it work? Try the v.1.02a-TEST loader >> https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=68662. Then revert. Link to comment Share on other sites More sharing options...
Benoire Posted April 5, 2017 Share #94 Posted April 5, 2017 Does anybody know how to mod the VMDK image for esxi to hide the ide boot device? I know the command, just don't know how to edit the files to change the grub lines. So I got it, simply used poweriso on the img file, edited the grub.cfg to add the correct command that hides the IDE drives, switched the VMDK on to the IDE controller and rebooted and it was gone. Link to comment Share on other sites More sharing options...
seeiis Posted April 5, 2017 Share #95 Posted April 5, 2017 Polanskiman said: seeiis said: Update to version 6.1 with loader 1.02a, I detect the network without problems, install the PAT, but after restarting I can no longer see it on the network, for any of my 2 LAN Cards, I see that there is activity because the HDD indicator is constantly blinking, any idea if I can do something to make it work? Try the v.1.02a-TEST loader >> https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=68662. Then revert. Sure, i try it, but nothing ill try later to reinstall the firmware with force install in the grub and clean install in DSM Install, If somebody have any idea Link to comment Share on other sites More sharing options...
iRegue Posted April 5, 2017 Share #96 Posted April 5, 2017 Hi, A few days ago i updated to 6.2 and it works fine. I can restart and shut down the NAS without problems, but today, when i arrived home and enter dsm to check the download station, i cant enter to DSM. It says that. What can i do? i restart the system but the message is the same. this is the correct ip and port. I need help please. Thank you so much. Link to comment Share on other sites More sharing options...
seeiis Posted April 5, 2017 Share #97 Posted April 5, 2017 Hi, A few days ago i updated to 6.2 and it works fine. I can restart and shut down the NAS without problems, but today, when i arrived home and enter dsm to check the download station, i cant enter to DSM. It says that. What can i do? i restart the system but the message is the same. this is the correct ip and port. I need help please. Thank you so much. What you do, to install the update 6.1? how the LAN get DHCP? Link to comment Share on other sites More sharing options...
iRegue Posted April 5, 2017 Share #98 Posted April 5, 2017 Hi, A few days ago i updated to 6.2 and it works fine. I can restart and shut down the NAS without problems, but today, when i arrived home and enter dsm to check the download station, i cant enter to DSM. It says that. What can i do? i restart the system but the message is the same. this is the correct ip and port. I need help please. Thank you so much. What you do, to install the update 6.1? how the LAN get DHCP? Hi, i download the loader of this topic. I burn into an USB and put the vid/pid. I use the second option in loader and i do a clean install of 6.1 keeping my files. When the install finished, i put the static ip and my port and all was good. I update to update 2 too and all good. In the next 2 days i use the NAS for download and i turn off and on when i want and all was good. But yesterday, when i want to enter to see my downloads, i see this message. I restart and turn of the machine some times and nothing always this message. I do ping by cmd in windows to the nas ip and is good. I dont know what can i do. My nas is asrock q1900 itx 4 gb ram and 7 hdds in shr. The video output of the nas said me than the loader is good. nothing extrange here. Thank you so much. Link to comment Share on other sites More sharing options...
seeiis Posted April 5, 2017 Share #99 Posted April 5, 2017 Hi, A few days ago i updated to 6.2 and it works fine. I can restart and shut down the NAS without problems, but today, when i arrived home and enter dsm to check the download station, i cant enter to DSM. It says that. What can i do? i restart the system but the message is the same. this is the correct ip and port. I need help please. Thank you so much. What you do, to install the update 6.1? how the LAN get DHCP? Hi, i download the loader of this topic. I burn into an USB and put the vid/pid. I use the second option in loader and i do a clean install of 6.1 keeping my files. When the install finished, i put the static ip and my port and all was good. I update to update 2 too and all good. In the next 2 days i use the NAS for download and i turn off and on when i want and all was good. But yesterday, when i want to enter to see my downloads, i see this message. I restart and turn of the machine some times and nothing always this message. I do ping by cmd in windows to the nas ip and is good. I dont know what can i do. My nas is asrock q1900 itx 4 gb ram and 7 hdds in shr. The video output of the nas said me than the loader is good. nothing extrange here. Thank you so much. Ok Thank you, you put the Static IP Throug the DSM? Link to comment Share on other sites More sharing options...
iRegue Posted April 5, 2017 Share #100 Posted April 5, 2017 yes, at first i can enter to dsm, and now no. synology assistant dont find the nas too... thank you Link to comment Share on other sites More sharing options...
Recommended Posts