Jump to content
XPEnology Community

mcdull

Member
 View Profile  See their activity

  • Posts

    252

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by mcdull

    Driver extension jun 1.03b/1.04b for DSM6.2.3 for 918+ / 3615xs / 3617xs

    in Additional Compiled Modules

    Posted

    On 9/29/2020 at 6:38 PM, IG-88 said:

    afair the change braking the drivers was introduced in DSM 6.2.1-23824 so if you use the latest 6.2.1 it will be the same as 6.2.2

    but the i915 driver in both are the same, we did not have the source jun used for this driver so it was reused in 6.2.2 and worked

    so if hardware trancoding is your problem then it might be something diffrent, the best way in that case is 6.2.3, just follow the guide in that thread

    the new i915 driver from synology works at least as good as jun's, does seem to have less problems with some different apollolake and geminilake boards

     

     

    i would not clean out the firmware directory as there are firmwares from synology there that does not come with the loader, i file more there does not hurt and the loader will compare and replace firmware files by itself, so any old/different files will be replaced and new file will be copied

    cleaning the update folder does not hurt but is not needed usually (if so it will be written in the guide i wrote to that extra.lzma in question)

    I too found the performance of emulated vmxnet3 network adaptor very bad.  Is there any test build on virt-io for DS918 @ 6.2.3?

    I think net driver is good enough as disk performance would not have much difference for lun passthrough.

    qemu-guest-agent would be awsome but I guess it is not a driver only issue.  Thanks. 

    2 out of 5 drives in SHR being very busy

    in DSM 6.x

    Posted

    /proc/mdstat 

     

    Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
    md2 : active raid5 sdk5[6] sdh5[4] sdl5[7] sdg5[8] sdj5[5]
          15608749824 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
          [===============>.....]  resync = 75.9% (2961953688/3902187456) finish=127.9min speed=122511K/sec
          
    md4 : active raid1 sdk6[0] sdl6[1]
          3906998912 blocks super 1.2 [2/2] [UU]
          
    md5 : active raid1 sdi3[0]
          9761614848 blocks super 1.2 [1/1]
          
    md1 : active raid1 sdg2[2] sdh2[5] sdi2[1] sdj2[4] sdk2[3] sdl2[6]
          2097088 blocks [12/6] [_UUUUUU_____]
          
    md0 : active raid1 sdg1[4] sdh1[3] sdi1[5] sdj1[6] sdk1[1] sdl1[2]
          2490176 blocks [12/6] [_UUUUUU_____]
          
    unused devices: <none>

    2 out of 5 drives in SHR being very busy

    in DSM 6.x

    Posted

    I have a VM under Proxmox running DSM 6.2 with AMD cpu.

    The DSM was migrated from an old intel with an SHR consists of 5 disks

    3 x 8TB and 2 x 4TB

     

    Occassionally, the 2 4TB disk will be extremely busy with utilization at 99-100%, while the other 3 at 60-65%

    the 4TB disk are 7200 Toshiba, and the 8TBs are all helium based 5400rpm from WD.

     

    Are there any means that I can check what the 2 4TB are actually doing?  I have scanned the 2 disks and without errors.

    DSM 6.x Proxmox Backup Template

    in DSM 6.x

    Posted · Edited by mcdull
    more info

    45 minutes ago, tronba said:

     

    When used the Template, where can i put the new mac address and change the serial number?

     

    I did not use the template. I just use the raw loader.  mount the first partition in r/w mode and there is a file under grub folder. 

     

    You need to modify the below "TWO" files.

     

    grub.cfg

    grubenv

     

    DSM 6.x Proxmox Backup Template

    in DSM 6.x

    Posted

    I did not use the template, as I did not learn this thread when I prepare my migration.

    I confirm that PVE 6.2 can run 6.2.3-25426 update 2, but I installed straight from the pat file.

    vmxnet3 as network card is much faster than E1000, although both are rated at 1Gbps, but will go beyond 1gbps connection.

    with 1000E, the speed is like 160MB.

    with vmxnet3, the speed is up to 350MB.

    quickconnect works if you own geniune serial number with associated mac address.

     

    I used the loader only.. (synoboot.img), nothing else. you need to modify the img so that the serial number and mac address changes with the genine serial you got.

     

     

    Photo station and Moments (DSM 6.2)

    in Synology Packages

    Posted

    On 3/30/2019 at 10:40 AM, Kollcn said:
     

     

    My setting.

     

    E3-1275

     

    ESXi,

    CPU=4

    Cores per Socket = 4: Sockets:1

     

    On 3/30/2019 at 10:40 AM, Kollcn said:

    Can you post your settings on ESXI? I tried set cpu settings to 2  cores and 4 cores and others.the log always returns like:

    p.s  I am using 1.04b loader and DSM 6.2.1-23824 Update 6 under ESXi 6.7.0 

    
synophoto-concept: uncaught thread task exception /source/synophoto/src/daemon/plugin/plugin_worker.cpp:102 plugin init failed: /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so

     

     

    DSM 6.2 Loader

    in Loaders

    Posted

    My DSM is getting into trouble.  It is setup on top of ESXi 6.7. And it recently stopped working after a few days. Ping cannot reach the host but the VM keep using 3.0Ghz of CPU.

    I have no idea if it is some malware that infact the device but I am not quite sure on where should I check.

     

    Serial log has nothing special.

    The DSM is 6.2.1 with latest update.  Any help will be appreciated.  

    Photo station and Moments (DSM 6.2)

    in Synology Packages

    Posted

    I have checked that 3615xs is also a dual core cpu with HT.  So enabling HT may already solve your problem.  please see cat /proc/cpuinfo if you got 4 cpu cores picked up.

    4 minutes ago, Designator said:

     

    That´s not an option right now as my cpu is not compatible with Intel VT-d. So I wouldn´t be able to passthrough my disks.

     

     

    Photo station and Moments (DSM 6.2)

    in Synology Packages

    Posted

    Woo... I got it solved.!!!!! 

    thanks for @Designator to tell me that he got the same issue while he got a new CPU.

    Then I looked into others set up again and checked the log.

     

    /run/synophoto/concept.socket] construct failed: connect: Connection refused  

     

    This line drew my attention and I believe it is all related to the setting of hypervisors.

    It seems that the software tried to connected to something that failed.. which is in terms of sockets.

     

    It turns out to be the "NUMBER OF CORES" has to match with the identified CPU.  I always assign 2 cores in previous setting. Now, with 4 cores, subjects now popping out real fast.!!!!!!!!

×
×
  • Create New...