cuspess Posted May 17, 2017 Share #276 Posted May 17, 2017 1. jun's loader v1.02.a2 is a fixed loader for ds3617xs, v1.02a has "time bomb"2. ds3617xs is compiled for new cpu architecture, with new set of instructions, hardware acceleration etc. if you use it on old cpu then it can cause problems on some part of dsm and packages, but users will blame xpeno loaders. for sake of safety and peace of mind its highly recommended to use emulation of ds3615xs While I agree both points, I think whether to use DS3617xs or DS3615xs bootloader comes to trial & error more than anything. No doubt people with knowledge in these area could make a better judgement on which would suit them better, but because most hardware we use to run DSM here are unofficially supported, no guaranteed anything would work. So I think there is no harm trying both, with your testing environment at least, to find which suits your hardware best. Link to comment Share on other sites More sharing options...
chege Posted May 17, 2017 Share #277 Posted May 17, 2017 Agree. Thats why, i think, loader is prepared to emulate both hardware. Thanks to jun Link to comment Share on other sites More sharing options...
Rhubarb Posted May 17, 2017 Share #278 Posted May 17, 2017 My question. You were running DSM 5.2 on xpenology DS3615XS just fine. Why did you upgraded to Jun's DS3617XS instead of the same Jun's DS3615XS bootloader? Elpee Posts: 137 Joined: 19 Feb 2014 01:22 I decided to go to the DS3617xs instead of the DS3615xs because the 3617xs more closely resembled my Xeon processor, whereas the 3615xs has a normal Intel (non-xeon) cpu. Problem is, that Synology seem to regard the DS3617xs as a "business" product and seem to have 'crippled' it from running some of the transcoding apps (and apparently this includes video playback from Photostation 6 (I'm currently running version 6.7.1-3419). Link to comment Share on other sites More sharing options...
Rhubarb Posted May 18, 2017 Share #279 Posted May 18, 2017 Well, I've now reverted to DS3615xs from a Ds3617xs emulation. Still the same problem with Photostation 6.7.1-3419 - videos embedded into Photostation will not play from the Photostation web pages. Exactly the same videos play fine out of Photostation (v6.7.1-3419) on my Synology DS1513+ Have uninstalled Photostation from my xPenology device; re-installed; and re-added the photostation photos and videos to see if this solves the problem. I'm now inclined to revert my xPenology NAS to DS3617xs as the change back to DS3615xs emulation was of no benefit. Supermicro X10SL7-F mbrd, Xeon E3-1241v3, 16GB (2x8GB ECC), 4x8TB WD80EFZX HDD in RAID 6 config: baremetal. Link to comment Share on other sites More sharing options...
Designator Posted May 18, 2017 Share #280 Posted May 18, 2017 Installed another bare-metal system with 1.02a2 successfully, running DSM 6.1.1-15101 Update 2: - ASROCK FM2A78M-ITX+ - AMD AD786KYBI44JC - 2x4GB DDR3 - 4x4TB Seagate & 1x120GB SSD (read cache) A quick question. Any benefits if using SSD for cache in real world? I'm asking because I have to sacrifice a SATA port in my Nas for the SSD drive. Thanks. Are you able to use all 8gb of RAM ? I'm on 1.02a ds3615xs and everytime the System boots 7gb get reserved and can't be accessed by dsm. Link to comment Share on other sites More sharing options...
Designator Posted May 18, 2017 Share #281 Posted May 18, 2017 Installed another bare-metal system with 1.02a2 successfully, running DSM 6.1.1-15101 Update 2: - ASROCK FM2A78M-ITX+ - AMD AD786KYBI44JC - 2x4GB DDR3 - 4x4TB Seagate & 1x120GB SSD (read cache) A quick question. Any benefits if using SSD for cache in real world? I'm asking because I have to sacrifice a SATA port in my Nas for the SSD drive. Thanks. Are you able to use all 8gb of RAM ? I'm on 1.02a ds3615xs and everytime the System boots 7gb get reserved and can't be accessed by dsm. Link to comment Share on other sites More sharing options...
Razor237 Posted May 18, 2017 Share #282 Posted May 18, 2017 I recently redid my setup after a disk failure on my Qnap TVS-471 that i wasn't using a raid setup. i decided to install xpenolgy on that. my question is there a better option of the two loaders .... DS3615xs or DS3617xs, ive tried them both and they both seem to work just wondering if one was a better choice ? since im tinkering i installed photo station threw some photos and videos into the folder. its not a program i use so to me it seems to work ok , i was able to play avi & mp4 files, how were you trying to play the videos Link to comment Share on other sites More sharing options...
Parallax Posted May 18, 2017 Share #283 Posted May 18, 2017 As usual, my first post is a request for help! I'm running a bare metal Gen8 and all was fine using Jun's 1.02a, 6.1, and DS3615xs. I read here a number of people had no problems on Gen8 bare metal upgrading to 6.1.1, so stupidly I allowed DSM to upgrade. Now, I have a problem. I can only see the machine on the network through find.synology.com etc if I do force install. If I do a normal boot, nothing can see it. I see others have had the same problem - although not on a Gen8 - but I haven't seen a solution anywhere. Other info : - I've built a new USB stick, no change. - After a forced install, Synology Assistant finds the system as migratable, and will (re)install the latest 6.1.1. But then when it reboots normally, it doesn't reappear on the network. If I force install again at that point, then of course I'm back to migratable. Any ideas, please? Seems it's perhaps some sort of problem with the NIC driver, but I don't know what and I thought the Gen8 NIC was included in the base 1.02a? (Plus, it used to work...) Thanks in advance. Link to comment Share on other sites More sharing options...
IG-88 Posted May 18, 2017 Share #284 Posted May 18, 2017 there might by a "easy" solution boot from live linux, use mdadm to assamble the system parttion (raid1 over first partition on all disks, 2nd link) and copy the file(s) from /lib/modules/update/ to /lib/modules/ https://xpenology.com/forum/viewtopic.php?f=2&t=20216&start=2900#p101580 and https://xpenology.com/forum/viewtopic.php?f=2&t=30805 PS: I read here a number of people had no problems on Gen8 bare metal upgrading to 6.1.1, not shure where you have read that but i clearly remember a lot of people here complainig about for 2 weeks that it does not work - hardly to overlook when reading about 6.1.1 more then 5 minutes Link to comment Share on other sites More sharing options...
Parallax Posted May 18, 2017 Share #285 Posted May 18, 2017 Thanks, I'll give that a go and see. As a newbie, it would be nice to understand what went wrong and how doing this (hopefully) fixes that, but I guess the aim is to get the system running. not shure where you have read that but i clearly remember a lot of people here complainig about for 2 weeks that it does not work - hardly to overlook when reading about 6.1.1 more then 5 minutes Well, we could trade links to positive and negative postings, and then do a comparison of people's experiences, also positive and negative, with earlier updates, but I don't really see the gain. The impression I formed after reading posts for much of the day on 6.1.1 was positive for bare metal installs and negative for virtualised ones. You have your views based on what you read, I have mine, and the situation is what it is. It has been complained about elsewhere that the nature of this forum is that a huge amount of knowledge on a lot of very complex detail is spread across many, many posts, and builds on history and context going back months and years - plus solutions evolve over time. It is ultimately very hard for a casual and inexperienced user to assimilate all this accurately, particularly while under the pressure of a non-functioning system. Anyway, I appreciate the help and will report back. Link to comment Share on other sites More sharing options...
Parallax Posted May 19, 2017 Share #286 Posted May 19, 2017 OK, I copied the only Broadcom .ko I could find that wasn't present - bnx2.ko from memory - and rebooted. The system then came up as "configuration lost," I reinstalled 6.1.1 and now I'm re-configuring everything to get things working again (all my data is fine, though). I'll see how I go tomorrow because it's late now, but it seems to have worked. But why? But thank you! Link to comment Share on other sites More sharing options...
Parallax Posted May 19, 2017 Share #287 Posted May 19, 2017 Everything's working. It wants me to install 15101-u2 but, um, no, not for the moment. Link to comment Share on other sites More sharing options...
suranx Posted May 19, 2017 Share #288 Posted May 19, 2017 Hi, can you add the virtio drivers? or tell me how to build the extra.lzma? thx Link to comment Share on other sites More sharing options...
IG-88 Posted May 19, 2017 Share #289 Posted May 19, 2017 Hi, can you add the virtio drivers? virtio drivers are part of libvirt? as there is a (beta) virtualization package vom synology with libvirt, qemu(KVM) i'd expect that to part of dsm or that package? or tell me how to build the extra.lzma? thx https://xpenology.com/forum/viewtopic.php?f=2&t=32744 Link to comment Share on other sites More sharing options...
derwoodbones Posted May 19, 2017 Share #290 Posted May 19, 2017 Running Bare Metal on Dell Optiplex 760 Using 1.02a2 With DSM 6.1.1-15101 Update 2, Working great with everything I use. Intel Cre 2 Duo 3.06 Ghz 8GB DDR 2 2x WD 1TB Nextcloud Working WOL Working Auto Power on and off working Thank you very much ! Link to comment Share on other sites More sharing options...
nemesis122 Posted May 20, 2017 Share #291 Posted May 20, 2017 Hi all Sorry the dumb Question but is the newest DSM 6.1 DSM_DS3615xs_15101 working in the GEN8 with Xeon ?? with the newest Loader from DS3615xs 6.1 Jun's Mod V1.02-alpha. Thank you Link to comment Share on other sites More sharing options...
swanduron Posted May 20, 2017 Share #292 Posted May 20, 2017 Hey guys, I try to install 1.02a2 with DS3617 image on my NAS, but the Synology assistant always notice me ERROR CODE 21 about installation file interruption during 'installing DSM' step. I replace computer and pat file, issue still exists. Does anyone meet this issue like me? Regards Link to comment Share on other sites More sharing options...
swanduron Posted May 20, 2017 Share #293 Posted May 20, 2017 Error code 13 (file interruption) is seen in web install. Link to comment Share on other sites More sharing options...
IG-88 Posted May 20, 2017 Share #294 Posted May 20, 2017 whats the hardware (systemboard, controller, nic)? Link to comment Share on other sites More sharing options...
swanduron Posted May 20, 2017 Share #295 Posted May 20, 2017 Multiple platforms. Include DELL V130 notebook, NAS Server(G2120T with Zotec Z77) Intel NUC with i5 and Intel NUC with N2820. All platforms can launch DSM5.2 smoothly. Link to comment Share on other sites More sharing options...
suranx Posted May 20, 2017 Share #296 Posted May 20, 2017 Hi, can you add the virtio drivers? virtio drivers are part of libvirt? as there is a (beta) virtualization package vom synology with libvirt, qemu(KVM) i'd expect that to part of dsm or that package? or tell me how to build the extra.lzma? thx https://xpenology.com/forum/viewtopic.php?f=2&t=32744 thx, i will try it. virtio driver in the linux kernel,with CONFIG_VIRTIO;module name like virtio_net virtio_blk virtio_pci ..... now! I see that xpenology loads virtio drivers. But the installer does not detect any disks. Is this because virtio mounts as /dev/vda. the virtio_net it's work. Link to comment Share on other sites More sharing options...
quicknick Posted May 22, 2017 Share #297 Posted May 22, 2017 (edited) Back from the dead with some good news... I can confirm with high confidence that upgrading directly from 5.2 or 6.0.2 to 6.1.1 is completely successful. To aid future upgrades as the bootloader matures, I am coming up with a nice backup package to backup of the system 2.4gb partition. I recommend for everyone to do this before they do any upgrade/update. Then the risk is really low to upgrade to any version even when untested. If an upgrade fails it is easy to restore back to previous version you were running if you fail. More on that soon. Edited May 22, 2017 by Guest Link to comment Share on other sites More sharing options...
Polanskiman Posted May 22, 2017 Share #298 Posted May 22, 2017 Back from the dead with some good news... I can confirm with high confidence that upgrading directly from 5.2 or 6.0.2 to 6.1.1 is completely successful. To aid future upgrades as the bootloader matures, I am coming up with a nice backup package a backup of the system 2.4gb partition is saved. I recommend for everyone to do this before they do any upgrade/update. Then the risk is really low to upgrade to any version even when untested. If an upgrade fails it is easy to restore back to previous version you were running if you fail. More on that soon. Great news! Link to comment Share on other sites More sharing options...
filippo333 Posted May 22, 2017 Share #299 Posted May 22, 2017 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. Link to comment Share on other sites More sharing options...
filippo333 Posted May 22, 2017 Share #300 Posted May 22, 2017 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 Link to comment Share on other sites More sharing options...
Recommended Posts