• Announcements

    • Polanskiman

      DSM 6.2-23739   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs Release note: Version: 6.2-23739   (2018-05-23) Important Note The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. Compatibility and Installation DSM 6.2 can only be installed on Synology products running DSM 6.0 and above. Starting from DSM 6.2, the core replication function is centrally managed by a new package, Replication Service. Packages with replication feature, such as Snapshot Replication, must install the Replication Service package. For the following models, DSM 6.2 will be the last upgradable version. DSM 6.2 will continue to receive critical and security updates for a minimum of 2 years after the official release. XS Series : RS3412xs, RS3412RPxs, RS3411xs, RS3411RPxs, DS3612xs, DS3611xs Plus Series : RS2212+, RS2212RP+, RS2211+, RS2211RP+, RS812+, RS812RP+, DS2411+, DS1812+, DS1512+, DS1511+, DS712+, DS412+, DS411+II, DS411+, DS213+, DS212+, DS211+, DS112+ Value Series : RS812, RS212, DS413, DS411, DS213, DS212, DS211, DS112, DS111 J Series : DS413j, DS411j, DS411slim, DS213air, DS212j, DS211j, DS112j Others : DDSM What’s New in DSM 6.2 DSM For easier management, Key Manager can now be stored locally on Synology NAS. Encrypted shared folders can be auto-mounted without the need of a USB drive. (To achieve better data protection, users are suggested to store Key Manager on an external USB drive.) Standard users can now right-click on shared folders in File Station to view Properties. Added support for IBM WebSphere SSO. Enhanced password strength policy for better account security. Added support for a new SMS provider SendinBlue and Clickatell API (RESTful). Added support for Thai language. Updated Privacy Statement and related settings in the installation flow. iSCSI Manager Brand new iSCSI Manager built for IT administrators, providing a new management user interface for an optimized iSCSI management and monitoring experience. Advanced LUN provides lightning-fast LUN snapshot creation and recovery, and LUN cloning within seconds, as well as VAAI/ODX, storage acceleration commands, and support for better VM performance. Since Advanced LUNs can utilize file system cache to provide better efficiency, block-level LUNs will no longer be supported on DSM 6.2 and onward. DSM 6.2 will still be compatible with the block-level LUNs upgraded from DSM 6.1 and prior. Supports cross-volume LUN clones. Added support for network binding settings to allow each iSCSI target to map to a network interface. Users can now disable storage reclamation for thin-provisioned LUNs to enhance I/O performance. Storage Manager The brand new Overview shows the health status of all storage components on your NAS, displaying a clearer and better look on the system overview. Introduced Storage Pool, a new storage component, to replace the original Disk Group and RAID Group, and rearrange storage-related functions to provide users with a more consistent and smoother experience. Smart Data Scrubbing detects the supported file system and RAID type to perform data scrubbing automatically while enhancing data scrubbing usability. A new built-in scheduler allows users to do data scrubbing periodically with just a few clicks, improving data integrity and consistency. RAID resync speed can now be adjusted to accommodate IT management needs. Users can remotely deactivate drives via Storage Manager for better management. Added a default monthly S.M.A.R.T. test on both new and existing drives that were not previously configured. After each DSM upgrade, DSM will remind users if a bad sector or lifespan alert is not set up.  The health status of disks is now uniform with storage pools and volumes. Log Center now includes disk logs. Provided an option to change stripe cache size when the RAID type of Storage pool is RAID 5, RAID 6, RAID F1, or SHR (three disks or above). High Availability Manager 2.0 High Availability Manager has been modularized into a package to ensure better system maintenance and offers greater update  flexibility. New mechanism can now eliminate unnecessary system reboot during major update to keep your cluster secure and maintain high service availability. SHA 2.0 can handle situations more effectively especially when the servers are in a vulnerable state. A simpler yet more intuitive user interface,  offering you a comprehensive cluster overview and management. The new interface design provides more detailed and visual information as well as easy-to-follow solutions. Brand new user interface is introduced to display more details of both active server and passive server, giving you an in-depth system utilization overview.  When first creating SHA cluster, user new to SHA can choose to only replicate system configuration to shorten setup time. Extended Btrfs File System Coverage Btrfs file system is now available on more Synology NAS models utilizing ARM platforms. Enjoy the powerful features of the next-generation file system. Applied Models: 18-series: DS218, DS418 and more x18 series to come.  Azure AD support Added the capability to join existing Azure AD as an SSO client. Utilizing the single sign-on feature, daily productivity is increased by saving time spent on re-authentication. Security Advisor User login details and abnormal geolocation information are dissected using intelligent analysis techniques and reported via DSM notifications.  Daily and monthly reports provide more comprehensive information, allowing IT administrator to review abnormal activity and security scan regularly. TLS/SSL Profile Level An advanced way to configure your security level profile based on different services to meet different security level requirements, providing flexibility to suit your network security requirements. 2-step authentication Synology NAS administrators must set up an email notification when 2-step authentication is enabled. Domain/LDAP management Flexibly assign specified domain groups with admin privileges. FTP Added ECDSA certificate support for FTPS connections. NFS Added NFS v4.1 multipathing for load balancing and network redundancy to fully support VMware vSphere® 6.5. Applied models: 18-series : DS3018xs, DS418play, DS918+, DS418j, DS418, DS718+, DS218+ 17-series : FS3017, FS2017, RS4017xs+, RS3617xs, RS3617RPxs, DS3617xs, RS3617xs+, RS18017xs+, DS1817+, DS1817, DS1517+, DS1517, RS217 16-series : RS2416RP+, RS2416+, RS18016xs+, DS416play, RS816, DS916+, DS416slim, DS416j, DS416, DS216play, DS716+II, DS716+, DS216j, DS216+II, DS216+, DS216, DS116 Package Center The brand new user interface design brings a more intuitive experience and allows users to quickly find everything they need. IHM tool Added Seagate IronWolf Health Management (IHM) support on DS118, DS218play, DS418j and DS418. Known Issues & Limitations DSM 6.2 is the last DSM version supporting IPv6 Tunneling in Network Interface. The Fedora utility will not be supported after DSM 6.2. Starting from DSM 6.2, the USB device drivers, including printers, cloud printers, DAC/speakers, Wi-Fi dongles, DTV dongles, LTE dongles, and Bluetooth dongles will no longer be updated. Wi-Fi dongle does not support Parental Control and Device List if set as Bridge Mode. Starting from DSM 6.2 Beta, Virtual Machine Manager will no longer support creating clusters with older DSM versions. Please update each host in the cluster to the same DSM version or above versions for the Virtual Machine Manager cluster to operate properly. SSH authentication by DSA public key is prohibited for security concerns. When logging in through VPN or Proxy server, some functionalities may have authentication issues. To fix this issue, please go to Control Panel > Security, and click the Trusted Proxies button to add the trusted proxy server to the list. The original RAID scrubbing scheduled tasks will be migrated to Smart Data Scrubbing scheduled tasks. If the upgrade is performed while running scheduled tasks, the Data Scrubbing process will automatically be re-executed shortly after the upgrade is completed.  Office 2.x and below are not compatible with DSM 6.2.  Hide    

