• 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    

VeNoM

Members
 View Profile  See their activity

  • Content count

    70

  • Joined

  • Last visited

Community Reputation

0 Neutral

About VeNoM

  • Rank
    Regular Member
  1. VeNoM started following How to compile the kernel, Building 5.0-4458 issues and 4.3 issues
  2. Try renaming /bin/umount

  3. Building 5.0-4458 issues

    VeNoM replied to VeNoM's topic in Archives

    Try installing sancome's version and look in /proc/kallsyms for funcSYNODiskRetryReport. If is't there, he has the solution. sancome's version still uses the mount for pcidevices ? cat /proc/kallsyms | grep -i funcSYNODiskRetryReport How did you fixed the pat file to bypass the checksum ?
  4. Also this build should work with LinuxKVM/WmWare for easier testing
  5. The mount fix doesn't work anymore ? I will test my dsmgeneric kernel module with the new protection.

  6. Building 5.0-4458 issues

    VeNoM replied to VeNoM's topic in Archives

    I will try to use the default kernel built by synology with modules for my VM to see if it passes the checksum. I do not have the time right now to investigate this. Anyone else ?

  7. Building 5.0-4458 issues

    VeNoM replied to VeNoM's topic in Archives

    Apparently Synology introduced a new checksum in 4458. When loaded, the synobios creates /proc/syno_cpu_arch. Jan 1 00:00:01 syslog: util_fhost.c:1204 Serial number is 0 out of size Jan 1 00:00:02 syslaog: format start, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:02 syslog: ninstaller.c:717 Dev: sda, DiskPath: /dev/sda, Check Partitions: 1 Jan 1 00:00:02 syslog: ninstaller.c:577 failed to get upnpmodelname from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:00:02 syslog: ninstaller.c:584 failed to get buildnumber from [/tmpMnt1234/etc.defaults/VERSION]. Jan 1 00:00:02 syslog: ../libsynosdk/lib/system/system_platform_get.c:35 failed to get unique from /tmpMnt1234/etc.defaults/synoinfo.conf errno=[0x0900] Jan 1 00:00:02 syslog: ninstaller.c:600 failed to get platform from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:00:02 syslog: ../libsynosdk/lib/system/system_max_align_get.c:85 [/tmpMnt1234/.system_info/pgsql_alignment] doesn't exist, check model name for alignment Jan 1 00:00:02 syslog: ../libsynosdk/lib/system/system_endian_get.c:61 [/tmpMnt1234/.system_info/endian] doesn't exist, check model name for endian Jan 1 00:00:02 syslog: ../libsynosdk/lib/system/system_bit_get.c:57 [/tmpMnt1234/.system_info/bits] doesn't exist, check model name for bits Jan 1 00:00:02 syslog: ninstaller.c:839(BlCheckSystemStatusRAID): Has Syno Partition = 1, System Status: 2 Jan 1 00:00:02 syslog: ninstaller.c:846(BlCheckSystemStatusRAID): gszUpgradeVolDev = /dev/md0 Jan 1 00:00:02 syslog: ninstaller.c:848(BlCheckSystemStatusRAID): gszUpgradeVolMnt = /tmpData Jan 1 00:00:02 syslog: ninstaller.c:849(BlCheckSystemStatusRAID): we use md0 to upgrade. Jan 1 00:00:02 syslog: ninstaller.c:1504 gblSupportRaid: 1, gSysStatus: 2, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 1 00:00:02 syslog: ninstaller.c:2585 CreateDataVol=[0], CheckBadblocks=[0] Jan 1 00:00:02 syslog: ninstaller.c:2651(ErrFHOSTDoFdiskFormat) retv=[0] Jan 1 00:00:02 syslog: ErrFHOSTTcpResponseCmd: cmd=[2], ulErr=[0] Jan 1 00:00:02 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:02 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:02 syslog: index=[0], ulRate=[101] Jan 1 00:00:02 kernel: [ 285.784509] md1: detected capacity change from 2147418112 to 0 Jan 1 00:00:02 kernel: [ 285.785248] md: md1: set sda2 to auto_remap [0] Jan 1 00:00:02 kernel: [ 285.785902] md: md1 stopped. Jan 1 00:00:02 kernel: [ 285.786493] md: unbind Jan 1 00:00:02 kernel: [ 285.793025] md: export_rdev(sda2) Jan 1 00:00:02 kernel: [ 285.798581] md0: detected capacity change from 2549940224 to 0 Jan 1 00:00:02 kernel: [ 285.799750] md: md0: set sda1 to auto_remap [0] Jan 1 00:00:02 kernel: [ 285.800802] md: md0 stopped. Jan 1 00:00:02 kernel: [ 285.801735] md: unbind Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 default.hotplug[6143]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 default.hotplug[6146]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6154]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 default.hotplug[6168]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6176]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 kernel: [ 285.807034] md: export_rdev(sda1) Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 default.hotplug[6221]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6234]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6224]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:02 default.hotplug[6246]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6256]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6349]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6348]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6382]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6400]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6405]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:02 default.hotplug[6407]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:04 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:04 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:04 syslog: index=[0], ulRate=[102] Jan 1 00:00:05 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:05 default.hotplug[6463]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:05 kernel: [ 289.056405] md: bind Jan 1 00:00:05 kernel: [ 289.057299] bio: create slab at 1 Jan 1 00:00:05 kernel: [ 289.057975] md/raid1:md0: active with 1 out of 12 mirrors Jan 1 00:00:05 kernel: [ 289.058692] md0: detected capacity change from 0 to 2549940224 Jan 1 00:00:05 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:05 default.hotplug[6480]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:06 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:06 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:06 syslog: index=[0], ulRate=[103] Jan 1 00:00:08 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:08 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:08 syslog: index=[0], ulRate=[104] Jan 1 00:00:08 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:08 default.hotplug[6496]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:08 kernel: [ 292.118088] md: bind Jan 1 00:00:08 kernel: [ 292.118864] md/raid1:md1: active with 1 out of 12 mirrors Jan 1 00:00:08 kernel: [ 292.119565] md1: detected capacity change from 0 to 2147418112 Jan 1 00:00:08 syslog: raidtool.c:419 system inited on [/dev/sda1 ], [/dev/sda2 ] Jan 1 00:00:08 kernel: [ 292.121560] md1: unknown partition table Jan 1 00:00:08 syslog: ../libsynosdk/lib/external/external_disk_port_check.c:87 expected sdx or /dev/sdx, not md, not match any port type Jan 1 00:00:08 default.hotplug[6513]: couldn't exec /usr/syno/hotplug/block.agent Jan 1 00:00:08 kernel: [ 292.137124] md0: unknown partition table Jan 1 00:00:10 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:10 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:10 syslog: index=[0], ulRate=[100] Jan 1 00:00:12 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:12 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:12 syslog: index=[0], ulRate=[100] Jan 1 00:00:12 kernel: [ 296.111885] EXT4-fs (md0): barriers disabled Jan 1 00:00:12 kernel: [ 296.127975] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:12 syslog: ninstaller.c:2605 /bin/mount /dev/md0 /tmpRoot Jan 1 00:00:12 kernel: [ 296.186880] EXT4-fs (md0): barriers disabled Jan 1 00:00:12 kernel: [ 296.197544] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:12 syslog: ninstaller.c:2607 mount root partition failed. Jan 1 00:00:12 syslog: ninstaller.c:2646 retv=[0] Jan 1 00:00:14 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:14 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] ret:0 Jan 1 00:00:14 syslog: ninstaller.c:2520(ErrFHOSTUpdateMkfsProgress) gInstallStage=[3] , process=[/dev/md0] Jan 1 00:00:14 syslog: ninstaller.c:2524(ErrFHOSTUpdateMkfsProgress) switch to PROG_FORMAT_DATA Jan 1 00:00:14 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[4] ret:0 Jan 1 00:00:14 syslog: ninstaller.c:2558(ErrFHOSTUpdateMkfsProgress) skip format data volume... Jan 1 00:00:14 syslog: index=[1], ulRate=[100] Jan 1 00:00:16 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:16 syslog: ninstaller.c:2483(ErrFHOSTUpdateMkfsProgress) gInstallStage=[4] ret:0 Jan 1 00:00:16 syslog: ninstaller.c:2558(ErrFHOSTUpdateMkfsProgress) skip format data volume... Jan 1 00:00:16 syslog: index=[1], ulRate=[100] Jan 1 00:00:18 syslog: pat start, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:18 kernel: [ 301.805297] EXT4-fs (md0): barriers disabled Jan 1 00:00:18 kernel: [ 301.858438] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:18 syslog: ninstaller.c:1709(ErrFHOSTReceiveUpgradeFile): szUpgradeFile = /tmpData//upd@te.pat Jan 1 00:00:23 syslog: ninstaller.c:1740(ErrFHOSTReceiveUpgradeFile) cRead=[4], ulFileSize=[183347200] Jan 1 00:00:24 syslog: Estimated time =[2] Jan 1 00:00:25 syslog: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:25 syslog: Starting ErrFHOSTDoUpgrade()... Jan 1 00:00:25 syslog: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:25 syslog: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:25 syslog: ninstaller.c:2702(ErrFHOSTDoUpgrade) retv=[0] Jan 1 00:00:25 syslog: ErrFHOSTDoUpgrade() Done Jan 1 00:00:25 syslog: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:25 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:25 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:25 syslog: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:25 syslog: Untar /tmpData/upd@te.pat...cmd=[/bin/tar xpf "/tmpData/upd@te.pat" -C /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:27 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:27 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:29 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:29 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:31 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:31 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:33 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:33 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:35 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:35 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:37 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:37 syslog: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:37 syslog: Verify checksum of [/tmpData/upd@te]... Jan 1 00:00:37 syslog: ErrFHOSTCheckUpgradeFile: Fail to verify checksum of /tmpData/upd@te...(retv=0x3800) Jan 1 00:00:37 syslog: ErrFHOSTCheckUpgradeFile: set error code cmd=[/bin/echo "A:-13:" > /tmp/update.progress] Jan 1 00:00:37 syslog: ninstaller.c:2692(ErrFHOSTDoUpgrade) err=[-1] Jan 1 00:00:39 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:39 syslog: alz=[0], prg=[0], cfg=[0], retv=[-13] Jan 1 00:00:39 syslog: ninstaller.c:2197(ErrFHOSTUpdaterProgress) retv=-13 Jan 1 00:00:41 syslog: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:41 syslog: alz=[0], prg=[0], cfg=[0], retv=[-13] Jan 1 00:00:41 syslog: ninstaller.c:2197(ErrFHOSTUpdaterProgress) retv=-13 Jan 1 00:00:41 syslog: ninstaller.c:1541(ErrFHOSTNetInstaller) read socket fail, ret=[0], errno=[10] Jan 1 00:00:41 syslog: ninstaller.c:1625(ErrFHOSTNetInstaller) retSel=[1] err=(10)[No child processes] Jan 1 00:00:41 syslog: ninstaller.c:1640(ErrFHOSTNetInstaller) Jan 1 00:00:41 syslog: Return from TcpServer() Jan 1 00:00:01 syslog: util_fhost.c:1204 Serial number is 0 out of size Jan 1 00:00:16 syslog: Return from TcpServer() Jan 1 00:01:19 syslog: util_fhost.c:1204 Serial number is 0 out of size Jan 1 00:01:22 syslog: ninstaller.c:717 Dev: sda, DiskPath: /dev/sda, Check Partitions: 1 Jan 1 00:01:22 syslog: ninstaller.c:577 failed to get upnpmodelname from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:01:22 syslog: ninstaller.c:584 failed to get buildnumber from [/tmpMnt1234/etc.defaults/VERSION]. Jan 1 00:01:22 syslog: ../libsynosdk/lib/system/system_platform_get.c:35 failed to get unique from /tmpMnt1234/etc.defaults/synoinfo.conf errno=[0x0900] Jan 1 00:01:22 syslog: ninstaller.c:600 failed to get platform from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:01:22 syslog: ../libsynosdk/lib/system/system_max_align_get.c:85 [/tmpMnt1234/.system_info/pgsql_alignment] doesn't exist, check model name for alignment Jan 1 00:01:22 syslog: ../libsynosdk/lib/system/system_endian_get.c:61 [/tmpMnt1234/.system_info/endian] doesn't exist, check model name for endian Jan 1 00:01:22 syslog: ../libsynosdk/lib/system/system_bit_get.c:57 [/tmpMnt1234/.system_info/bits] doesn't exist, check model name for bits Jan 1 00:01:22 syslog: ninstaller.c:839(BlCheckSystemStatusRAID): Has Syno Partition = 1, System Status: 2 Jan 1 00:01:22 syslog: ninstaller.c:846(BlCheckSystemStatusRAID): gszUpgradeVolDev = /dev/md0 Jan 1 00:01:22 syslog: ninstaller.c:848(BlCheckSystemStatusRAID): gszUpgradeVolMnt = /tmpData Jan 1 00:01:22 syslog: ninstaller.c:849(BlCheckSystemStatusRAID): we use md0 to upgrade. Jan 1 00:01:22 syslog: ninstaller.c:1504 gblSupportRaid: 1, gSysStatus: 2, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 1 00:01:26 syslog: /source/libsynosdk/lib/partition/partition_check_layout.c:52 sd: dont contain partition [1] Jan 1 00:01:28 syslog: ninstaller.c:717 Dev: sda, DiskPath: /dev/sda, Check Partitions: 1 Jan 1 00:01:28 syslog: ninstaller.c:577 failed to get upnpmodelname from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:01:28 syslog: ninstaller.c:584 failed to get buildnumber from [/tmpMnt1234/etc.defaults/VERSION]. Jan 1 00:01:28 syslog: ../libsynosdk/lib/system/system_platform_get.c:35 failed to get unique from /tmpMnt1234/etc.defaults/synoinfo.conf errno=[0x0900] Jan 1 00:01:28 syslog: ninstaller.c:600 failed to get platform from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:01:28 syslog: ../libsynosdk/lib/system/system_max_align_get.c:85 [/tmpMnt1234/.system_info/pgsql_alignment] doesn't exist, check model name for alignment Jan 1 00:01:28 syslog: ../libsynosdk/lib/system/system_endian_get.c:61 [/tmpMnt1234/.system_info/endian] doesn't exist, check model name for endian Jan 1 00:01:28 syslog: ../libsynosdk/lib/system/system_bit_get.c:57 [/tmpMnt1234/.system_info/bits] doesn't exist, check model name for bits Jan 1 00:01:28 syslog: ninstaller.c:839(BlCheckSystemStatusRAID): Has Syno Partition = 1, System Status: 2 Jan 1 00:01:28 syslog: ninstaller.c:846(BlCheckSystemStatusRAID): gszUpgradeVolDev = /dev/md0 Jan 1 00:01:28 syslog: ninstaller.c:848(BlCheckSystemStatusRAID): gszUpgradeVolMnt = /tmpData Jan 1 00:01:28 syslog: ninstaller.c:849(BlCheckSystemStatusRAID): we use md0 to upgrade. Jan 1 00:01:28 syslog: ninstaller.c:1504 gblSupportRaid: 1, gSysStatus: 2, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 1 00:01:32 syslog: /source/libsynosdk/lib/partition/partition_check_layout.c:52 sd: dont contain partition [1]

  8. Building 5.0-4458 issues

    VeNoM posted a topic in Archives

    I have set up a VM for 5.0 testing and I have some issues. - funcSYNODiskRetryReport unknown symbol in synobios - the checksum for pat contents fails for some reason Kernel patch --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -7414,7 +7414,7 @@ int (*funcSYNODeepSleepEvent)(unsigned int, unsigned int) = NULL; EXPORT_SYMBOL(funcSYNODeepSleepEvent); -#ifdef MY_DEF_HERE +#if (defined(MY_DEF_HERE) || defined(XPENOLOGY)) int (*funcSYNOSendEboxRefreshEvent)(int portIndex) = NULL; EXPORT_SYMBOL(funcSYNOSendEboxRefreshEvent); #endif --- a/drivers/ata/sata_mv.c +++ b/drivers/ata/sata_mv.c @@ -3706,6 +3706,7 @@ /*FIXME - Too brutal and directly, should separate into levels*/ void syno_sata_mv_gpio_write(u8 blFaulty, const unsigned short hostnum) { +#ifndef XPENOLOGY struct Scsi_Host *shost = scsi_host_lookup(hostnum); struct ata_port *ap = NULL; void __iomem *host_mmio = NULL; @@ -3740,6 +3741,8 @@ if (NULL != shost) { scsi_host_put(shost); } +#endif +END: return; } EXPORT_SYMBOL(syno_sata_mv_gpio_write); --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -618,7 +618,9 @@ ( pin < 0 || pin >= 96 ) || NULL == pValue ) { +#ifndef XPENOLOGY printk("parameter error. gpiobase=%08X, pin=%d, pValue=%p\n", gpiobase, pin, pValue); +#endif goto END; } --- a/drivers/tty/vt/vt.c +++ b/drivers/tty/vt/vt.c @@ -2474,7 +2474,7 @@ return kmsg_con; } -#ifndef MY_ABC_HERE +#if (defined(MY_DEF_HERE) || defined(XPENOLOGY)) /* * Console on virtual terminal * @@ -2574,7 +2574,7 @@ } #endif -#ifndef MY_ABC_HERE +#if (!defined(MY_ABC_HERE) || defined(XPENOLOGY)) static struct tty_driver *vt_console_device(struct console *c, int *index) { *index = c->index ? c->index-1 : fg_console; @@ -2942,7 +2942,7 @@ console_unlock(); -#ifndef MY_ABC_HERE +#if (!defined(MY_ABC_HERE) || defined(XPENOLOGY)) #ifdef CONFIG_VT_CONSOLE register_console(&vt_console_driver); #endif --- a/fs/compat_ioctl.c +++ b/fs/compat_ioctl.c @@ -1760,13 +1760,14 @@ sprintf(buf,"'%c'", (cmd>>_IOC_TYPESHIFT) & _IOC_TYPEMASK); if (!isprint(buf[1])) sprintf(buf, "%02x", buf[1]); +#ifndef XPENOLOGY compat_printk("ioctl32(%s:%d): Unknown cmd fd(%d) " "cmd(%08x){t:%s;sz:%u} arg(%08x) on %s\n", current->comm, current->pid, (int)fd, (unsigned int)cmd, buf, (cmd >> _IOC_SIZESHIFT) & _IOC_SIZEMASK, (unsigned int)arg, fn); - +#endif if (path) free_page((unsigned long)path); } --- a/include/linux/syno_user.h +++ b/include/linux/syno_user.h @@ -2,6 +2,11 @@ #ifndef __SYNO_USER_H_ #define __SYNO_USER_H_ + +/** + * XPENOLOGY + */ +#define XPENOLOGY /** * Dsc: Synology multimedia server feature. For indexing video, photo, --- a/kernel/sysctl.c +++ b/kernel/sysctl.c @@ -228,7 +228,7 @@ int (*funcSYNOGetHwCapability)(CAPABILITY *) = NULL; EXPORT_SYMBOL(funcSYNOGetHwCapability); -#ifdef MY_DEF_HERE +#if (defined(MY_DEF_HERE) || defined(XPENOLOGY)) EUNIT_PWRON_TYPE (*funcSynoEunitPowerctlType)(void) = NULL; EXPORT_SYMBOL(funcSynoEunitPowerctlType); #endif

  9. DSM 5.0 - 4458 is released today

    VeNoM replied to squallelf's topic in Readers News & Rumours

    I got a new kernel working including patches + my dsmgeneric module. file arch/x86/boot/bzImage arch/x86/boot/bzImage: Linux kernel x86 boot executable bzImage, version 3.2.40 (aaa@bbb) #1 SMP Thu Mar 13 14:40:01 EET 2014, RO-rootFS, swap_dev 0x3, Normal VGA I see that rd.gz in the DS3612xs is not a gzip file. Any ideeas ? LE : lzma/cpio mv rd.gz rd.lzma lzma -d rd.lzma cpio -idv < rd

  10. DSM 5.0 - 4458 is released today

    VeNoM replied to squallelf's topic in Readers News & Rumours

    Any new security checks in 5.0 ?

  11. 4.3 issues

    VeNoM replied to VeNoM's topic in DSM 5.2 and earlier (Legacy)

    Can somebody with Trantor's build give me the output of df -h ?

  12. 4.3 issues

    VeNoM replied to VeNoM's topic in DSM 5.2 and earlier (Legacy)

    You should wait to see if this update is safe for Trantor's build. If it's ok, then : Go to update, click download. Then go to scheduled tasks and create a custom task : sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info Run this task. Then go to update and hit the update button.

  13. 4.3 issues

    VeNoM replied to VeNoM's topic in DSM 5.2 and earlier (Legacy)

    DSM 4.3-3810 Update 2 available. I just updated and with my mod it seems ok.

  14. 4.3 issues

    VeNoM replied to VeNoM's topic in DSM 5.2 and earlier (Legacy)

    3810 Update 1 is available. Be carefull. (2013/11/20) Compatibility and Installation DSM 4.3-3810 Update 1 can only be installed on Synology products running DSM 4.3-3810 via DSM Update. Please log in to DSM and go to Control Panel > DSM Update to install the update. Fixed Issues Fixed a system security issue. Improved the compatibility of file uploading with Internet Explorer 11 in File Station.

  15. 4.3 issues

    VeNoM replied to VeNoM's topic in DSM 5.2 and earlier (Legacy)

    We can maybe block this with iptables ? No. Syno can detect this mod in the next update by simply checking /proc/mounts and just do a "umount /proc/bus/pci"
  16. Or simply change the boot loader by adding parameters to the kernel and comment cksum, vender and hw_model. title SYNOLOGY root (hd0,1) # cksum /grub_cksum.syno # vender /vender show # hw_model kernel /zImage root=/dev/md0 ihd_num=0 netif_num=2 syno_hw_version=DS3612xs mac1=00113208d68a mac2=00113208d68b mac3=004d9469c492 mac4=004d9469c493 sn=B3J4N00001 initrd /rd.gz