• 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    

Kybla

New Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kybla

  • Rank
    Newbie
  1. XPEnology gnoBoot

    Hi and thanks for your great work. I'm using gnoBoot 10.4 as my home server and another one as a backup server, both on ASUS C60M1-I. Both are working great, except one (major) issue with the backup server. It seems that something in DSM 5.0 upgrade (on the real DS) broke Time Backup so that it is not able to do incremental network backups with any XPEnology as a target (though another real DS works fine). It always do "full" backups when using XPEnology as a target (while it does only "incremental" backup when using real DS as a target, which is correct behaviour). See my thread with full explanation of this issue here: http://xpenology.com/forum/viewtopic.php?f=2&t=2781 Could it be somehow related to the issue "Broken block-level iSCSI (LIO)", or is it another thing? Thanks for any help.
  2. Hi, I have been using XPEnology on real HW (ASUS C60M1-I) as a Time Backup target from my real DS (1512+) for a year and everything was working fine. I had block backup enabled, only changes were copied and every new backup (once a day) was an incremental one, so the occupied space on the backup DS was not expanding much. I had DSM 4.2 both on the real DS and backup DS (Trantor) But after the upgrade of the real DS (to DSM 5.0-4458 Update 1), the incremental backups to XPEnology as a target are not working properly anymore. Every time, the backup takes all the space of the data on the backup DS. I did a test and set a Time Backup to another real DS (712+), and then it works - only the first backup takes all the space, and every subsequent backup takes only the space of changed files. I also tried DSM 4.3 (Trantor) and DSM 5.0-4458 Update 1 (gnoBoot 10.4 alpha) on the backup DS, but still the same. As my explanation may be little confusing, I will explain it in steps. Legend: DS1 = main real DS1512+, DSM 5.0-4458 Update 1. DS2 = another real DS712+, DSM 5.0-4458 Update 1. DS3 = backup DS with XPEnology DSM 5.0-4458 Update 1 (gnoBoot 10.4 alpha). 1. I set Time Backup on DS1 with DS2 as a target to backup cca 10 GB of data, block level enabled. First run - 6 minutes, 10GB taken on DS2. Second run (immediately after), 2 minutes, additional 0.01 GB taken on DS2, totalling on 10.01 GB taken. Everything works fine. 2. I set Time Backup on DS1 with DS3 as a target with the same parameters and data as before. First run - 7 minutes, 10GB taken on DS3. Second run (immediately after), 4 minutes, additional 10 GB taken on DS3, totalling on 20 GB taken. Whoops . It seems that the subsequent backup is an "incremental" one, but on XPEnology, whole files are copied to the new backup location, instead of making only links as on the real DS. I've tried to compare logs from both DS2 and DS3, but I see nothing clear there: iscsi.log on DS2: Apr 1 12:57:50 Sedmdesatka kernel: [435172.212424] iSCSI: iSCSI: Discovery session from [127.0.0.1] Apr 1 12:57:51 Sedmdesatka kernel: [435172.569701] iSCSI: iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345] Apr 1 12:57:52 Sedmdesatka kernel: [435174.256099] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[(null)] Apr 1 13:02:45 Sedmdesatka kernel: [435467.397406] iSCSI: iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] Apr 1 13:02:45 Sedmdesatka kernel: [435467.412483] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] Apr 1 13:03:59 Sedmdesatka kernel: [435541.483492] iSCSI: iSCSI: Discovery session from [127.0.0.1] Apr 1 13:04:00 Sedmdesatka kernel: [435541.799758] iSCSI: iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345] Apr 1 13:04:01 Sedmdesatka kernel: [435543.526056] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[(null)] Apr 1 13:04:36 Sedmdesatka kernel: [435578.058400] iSCSI: iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] Apr 1 13:04:36 Sedmdesatka kernel: [435578.073135] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] iscsi.log on DS3: Apr 1 17:12:29 Thecology kernel: [ 3302.349385] iSCSI: Discovery session from [127.0.0.1] Apr 1 17:12:30 Thecology kernel: [ 3302.704290] iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345] Apr 1 17:17:41 Thecology kernel: [ 3614.322366] iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] Apr 1 17:20:07 Thecology kernel: [ 3760.096466] iSCSI: Discovery session from [127.0.0.1] Apr 1 17:20:08 Thecology kernel: [ 3760.452273] iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345] Apr 1 17:22:44 Thecology kernel: [ 3916.791102] iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0] messages on DS2: Apr 1 12:57:51 Sedmdesatka kernel: [435172.837699] iSCSI: TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION. Apr 1 12:57:58 Sedmdesatka entry.cgi_SYNO.Core.Upgrade.Server[1].check[1536]: smallupdate.cpp:413 small fix can't downgrade, org_version[1], new_version[1] Apr 1 13:04:00 Sedmdesatka kernel: [435542.052721] iSCSI: TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION. messages on DS3: Apr 1 17:12:28 Thecology kernel: [ 3301.163040] EXT_INFO: INIT Extent-Pool Apr 1 17:12:28 Thecology kernel: [ 3301.259652] RODSP_INFO: RODSPS Start-[50:46:5d:a3:93:07] Apr 1 17:12:30 Thecology kernel: [ 3302.958424] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION. Apr 1 17:20:08 Thecology kernel: [ 3760.706364] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION. I would be glad for any help. Thanks a lot. And of course I would like to thank Trantor and gnoBoot for their work. (And, lastly, I would like to apologize for a long post, somehow I am not able to explain things without using many words )
  3. Another motherboard to add to the list: Asus C60M1-I, AMD FCH A50M chipset, 6x SATA III. LAN OK, SATA OK, restart / shutdown OK. I had to switch SATA to 3G mode in BIOS.
  4. Hi and thanks, Andy, for making this possible. I am running XPEnology on Intel BLKD525MW (Atom D525, NM10 chipset), SATA OK, network OK. Restart/shutdown doesn't work (it shuts down, but after boot when logging in to DSM it writes "System is upgrading" instead, so I have to shut it down forcefully by holding the power button) USB drive shows as internal (so no eject choice) Tried USB WiFi dongle (EW-7811Un) and it works well, shows as wireless network and connects to it How about using two or more XPEnologys on the same network? They all have the same MAC, right?