libra1999

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About libra1999

  • Rank
    Newbie
  1. no need in my case, my gut feeling is that bootloader can grab the physical Mac during the boot, and then official pat installation package can config DSM accordingly. It may be required in the previous version of boot tools. Any thought for the hibernation. so frustrated and almost give up. may try Windows Storage Server 2012.
  2. Hibernation Issue with N54L + DSM5.0 Update2 + Nanoboot

    it does not help. I leave the only main HDD which have DSM installed and set as SATA other than eSATA. no hibernation at all.
  3. WOL works perfectly either LAN or WAN without adding MAC. however the hibernation still does not work even I remove the eSATA drive and leave only 1 main HDD. still could not see any log like "wake from hibernation"
  4. Hibernation Issue with N54L + DSM5.0 Update2 + Nanoboot

    Thanks Jbugman. what's the seats port? i STOP the video station but it didn't help out.
  5. Hibernation Issue with N54L + DSM5.0 Update2 + Nanoboot

    still struggling with the hibernation issue. check the scemd.log and see lots of entries about eSATA port check during the testing timeframe Jul 3 21:50:45 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:51:17 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:51:49 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:52:21 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) would this be the problem that stop the hibernation? Where I can make a change to MAX_CDISK_SATA? I have done the configure change to mount esata port by editing /etc.defaults/synoinfo.conf esataportcfg="0x0ffe" internalportcfg="0x001" folks, give a hand please.
  6. I installed 4493 and upgraded to update2 without any problem. just did within DSM. WOL also works well. May I ask why we need to change MAC and SN, is any other propose for this change. I could not have the hibernation work on my N54L. Looking forward to suggestion/instruction? -----update---- still struggling with the hibernation issue. check the scemd.log and see lots of entries about eSATA port check during the testing timeframe Jul 3 21:50:45 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:51:17 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:51:49 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) Jul 3 21:52:21 DiskStation scemd: modules/disk_check.c:539 The machine eSATA ports exceed defined value(MAX_CDISK_SATA) would this be the problem that stop the hibernation? Where I can make a change to MAX_CDISK_SATA? I have done the configure change to mount esata port by editing /etc.defaults/synoinfo.conf esataportcfg="0x0ffe" internalportcfg="0x001" folks, give a hand please.
  7. Just installed DSM5.0 on my N54L via Nano boot x64 iso. I have the problem with the hibernation. What I did include: 1> BIOS mod with O41100113 2> Enable eSATA for port 2-6, only port 1 set to SATA 3> WOL works well after adding the shutdown script. However, the hibernation does not work at all. After enable the debugging tools, I saw a number of log entry after disconnect LAN. Jul 2 20:38:09 DiskStation kernel: [ 9009.793257] [/etc/resolv.conf] opened by pid 17840 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:38:23 DiskStation kernel: [ 9024.164182] [pg_clog/0000] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:30 DiskStation kernel: [ 9030.661088] [base/16585/16725] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:33 DiskStation kernel: [ 9033.792095] [base/16585/16868] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:37 DiskStation kernel: [ 9038.135088] [base/16585/16875] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:42 DiskStation kernel: [ 9042.377092] [base/16585/16760] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:44 DiskStation kernel: [ 9044.700103] [base/16585/16751] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:46 DiskStation kernel: [ 9046.316093] [base/16585/16877] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:48 DiskStation kernel: [ 9048.336089] [base/16585/11778] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:49 DiskStation kernel: [ 9050.255095] [base/16585/16696] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:51 DiskStation kernel: [ 9051.530245] [/etc/resolv.conf] opened by pid 17841 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:38:54 DiskStation kernel: [ 9054.901103] [base/16585/11638] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:56 DiskStation kernel: [ 9056.820091] [base/16585/16682] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:38:57 DiskStation kernel: [ 9057.931082] [base/16585/16758] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:06 DiskStation kernel: [ 9066.314094] [base/16585/16788] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:08 DiskStation kernel: [ 9069.243082] [base/16585/16718] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:11 DiskStation kernel: [ 9071.970082] [base/16585/16694] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:12 DiskStation kernel: [ 9073.081091] [base/16585/16739] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:16 DiskStation kernel: [ 9076.717090] [base/16585/16659] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:21 DiskStation kernel: [ 9081.969089] [base/16585/16768] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:24 DiskStation kernel: [ 9084.393083] [base/16585/16709] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:31 DiskStation kernel: [ 9091.766082] [base/16585/16879] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:32 DiskStation kernel: [ 9093.079087] [base/16585/16621] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:42 DiskStation kernel: [ 9103.280084] [base/16585/11776_fsm] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:45 DiskStation kernel: [ 9105.502088] [base/16585/16726] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:39:54 DiskStation kernel: [ 9115.098168] [/etc/hosts] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:14 DiskStation kernel: [ 9135.198247] [/etc/resolv.conf] opened by pid 17957 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:23 DiskStation kernel: [ 9143.592093] [base/16585/16730] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:40:36 DiskStation kernel: [ 9156.835177] [/etc/hosts] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:40:49 DiskStation kernel: [ 9169.565092] [base/16585/16737] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:40:56 DiskStation kernel: [ 9176.935272] [/etc/resolv.conf] opened by pid 17958 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:41:18 DiskStation kernel: [ 9198.572331] [/usr/syno/etc/synoshare.db] opened by pid 18194 [u:(/var/packages/VideoStation/targ), comm:(synovideometada)] Jul 2 20:41:38 DiskStation kernel: [ 9218.726500] [/etc/resolv.conf] opened by pid 18010 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:01 DiskStation kernel: [ 9241.827178] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:21 DiskStation kernel: [ 9261.927264] [/etc/resolv.conf] opened by pid 18011 [u:(/usr/bin/php), comm:(php)] Jul 2 20:42:42 DiskStation kernel: [ 9283.028180] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:43:02 DiskStation kernel: [ 9303.128242] [/etc/resolv.conf] opened by pid 18012 [u:(/usr/bin/php), comm:(php)] Jul 2 20:43:23 DiskStation kernel: [ 9323.619077] [pg_clog/0000] opened by pid 15709 [u:(postgres: checkpointer process ), comm:(postgres)] Jul 2 20:43:45 DiskStation kernel: [ 9345.329306] [/etc/resolv.conf] opened by pid 18013 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:06 DiskStation kernel: [ 9366.430172] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:26 DiskStation kernel: [ 9386.530243] [/etc/resolv.conf] opened by pid 18014 [u:(/usr/bin/php), comm:(php)] Jul 2 20:44:48 DiskStation kernel: [ 9408.631155] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:08 DiskStation kernel: [ 9428.731249] [/etc/resolv.conf] opened by pid 18015 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:31 DiskStation kernel: [ 9451.832274] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:45:51 DiskStation kernel: [ 9471.932289] [/etc/resolv.conf] opened by pid 18016 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:13 DiskStation kernel: [ 9494.033158] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:33 DiskStation kernel: [ 9514.133240] [/etc/resolv.conf] opened by pid 18017 [u:(/usr/bin/php), comm:(php)] Jul 2 20:46:54 DiskStation kernel: [ 9535.234168] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:15 DiskStation kernel: [ 9555.334249] [/etc/resolv.conf] opened by pid 18018 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:36 DiskStation kernel: [ 9576.435285] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:47:56 DiskStation kernel: [ 9596.535300] [/etc/resolv.conf] opened by pid 18019 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:17 DiskStation kernel: [ 9617.636169] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:37 DiskStation kernel: [ 9637.736249] [/etc/resolv.conf] opened by pid 18020 [u:(/usr/bin/php), comm:(php)] Jul 2 20:48:58 DiskStation kernel: [ 9658.837168] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:49:18 DiskStation kernel: [ 9678.937251] [/etc/resolv.conf] opened by pid 18021 [u:(/usr/bin/php), comm:(php)] Jul 2 20:49:41 DiskStation kernel: [ 9702.038287] [/volume1/@appstore/VideoStation/plugins/plugin_data/com.synology.Synovideodb/cloud/info.json] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:01 DiskStation kernel: [ 9722.138307] [/etc/resolv.conf] opened by pid 18022 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:23 DiskStation kernel: [ 9744.239177] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] Jul 2 20:50:44 DiskStation kernel: [ 9764.339268] [/etc/resolv.conf] opened by pid 18023 [u:(/usr/bin/php), comm:(php)] Jul 2 20:51:06 DiskStation kernel: [ 9786.440171] [/etc/hosts] opened by pid 18009 [u:(/usr/bin/php), comm:(php)] it seems something keep still running and it is related to Video Station. Any thoughts/advice? thanks a lot.
  8. [SOLVED] Possible downgrade DSM 5.0

    Hibernation works for me with DSM 5 on an HP N54L if that helps. Hi, may I ask what's the boot you are using? gno or nano? I just installed DSM5 on N54L via Nanoboot x64 iso I upgraded to UPDATE2 and WOL works fine, but not for hibernation. could not work out why
  9. Trial of Nanoboot (4493) - 5.0.3.1

    Hibernation does work with my system, any thought?
  10. Trial of Nanoboot (4493) - 5.0.3.1

    Update2 works well in DSM without "sed" thanks Nanoboot!
  11. Drive Hibernation DSM 5.0-4493

    Actually, i have same stupid question, I set up the option in DSM but could not see anything related in the log file. Did I miss anything?
  12. I bought my toy N54L two weeks ago and just started to play with it. the first thing i did is to register my HP passport, however, once i put my S/N there, HP shows totally different product information. it says "HP ProLiant N36L 1P 1GB-U Int SATA Cold Plug SATA 160GB 200W PS MicroServer" and even links to a different product number (not what shows on the label of my server". further, the warranty expires by November, only 5 months left. Anyone experience this before? is it a refurbish product?
  13. N54L + XPEnlogy

    good luck, hope someone can help you out. My N54L still sits at the corner and to be installed.
  14. N54L + XPEnlogy

    Thanks a lot, Poechi If I set all SATA to eSATA via modifying /etc.deafults/synoinfo.conf, also I intend to attached these HDD after I have DSM installed. Would it be possible to install DSM without any SATA disk attached?
  15. N54L + XPEnlogy

    DSM doesn't use separate drive. It mirrors small system partition to all permanently connected (initialized) drives. USB is needed for synoboot, initial boot-loader. emm, it sounds a trouble for me. I am trying to avoid data migration. Can I set all SATA ports to eSATA with NFS supported and then use a USB as DSM OS? Would it have an issue for disk sleep mode? Cheers