• 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    


  • Content count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About NeoID

  • Rank
    Advanced Member
  1. DSM 6.1.5-15254

    - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: ESXi 6.5 - Additional comments: Took a long time for the NAS to get it's original IP back. Had to use Synology Assistant. DOCKER SEEMS BROKEN! JUST WSOD!
  2. Synology Drive

    Would appreciate it if anyone else could try the app on Android.
  3. Synology Drive

    Anyone managed to get the Android app to work when using a Letsencrypt certificate? All apps work fine except Drive.
  4. Repairing a crashed BTRFS volume

    I've been looking at dmesg and /proc/mdstat for the last couple of days. Today the rebuild did a second pass and now everything seems to be clean and working again! I guess my conclusion is.. make sure all cables are properly inserted and cool your HBA card.
  5. Repairing a crashed BTRFS volume

    I'm afraid you'r right about the rebuild taking only a single pass and something is wrong with my array... -_- Do you use a hypervisor or run baremetal? I have had these issues even on EXT4, so I doubts it's related to the file system.
  6. Repairing a crashed BTRFS volume

    I also use 3TB WD Red drives (10x ) in RAID 6. First of all I powered down my system and tested the drive on another machine. Since it was fine I didn't think that the crash was caused by it. To make sure, I've replaced the drive with another WD Red 3TB I had lying around. Also this drive "crashed" according to DSM after rebuilding for a day. I started noticing a pattern here. Every time I've started from scratch it has been the same disk bay that DSM was complaining about. The reason I didn't notice this sooner is that DSM sometimes changes the order of the disk (I don't remember if it happens on each boot or each install of DSM). However.. it was always the same bay causing issues. I finally removed the drive from the bay and connected it directly by SATA. For now everything seems to rebuild just fine (even though I don't see why it's currently rebuilding for the second time without any errors in between). I have also noticed that the HBA became very hot when rebuilding (and under heavy load), so that may also have something to do with this issue... So I've 3d printed a bracket and mounted a 120mm fan on top of the card. For now everything works smooth, so I just hope it doesn't restart the rebuild a third time or I think there's something wrong with DSM not being able to save the state of the volume somehow...
  7. A bad cable crashed my BTRFS volume the other day. I found the issue after a while and started the rebuild process after replacing the bad SATA cable. The rebuild took a few days to complete, but once it did, it restarted from 0% again. I have not received any other emails or notifications from DSM that anything is abnormal. Is it normal that the rebuild process need multiple passes to complete? I'm on ESXi and the boot drive is mounted as read-only once everything was up and running smoothly. First I thought the the rebuild restarted because the state couldn't be written back to the boot drive (I don't think it does), but it has been read-only since before the crash.. so I don't think it's related to this problem. Anyone who has been in this situation before and knows how many passes the rebuild process needs? I would never believe that it requires more than one, but who knows....
  8. DSM 6.x.x Loader

    I was about to make a video tutorial on how to upgrade to 6.1 with 1.02b after over a month with successful testing when suddenly one drive crashed. SMART values are fine and disk is ok, so it's false positive, upon rebuild another one bites to dust... also a false positive. I still suspect the 9201-16i PCI card to have some issues with XPenology, but the weird thing is that this only happens every 1-2 years. Could also be stress-related since I this time started a scrub hours before it happened. I have plenty of cooling, replaced all wires and drives, still the same thing happen a few month later. Since I'm on ESXi I don't think that anything else apart from the PCI controller, wires, drives and bay should matter but I'm left completely clueless on this one. Anyone else had sudden crashes for no apparent reason?
  9. DSM 6.x.x Loader

    Thanks, but I've figured it out. The problem was that I had to enbale hotplug cpu in esxi. Everything is working great now. I have the 9201-16i myself and it's great once you know about the setting.
  10. DSM 6.x.x Loader

    Awesome! Would love to buy one of those Threadripper CPU's
  11. I know this was required before, but what's the benefit of adding the serial port? Just debugging information and being able to do low-level stuff if SSH is down/disabled?
  12. DSM 6.x.x Loader

    because the loader packs a earlier kernel & ramdisk with it, and they are expected to be upgraded to latest version during install or upgrade process. that is how the loader is able to support multiple dsm version, and allows you to apply latest security fix, if kernel version code does not change. Thanks a lot for the clarification! I've also managed to get around the "general protection fault: 0000 [#1] SMP" issue when enabling SNMP or visiting the system info page. Seems like disabling the LSI cards BIOS and enabling CPU hotplug in ESXi will do the trick. I can't reproduce the bug anymore and everything works a lot better now. I now get a ton of these in dmesg, but it doesn't seem to do any hard (still trying to figure out how to remove them as well): [30377.275744] do_IRQ: 0.218 No irq handler for vector (irq -1)
  13. DSM 6.x.x Loader

    I'm curious.. I know the latest loader isn't compatible with AMD CPU's, but has anyone tried to use a AMD CPU on ESXi and this way get around this limitation? I wonder if that would actually work or if that also would fail. The reason I ask is because I suppose my i7-3770 to cause the "general protection fault" I've posted above. You would think that ESXi completely virtualizes the CPU and by default it does. However, once you enable passthrough the situation seems to change and the CPU is limited to the instructions it actually supports. It's like enabling passthrough punches a hole in the virtualization layer.... I'll investigate/prove this right or wrong when testing this with other PCI devices in passthrough mode instead of the current LSI SATA controller. So if anyone has tried using AMD on ESXi please let me know. My assumption is that it works well, but breaks horrible once you enable passthrough.
  14. DSM 6.x.x Loader

    Strange, I've always had the drive as independent without issues. Thanks a lot for the suggestion, seems to have worked!
  15. DSM 6.x.x Loader

    Another thing I've just noticed.. I've just upgraded from DSM 6.0 to 6.1 and every time the VM boots it's status is set as "Recoverable". It's able to repair it every time, but I have no idea why this should happen. Never encountered this on earlier versions of XPenology.