Jump to content
XPEnology Community

filippo333

Member
 View Profile  See their activity

  • Posts

    156

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by filippo333

    Jun's Alpha Loader for DSM 6.1

    in DSM 6.x

    Posted

    Log for those interested:

     

    [spoiler=Logs]2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: RSDP 0x00000000000F05B0 00024 (v02 ALASKA)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: XSDT 0x00000000B3DFE0A0 000BC (v01 ALASKA A M I 01072009 AMI 00010013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: FACP 0x00000000B3E26DB0 00114 (v06 ALASKA A M I 01072009 AMI 00010013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI BIOS Bug: Warning: FADT (revision 6) is longer than ACPI 5.0 version, truncating length 276 to 268 (20130328/tbfadt-311)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI Error: Gpe0Block - 32-bit FADT register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits max, truncating (20130328/tbfadt-202)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: DSDT 0x00000000B3DFE1F8 28BB2 (v02 ALASKA A M I 01072009 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: FACS 0x00000000C2D29C40 00040

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: APIC 0x00000000B3E26EC8 00084 (v03 ALASKA A M I 01072009 AMI 00010013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: FPDT 0x00000000B3E26F50 00044 (v01 ALASKA A M I 01072009 AMI 00010013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: DBG2 0x00000000B3E32650 00054 (v00 INTEL 00000002 MSFT 0000005F)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: MCFG 0x00000000B3E26FF0 0003C (v01 ALASKA A M I 01072009 MSFT 00000097)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E27030 00390 (v01 SataRe SataTabl 00001000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: FIDT 0x00000000B3E273C0 0009C (v01 ALASKA A M I 01072009 AMI 00010013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E27460 03041 (v02 SaSsdt SaSsdt 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2A4A8 02544 (v02 PegSsd PegSsdt 00001000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: HPET 0x00000000B3E2C9F0 00038 (v01 INTEL SKL 00000001 MSFT 0000005F)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2CA28 00E3B (v02 INTEL Ther_Rvp 00001000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2D868 00B19 (v02 INTEL xh_rvp08 00000000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: UEFI 0x00000000B3E2E388 00042 (v01 INTEL EDK2 00000002 01000013)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2E3D0 00EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: LPIT 0x00000000B3E2F2B0 00094 (v01 INTEL SKL 00000000 MSFT 0000005F)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: WSMT 0x00000000B3E2F348 00028 (v01 INTEL SKL 00000000 MSFT 0000005F)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2F370 0029F (v02 INTEL sensrhub 00000000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: SSDT 0x00000000B3E2F610 03002 (v02 INTEL PtidDevc 00001000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] ACPI: DBGP 0x00000000B3E32618 00034 (v01 INTEL 00000002 MSFT 0000005F)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Zone ranges:

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] DMA [mem 0x00001000-0x00ffffff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Normal [mem 0x100000000-0x436ffffff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Movable zone start for each node

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Early memory node ranges

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0x00001000-0x0009bfff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0x00100000-0xb3dfdfff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0xb3e33000-0xb41d3fff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0xb41d6000-0xc0e2dfff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0xc2547000-0xc2701fff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0xc32ff000-0xc32fffff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] node 0: [mem 0x100000000-0x436ffffff]

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4104442

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Power on seq num: 0

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Synology Hardware Version: DS3617xs-j

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Vender format version: 2

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Serial Number: A8ODN02468

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Mac1: 00006c0bf764

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.000000] Internal netif num: 1

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.005000] tsc: Unable to calibrate against PIT

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.018479] ACPI: All ACPI Tables successfully acquired

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.107883] raid6: sse2x1 gen() 12765 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.124890] raid6: sse2x1 xor() 9228 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.141898] raid6: sse2x2 gen() 16082 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.158902] raid6: sse2x2 xor() 11046 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.175911] raid6: sse2x4 gen() 16996 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.192917] raid6: sse2x4 xor() 12468 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.209923] raid6: avx2x1 gen() 25718 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.226928] raid6: avx2x2 gen() 29234 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.243934] raid6: avx2x4 gen() 32777 MB/s

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.243935] raid6: using algorithm avx2x4 gen() (32777 MB/s)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.243935] raid6: using avx2x2 recovery algorithm

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.256169] ACPI: Executed 36 blocks of module-level executable AML code

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.275166] ACPI: SSDT 0x00000000C14E3898 003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.275674] ACPI: Executed 1 blocks of module-level executable AML code

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.275676] ACPI: Dynamic OEM Table Load:

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.275677] ACPI: SSDT 0x0000000000000000 003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.275763] ACPI: SSDT 0x00000000C24F8398 00759 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.276266] ACPI: Executed 1 blocks of module-level executable AML code

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.276268] ACPI: Dynamic OEM Table Load:

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.276269] ACPI: SSDT 0x0000000000000000 00759 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.283270] ACPI: SSDT 0x00000000C14E3018 0065C (v02 PmRef ApIst 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.283819] ACPI: Executed 1 blocks of module-level executable AML code

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.283820] ACPI: Dynamic OEM Table Load:

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.283821] ACPI: SSDT 0x0000000000000000 0065C (v02 PmRef ApIst 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.286185] ACPI: SSDT 0x00000000C14E3DD8 0018A (v02 PmRef ApCst 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.286697] ACPI: Executed 1 blocks of module-level executable AML code

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.286699] ACPI: Dynamic OEM Table Load:

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.286700] ACPI: SSDT 0x0000000000000000 0018A (v02 PmRef ApCst 00003000 INTL 20160422)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 0.311842] ACPI: Enabled 4 GPEs in block 00 to 7F

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 1.335112] bounce pool size: 64 pages

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 1.335541] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.354910] broadwell_synobios: module license 'Synology Inc.' taints kernel.

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.354912] Disabling lock debugging due to kernel taint

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.355298] 2017-5-22 7:0:21 UTC

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.355302] Brand: Synology

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.355303] Model: DS-3617xs

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.355304] set group disks wakeup number to 4, spinup time deno 7

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.359735] synobios: unload

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.438803] md: invalid raid superblock magic on sda3

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.443942] md: sda3 does not have a valid v0.90 superblock, not importing!

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.509131] md: invalid raid superblock magic on sdb3

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.514254] md: sdb3 does not have a valid v0.90 superblock, not importing!

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.591271] md: invalid raid superblock magic on sdc3

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.596393] md: sdc3 does not have a valid v0.90 superblock, not importing!

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.596398] md: sda2 has different UUID to sda1

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.596400] md: sdb2 has different UUID to sda1

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 2.596403] md: sdc2 has different UUID to sda1

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 4.757300] usb 2-3: Parent hub missing LPM exit latency info. Power management will be impacted.

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.527504] sd 4:0:0:0: [synoboot] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.533472] sd 4:0:0:0: [synoboot] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.541566] sd 4:0:0:0: [synoboot] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.547478] sd 4:0:0:0: [synoboot] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.564075] sd 4:0:0:0: [synoboot] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.570093] sd 4:0:0:0: [synoboot] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.760722] sd 5:0:0:0: [sdu] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.766168] sd 5:0:0:0: [sdu] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.773731] sd 5:0:0:0: [sdu] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.779238] sd 5:0:0:0: [sdu] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.787040] sd 5:0:0:0: [sdu] No Caching mode page found

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 5.792506] sd 5:0:0:0: [sdu] Assuming drive cache: write through

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 6.002365] Got empty serial number. Generate serial number from product.

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 6.002434] usb 1-7: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

    2017-05-22T08:00:31+01:00 SR2 kernel: [ 6.002436] usb 1-7: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes

    2017-05-22T08:00:31+01:00 SR2 s70_synocheckhw: fan/fan_adjust_config_full_speed.c:90 Cannot find HIGH fan table.

    2017-05-22T08:00:32+01:00 SR2 kernel: [ 13.700802] zram: module is from the staging directory, the quality is unknown, you have been warned.

    2017-05-22T08:00:33+01:00 SR2 synoservice: synoservice.c:1559 pause gcpd due to require service cupsd runkey is stop

    2017-05-22T08:00:33+01:00 SR2 root: mkcert: Verifying certificate in [/usr/syno/etc/certificate/system/default].

    2017-05-22T08:00:33+01:00 SR2 [ 15.272765] init: syno-auth-check main process (5373) killed by TERM signal

    2017-05-22T08:00:35+01:00 SR2 kernel: [ 16.377586] 2017-5-22 7:0:35 UTC

    2017-05-22T08:00:35+01:00 SR2 kernel: [ 16.377591] Brand: Synology

    2017-05-22T08:00:35+01:00 SR2 kernel: [ 16.377592] Model: DS-3617xs

    2017-05-22T08:00:35+01:00 SR2 kernel: [ 16.377593] set group disks wakeup number to 4, spinup time deno 7

    2017-05-22T08:00:35+01:00 SR2 interface-catcher: eth0 (inet 192.168.1.240 netmask 255.255.255.0 mtu 1500) is added

    2017-05-22T08:00:35+01:00 SR2 interface-catcher: lo (inet 127.0.0.1 netmask 255.0.0.0 ) is added

    2017-05-22T08:00:35+01:00 SR2 synonetdtool: dbus_client.cpp:216 Failed to send message: The name com.synology.net was not provided by any .service files (-1)

    2017-05-22T08:00:35+01:00 SR2 synonetdtool: dbus_client.cpp:216 Failed to send message: The name com.synology.net was not provided by any .service files (-1)

    2017-05-22T08:00:36+01:00 SR2 synonetdtool: SYSTEM: Last message 'dbus_client.cpp:216 ' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:36+01:00 SR2 synostorage: synostorage_int_disk.c:279 Disk [sda] info cache generated

    2017-05-22T08:00:36+01:00 SR2 synostorage: synostorage_int_disk.c:279 Disk [sdc] info cache generated

    2017-05-22T08:00:36+01:00 SR2 synostorage: synostorage_int_disk.c:279 Disk [sdb] info cache generated

    2017-05-22T08:00:36+01:00 SR2 spacetool.shared: spacetool.c:3106 [info] Activate all VG

    2017-05-22T08:00:36+01:00 SR2 spacetool.shared: spacetool.c:3160 space: [/dev/md2]

    2017-05-22T08:00:36+01:00 SR2 spacetool.shared: spacetool.c:3186 space: [/dev/md2], ndisk: [3]

    2017-05-22T08:00:37+01:00 SR2 spacetool.shared: hotspare_repair_config_set.c:36 Failed to hup synostoraged

    2017-05-22T08:00:37+01:00 SR2 synovspace: virtual_space_conf_check.c:78 [iNFO] "PASS" checking configuration of virtual space [FCACHE], app: [1]

    2017-05-22T08:00:37+01:00 SR2 synovspace: virtual_space_conf_check.c:74 [iNFO] No implementation, skip checking configuration of virtual space [HA]

    2017-05-22T08:00:37+01:00 SR2 synovspace: virtual_space_conf_check.c:74 [iNFO] No implementation, skip checking configuration of virtual space [sNAPSHOT_ORG]

    2017-05-22T08:00:37+01:00 SR2 synovspace: vspace_wrapper_load_all.c:76 [iNFO] No virtual layer above space: [/volume1] / [/dev/md2]

    2017-05-22T08:00:39+01:00 SR2 kernel: [ 20.657356] BTRFS: has skinny extents

    2017-05-22T08:00:40+01:00 SR2 synocheckhotspare: synocheckhotspare.c:150 [iNFO] No hotspare config, skip hotspare config check. [0x2000 virtual_space_layer_get.c:97]

    2017-05-22T08:00:41+01:00 SR2 kernel: [ 22.630025] Get empty minor:104

    2017-05-22T08:00:41+01:00 SR2 syno_hdd_util: Model:[HTS721010A9E630], Firmware:[JB0OA3J0], S/N:[JR10006P10BSJE] in [/dev/sdc] is not ssd

    2017-05-22T08:00:41+01:00 SR2 syno_hdd_util: Model:[HTS721010A9E630], Firmware:[JB0OA3J0], S/N:[JR10006PHB1H9E] in [/dev/sdb] is not ssd

    2017-05-22T08:00:41+01:00 SR2 syno_hdd_util: Model:[HTS721010A9E630], Firmware:[JB0OA3B0], S/N:[JG40006PG8WW2C] in [/dev/sda] is not ssd

    2017-05-22T08:00:42+01:00 SR2 synoiscsiep: iscsi_start_all.cpp:93 Successfully started iSCSI service.

    2017-05-22T08:00:43+01:00 SR2 synodrivehook: synodrivehook.cpp:210 Failed [FALSE == SLIBServiceIsRunning(SZ_PGSQL_SERVICE_NAME)], err=No such file or directory

    2017-05-22T08:00:44+01:00 SR2 manutild: manutild.c:2896 /.start_manutild not exist, finish manutild

    2017-05-22T08:00:44+01:00 SR2 synousbdisk: RCClean succeeded

    2017-05-22T08:00:44+01:00 SR2 root: mkcert: Verifying certificate in [/usr/syno/etc/certificate/system/default].

    2017-05-22T08:00:45+01:00 SR2 synodrivehook: synodrivehook.cpp:210 Failed [FALSE == SLIBServiceIsRunning(SZ_PGSQL_SERVICE_NAME)], err=No such file or directory

    2017-05-22T08:00:46+01:00 SR2 [ 27.426231] init: iscsi_pluginserverd main process (9526) terminated with status 255

    2017-05-22T08:00:46+01:00 SR2 [ 27.426258] init: iscsi_pluginserverd main process ended, respawning

    2017-05-22T08:00:46+01:00 SR2 hotplugd: hotplugd.c:1092 failed get usb status from usb config, DEVICE=/proc/bus/usb/002/002, usbid=1058:259d:57584A314139364B44484854 [0x2200 file_get_section_value.c:28]

    2017-05-22T08:00:46+01:00 SR2 hotplugd: hotplugd.c:1335 ##### ACTION:add

    2017-05-22T08:00:46+01:00 SR2 hotplugd: DEVNAME:sdu

    2017-05-22T08:00:46+01:00 SR2 hotplugd: DEVICE:/proc/bus/usb/002/002

    2017-05-22T08:00:46+01:00 SR2 hotplugd: DEVGUID:57584A314139364B444848540

    2017-05-22T08:00:46+01:00 SR2 hotplugd: DEVPATH:sdu

    2017-05-22T08:00:46+01:00 SR2 hotplugd: SUBSYSTEM:block

    2017-05-22T08:00:46+01:00 SR2 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host5/target5:0:0/5:0:0:0

    2017-05-22T08:00:46+01:00 SR2 hotplugd: scemd_connector/scemd_connector.c:134 Fail to sendto() for scemd connector client.

    2017-05-22T08:00:46+01:00 SR2 hotplugd: hotplugd.c:1478 ==== USB disk [sdu] plugged in ====

    2017-05-22T08:00:46+01:00 SR2 hotplugd: hotplugd.c:1479 goto USB disk, szDeviceName=sdu

    2017-05-22T08:00:46+01:00 SR2 hotplugd: external_storage_parts_vol_info_get.c:98 Dev:sdu cannot find PostfixNumber.

    2017-05-22T08:00:47+01:00 SR2 synocheckshare: synocheckshare_vol_mount.c:47 Export Share [uSB] [/dev/sdu1] [/volumeUSB1/usbshare]

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1335 ##### ACTION:add

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVNAME:sda

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVGUID:JG40006PG8WW2C0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVPATH:sda

    2017-05-22T08:00:51+01:00 SR2 hotplugd: SUBSYSTEM:block

    2017-05-22T08:00:51+01:00 SR2 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: scemd_connector/scemd_connector.c:134 Fail to sendto() for scemd connector client.

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1431 ==== SATA disk [sda] hotswap [add] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sda 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sda 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1452 ==== SATA disk [sda] Model: [HTS721010A9E630 ] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1453 ==== SATA disk [sda] Serial number: [JG40006PG8WW2C] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1454 ==== SATA disk [sda] Firmware version: [JB0OA3B0] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1335 ##### ACTION:add

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVNAME:sdb

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVGUID:JR10006PHB1H9E0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVPATH:sdb

    2017-05-22T08:00:51+01:00 SR2 hotplugd: SUBSYSTEM:block

    2017-05-22T08:00:51+01:00 SR2 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: scemd_connector/scemd_connector.c:134 Fail to sendto() for scemd connector client.

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1431 ==== SATA disk [sdb] hotswap [add] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdb 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sdb 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1452 ==== SATA disk [sdb] Model: [HTS721010A9E630 ] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1453 ==== SATA disk [sdb] Serial number: [JR10006PHB1H9E] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1454 ==== SATA disk [sdb] Firmware version: [JB0OA3J0] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1335 ##### ACTION:add

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVNAME:sdc

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVGUID:JR10006P10BSJE0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: DEVPATH:sdc

    2017-05-22T08:00:51+01:00 SR2 hotplugd: SUBSYSTEM:block

    2017-05-22T08:00:51+01:00 SR2 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0

    2017-05-22T08:00:51+01:00 SR2 hotplugd: scemd_connector/scemd_connector.c:134 Fail to sendto() for scemd connector client.

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1431 ==== SATA disk [sdc] hotswap [add] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdc 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: disk/disk_config_single.c:209 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sdc 1>/dev/null 2>&1

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1452 ==== SATA disk [sdc] Model: [HTS721010A9E630 ] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1453 ==== SATA disk [sdc] Serial number: [JR10006P10BSJE] ====

    2017-05-22T08:00:51+01:00 SR2 hotplugd: hotplugd.c:1454 ==== SATA disk [sdc] Firmware version: [JB0OA3J0] ====

    2017-05-22T08:00:53+01:00 SR2 serv-bootup-timeout.sh: all service finish boot up.

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire pam-config for WebDAVServer when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for SnapshotReplication when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for SnapshotReplication when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: SYSTEM: Last message 'resource_api.cpp:163' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:54+01:00 SR2 synoenc: enclosure_host_enum.c:31 failed to use glob to find disk path:/sys/class/sas_host/host*

    2017-05-22T08:00:54+01:00 SR2 synoenc: enclosure_list_enum.c:202 failed to get enclosure head, please check enclosure firmware/hardware

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for SynoFinder when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for SynoFinder when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: SYSTEM: Last message 'resource_api.cpp:163' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for FileStation when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for FileStation when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: SYSTEM: Last message 'resource_api.cpp:163' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire web-config for FileStation when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for HyperBackup when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for HyperBackup when 0x0000 (done)

    2017-05-22T08:00:54+01:00 SR2 synopkgctl: SYSTEM: Last message 'resource_api.cpp:163' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:54+01:00 SR2 root: == DSM 6.1 15101-2 finished boot up ==

    2017-05-22T08:00:55+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for Docker when 0x0000 (done)

    2017-05-22T08:00:55+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire webapi-desc for Docker when 0x0000 (done)

    2017-05-22T08:00:55+01:00 SR2 synopkgctl: SYSTEM: Last message 'resource_api.cpp:163' repeated 1 times, suppressed by syslog-ng on SR2

    2017-05-22T08:00:55+01:00 SR2 synopkgctl: resource_api.cpp:163 Acquire web-config for NoteStation when 0x0000 (done)

    2017-05-22T08:00:55+01:00 SR2 thumbd: dispatcher.cpp:21 (11686, 0) start dispatcher thread

    2017-05-22T08:00:55+01:00 SR2 thumbd: worker_pool.cpp:69 (11686, 0) start worker pool

    2017-05-22T08:00:55+01:00 SR2 thumbd: pool_monitor.cpp:79 (11686, 0) start pool monitor

    2017-05-22T08:00:57+01:00 SR2 updater: utils.cpp:188 Run SUS available updates

    2017-05-22T08:01:04+01:00 SR2 synoddsmd: synoddsm-hostd.cpp:227 Fail to get DDSM licenses, errCode: 0x100

    2017-05-22T08:01:04+01:00 SR2 gateway_change hook event: NEW 0.0.0.0 on docker0

    2017-05-22T08:01:06+01:00 SR2 kernel: [ 47.711239] cgroup: docker-runc (12666) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.

    2017-05-22T08:05:51+01:00 SR2 if_link_down hook event: eth0

    2017-05-22T08:05:51+01:00 SR2 [ 332.824098] init: nmbd main process (13812) killed by TERM signal

    2017-05-22T08:05:58+01:00 SR2 if_link_up hook event: eth0

    2017-05-22T08:05:58+01:00 SR2 [ 340.034218] init: nmbd main process (14460) killed by TERM signal

    2017-05-22T08:05:59+01:00 SR2 gateway_change hook event: NEW 0.0.0.0 on eth0

    2017-05-22T08:05:59+01:00 SR2 dns_change hook event: (1) DNS1=192.168.1.1

    2017-05-22T08:05:59+01:00 SR2 gateway_change hook event: NEW 192.168.1.1 on eth0

    2017-05-22T08:05:59+01:00 SR2 gateway_change hook event: DEL 192.168.1.1 on eth0

    2017-05-22T08:05:59+01:00 SR2 gateway_change hook event: NEW 192.168.1.1 on eth0

     

    Jun's Alpha Loader for DSM 6.1

    in DSM 6.x

    Posted

    I've had barely any issues at all with this release (v1.02a2) but twice now after restarting my system the network interface failed to start. The fix is unplugging and replugging the network cable from the machine. I've had this loader for around 3 weeks now with an auto power off and power on task so 95% of the time I've not encountered this problem.

     

    Any ideas what could be causing this?

    The PC has an integrated Realtek RTL8111H NIC.

     

    Thanks.

    DSM 6.1.x Loader

    in Loaders

    Posted

    I was running DS3615xs 6.0.2 with Jun's Mod V1.01 and decided to do another bare medal install with DS3615xs 6.1 running Jun's Mod V1.02-alpha and DSM_DS3615xs_15047.pat. I kept getting error 13 when I chose to migrate and chose a fresh install.

     

    So I put a new HD in and made it seem like a fresh install and I still got the same error 13 error. Before I revert back to 6.0.2, I wanted to see if anyone had any suggestions?

    Migration didn't work for me either for whatever reason. I always recommend doing a simple data import without importing settings/apps.

     

    Sent from my SM-G935F using Tapatalk

    Dual CPU / Motherboard

    in Hardware Modding

    Posted

    Hello, I'm looking for some advice. I'm wondering if anyone has any experience running a Dual CPU motherboard. I run Plex with about 10 users (probably not at the same time). I use it for the surveillance station (currently 3 cameras but will be adding more in the future), and my wife used it to load high resolution raw photos from her dslr camera. Any advice will be greatly appreciated.

     

    Thanks,

    Jesus

    In theory it should work as DSM runs on top of Linux. I believe Linux has native support for multiple CPU sockets.

     

    Don't have any tests to back that up with DSM though.

     

    Sent from my SM-G935F using Tapatalk

    Bare metal Xpenology vs vmware

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    Are you referring to running Xpenology on top of a virtualisation layer for production? As that would be an incredibly dumb idea from many perspectives.

     

    If you're instead asking about replacing Xpenology with VMware then I'd say it's a good idea if you do an ample amount of virtualisation. Personally I'd host my datastore on a FreeNAS or Xpenology for the performance and backup features they offer.

     

     

    Sent from my iPad using Tapatalk

     

    I believe he is asking about running Xpenology in an ESXi VM vs bare metal.

    One would be insane to use the built in virtualization built into Xpenology vs VMware or other well developed methods, unless it's, just to try it.

    Who would use Xpenology for production? I would fire you for even suggesting that!

    Now that said, I run Xpenology in an ESXi 6.0 VM, and it runs very well and I will not run it bare metal, but for my Sophos firewall I run it bare metal, save lots of problems when you play with servers and VM's. The only reason I use Xpenology is for hobby use and because of SHR. It makes the best use of old odd sized hard drives. For any other important storage I use ZFS, whether it is freenas, nas4free or omnios & napp-it.

    I never said I'd use Xpenology for production, I'd use FreeNAS personally.

     

    Sent from my SM-G935F using Tapatalk

    DSM 6.1.x Loader

    in Loaders

    Posted

    Yea - I can't get DS3617xs to work properly either on bare metal with 1.02a2, but it is a driver thing - I was told that a new loader needs to be compiled to support the version of the firmware and all the drivers associated with it.

     

    I am able to get 1.02a and 3615 to work just fine, but I need to add in a NIC to the box that is compatible with the build.

     

    I'm just hanging tight for now to see what comes next.

     

    It's probably easier to buy a cheap supported Intel NIC and use that instead.

     

     

    Sent from my iPad using Tapatalk

    Bare metal Xpenology vs vmware

    in General Installation Questions/Discussions (non-hardware specific)

    Posted · Edited by Guest

    Are you referring to running Xpenology on top of a virtualisation layer for production? As that would be an incredibly dumb idea from many perspectives.

     

    If you're instead asking about replacing Xpenology with VMware then I'd say it's a good idea if you do an ample amount of virtualisation. Personally I'd host my datastore on a FreeNAS or Synology for the performance and backup features they offer.

     

     

    Sent from my iPad using Tapatalk

    1.0.2a2 VBox OVA

    in Software Modding

    Posted

    Previously my VM's were hung at the "find.synology.com" screen, not sure why.

     

    Where can i get the power button package from?

    Yeah don't use find.synology.com as it doesn't work properly. The official finder app however works great.

     

    Power button package is found below, I've tested it on my bare metal 1.0.2a2 DSM and in VBox and it works just fine.

     

    http://xpenology.com/forum/viewtopic.php?t=32773

     

    Sent from my SM-G935F using Tapatalk

    1.0.2a2 VBox OVA

    in Software Modding

    Posted · Edited by Guest

    Works perfectly, thanks! did you need to compile the vbox drivers for this to work?

     

    No need for any drivers from what I've tested, you may need to install the power button package if you would like to perform a graceful shutdown from the host (shutting down/restarting via DSM web interface works fine). USB 3 also works without issues on 3 completely different systems I tested.

    1.0.2a2 VBox OVA

    in Software Modding

    Posted

    I've created a OVA specifically for VirtualBox from Jun's 1.0.2a2 Loader. It's based on the DS3617xs image provided in the following post:

    http://xpenology.com/forum/viewtopic.php?f=2&t=20216

     

    Hopefully others will find it useful too, just attach one or more VHDs to the VM and you'll be able to find it using Synology Assistant. I strongly recommend the desktop version as the web version rarely works for me :smile:

     

    https://drive.google.com/file/d/0B2OeA4Xy1JA6ejA1dzFoc3NFWVE/view?usp=sharing

    Working DSM 6

    in Loaders

    Posted

    I own a synology 212j and since I updated to DSM 6 I can use many of synocommunity apps (sickrage, Deluge etc). I also have a Xpenology 5.2 running everything normally. If I go to DSM 6.*.* will I be able to use these apps normaly?

     

    I no longer see Deluge with 6.1.x :sad:

    It looks like many apps are dependant on a certain version of DSM.

    Internal disks woke up from hibernation?

    in Packages & DSM Features

    Posted

    Plex is most likely the reason why disks keep spinning up. In general, disk hybernation doen not work as expected, not just on Xpenology by the way. Better to switch hybernation off completely and optionally use power schedule to turn machine fully on/off. Better for life expectancy of disks.

     

    +1, can confirm that having Plex installed and active prevents disks from going into hibernation. My disks were power saving as normal until I got my Plex up and running. And yes I agree that scheduling your machine to turn off overnight is a better option.

     

     

    Sent from my iPad using Tapatalk

    DSM 6.1.x Loader

    in Loaders

    Posted

    Anyone ever got this message? http://s1038.photobucket.com/user/twistedus/media/Capture2.png.html

     

    I can't connect anymore on the NAS and even the drive map is not accessible anymore. I installed XPEnology 6.1.1 lastest update yesterday using DS3617xs v1.02a2. I was working fine. This morning I had this... I tried to reboot, but no result...

    Have you tried unplugging and reinserting your network cable when your Xpenology is in this state?

     

    Every time I've lost connectivity this has worked for me.

     

    Sent from my SM-G935F using Tapatalk

    DSM 6.1.x Loader

    in Loaders

    Posted

    Good to hear! :smile:

     

    It's pretty easy to enable SSH, just do it through the GUI in DSM. You should login using admin rather than root (as root doesn't work OOTB with DSM), you can still use sudo with your regular DSM admin password.

    DSM 6.1.x Loader

    in Loaders

    Posted

    2. Spoofing is another word for faking, if you don't put in your real MAC address into grub.cfg, your network card is having to fake its identity in simple terms.

     

    3. When you setup the Xpenology bootloader you'll see the following entry within grub.cfg:

    set mac1=0011322CA603

     

    You'll want to figure out what your NIC's real MAC address is, this can be done a number of ways but the easiest (assuming you know what your IP address is) to run "arp -a" from command prompt in Windows. You need to put the physical address you see into the variable above without the formatting so rather than 00:11:32:2C:A6:03 it needs to be 0011322CA603.

     

    As Jun mentioned, it's not mandatory to change the MAC address but from my own testing I find using your real MAC address works best.

     

    4. I'm using DS3617xs, I've not tried the other.

     

    EDIT: Forgot to mention that before you try and figure out your MAC address, it's essential that you unplug your system from power completely and leave it off for up to 5 mins. Do not boot back into the loader without changing the MAC address entry otherwise you'll get the spoofed MAC address rather than your real one.

    DSM 6.1.x Loader

    in Loaders

    Posted

    I'm desperately trying to install DSM 6.1 either with DS3615xs or preferably DS3617xs, but nothing works. I can't detect find it once I select Baremetal install (or force install). Is it because my NIC is not supported?

     

    Anyone has a step by step tutorial for Baremetal DSM 6.1 ideally DS3617xs?

     

    I have the EXACT same motherboard and CPU as you and mine works without any issues on 1.0.2a2, make sure your BIOS is up-to-date.

    One thing I've discovered is that the NIC inside this motherboard doesn't like to be spoofed, so ensure you use your real MAC address for the loader. If you're using a fake MAC address then fully power off and unplug your system for 5 mins; I've noticed the spoofed MAC address is persistent as long as the system is connected to the wall.

     

    Also don't select any of the options within the loader, just boot straight to the defaults and you'll be able to find it.

     

    One more quirk is that the Synology Finder software (including the website version) is unreliable with Xpenology, so I'd use an IP scanner to figure out what your IP address is. Better yet, reserve a Mac address :smile:

    DSM 6.1.x Loader

    in Loaders

    Posted

    Has anyone's Quickconnect and DDNS services stopped working? I checked the settings and now when I click on "Log in to Synology account" a message box pops up and says "Oops, an unknown error has occured". I have had this working for months without issue and I havn't changed/updated anything since 6.0.2u9. Have they stopped us all? Do I need a new MAC/SN combo? Any suggestions will be appreciated.

    (I'm running on ESXi with the older stable loader)

     

    Thanks

     

    Yep exactly what you said. Mine used to work perfectly, I guess they caught onto our hacking ways!

    It's not a deal breaker for me though, you can easily setup a dynamic dns on a third party router.

    DSM 6.1.x Loader

    in Loaders

    Posted

    Well I do have concerns about GitHub, since they're so keen on obeying any kind of DMCA takedown request - and those are easy to come by. Synology could say the bootloader collides with one of their trademarks or copyrights, and bam, repo down.

     

    In that case a privately hosted github repo should work?

    DSM 6.1.x Loader

    in Loaders

    Posted

    My personal opinion is that it wont come out of alpha since 6.1 sources are now available and I think it would make more sense so try doing a loader with these sources for the longer term; unless or course the new kernel ends up being more difficult to hack.

    I might be wrong though.

     

    That could also mean that 1.02 will be 6.1 sources based AND out of alpha :wink: But we'd definitely need a better organized thread, and definitely better organized releases (possibly even on Github?)

     

    +1, not sure why we've got this crazy forum thread going when hosting the project on github would allow us to properly raise bug reports and monitor progress. Thoughts?

×
×
  • Create New...