Jump to content
XPEnology Community

abesus

Member
  • Posts

    21
  • Joined

  • Last visited

Posts posted by abesus

  1. 1 hour ago, WiteWulf said:

    Yeah, we need to ideally wait for TTG to support 7.0.1, or as a bodge, for Jumkey to update their repo to support extensions.

    I already have locally updated sources for 918+ v 7.0.1 with support for extensions. The problem is, that TTG's extensions also needs to be updated to support 7.0.1 or someone has to fork them and modify...

     

    edit: so I've decided to wait for official support for 7.0.1. Until that I will stay on my current 7.0.1. Good for me that it is stable :)

  2. 8 minutes ago, WiteWulf said:

    It's good to see this happening across a variety of setups. So far I think I've had reports of it on:

    - baremetal Gen8

    - baremetal Gen7

    - Proxmox

    - ESXi

    So it looks like this problem is connected to DS3615xs. I'm running DS918+. One week ago I was running DS3615xs on the same baremetal (xeon E3-1265L V4, MB MSI Z97I ACK GAMING) machine with same dockers (this time I had InfluxDB docker runnig) and everything was working stable.

    • Like 1
  3. 1 hour ago, WiteWulf said:

    Just out of curiosity: could those of you having docker problems (or even if you're running docker and not having problems) install an influxdb container and see what happens? It kernel panics my machine every time I run it, across multiple versions of the image.

    I've created InfluxDB container but at this moment I have no connection to db. I'll let you now if anything happens.

    Im using few containers and everything is working great (gitlab, roon-server, mincraft server)

     

    btw: I've found this info, which looks very similar to your problems:

    https://access.redhat.com/solutions/1354963

    • Like 1
  4. 12 hours ago, ThorGroup said:

    Yes.... Intel decided to add a single instruction (MOVBE) to only the Atom line... then a few years later they've added it to the Xeons. Go figure... that's why 918+ requires a newer CPU with MOVBE support. If you search for "MOVBE intel cpu" you will find many topics not related to xpenology as this is a much bigger problem.

    As for the SN/MAC: the mac needs to match your real ethernet adaptor. As for the S/N you can google "xpenology s/n generator" and there are tools prepared by the community.

    The good information is that according to internet Xeon E3-1265L V4 has support for MOVBE. My problem was connected to intel iommu driver and I've resolved this issue by reconfiguring this driver. From now my DSM is stable and user_config.json looks like this (vid/pid/sn/mac are different of course ;-) )

    Quote

    { "extra_cmdline": { "vid": "0x46f4", "pid": "0x0001", "sn": "1780PDN123456", "mac1": "E2:C4:5C:C9:EE:EE", "intel_iommu" : "igfx_off" }, "synoinfo": {}, "ramdisk_copy": {} }

    It will (should) have impact only for virtual machines inside DSM which I don't have ;-) 

  5. 21 minutes ago, shibby said:

    ok, something is wrong with new driver (or maybe i something thing screw up).

    I have 7.0.1 DS918+ installed. Today i compile new redpill and "burn" on new flashdrive. Everything seems to launch correct, ping to NAS working, Synology Assistant found NAS with status "ready". But when i try go to IP:5000 then NAS goes to hard reboot. Does anyone has the same issue?

    I've build new image and installation was stopping at 56%. After cleaning everything once again, removing all images from docker and building image one more time it is working correctly.

  6. 5 hours ago, p33ps said:

     

    Could you please be more specific about this?

    In my case there were lot of logs like this:

    Quote

    kernel: DMAR: DRHD: handling fault status reg 3

    kernel: DMAR: [DMA Read] Request device [05:00.0] fault addr fffe0000 [fault reason 06] PTE Read access is not set

     

    It looks like there is an error in kernel (it is not the latest one) in iommu. After disabling this driver my NAS is rocket solid :) (excluding strange logs from bootup ;-))

  7. Hi,

    I've question: Is such log normal or is something bad in my system:

     

    Quote

    2021-09-09T20:00:51+02:00 DS kernel: [    2.863870] Module [apollolake_synobios] is removed. 
    2021-09-09T20:00:51+02:00 DS kernel: [    2.863943] synobios: unload
    2021-09-09T20:00:51+02:00 DS kernel: [    2.864035] <redpill/bios_shim.c:96> apollolake_synobios BIOS went away - you may get a kernel panic if YOU unloaded it 

     

  8. 35 minutes ago, haydibe said:

    Are you sure that you executed `sudo su - root` to become root before the vi line?

     

    Instead you could use `sudo -i` to become root.

     

    Refactored to by dynamic:

    
    #!/bin/sh
    for cpu in /sys/devices/system/cpu/cpu[0-9]*; do
        echo powersave > ${cpu}/cpufreq/scaling_governor
    done

     

    Yes. I'm sure:

     

    Quote

    root@DS:~# echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    -ash: echo: write error: Invalid argument

     

  9. 3 hours ago, titoum said:

    acpi throttle

    
    sudo su - root
    vi /usr/local/etc/rc.d/S99Powersaving.sh and insert according to number of core
     
    Script-content:
    
    #!/bin/sh
    
    echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
    
    chmod +x /usr/local/etc/rc.d/S99Powersaving.sh
    sh /usr/local/etc/rc.d/S99Powersaving.sh

     

    It doesn't work on my setup. Currently DS918+(cpu xeon, motherboard MSI Z97I GAMING ACK). I've got such error:

     

    -ash: echo: write error: Invalid argument

     

    I cannot write to this file even using vi.

    Am i doing something wrong?

     

     

  10. 16 hours ago, p33ps said:

     

    I'm afraid that DS3615xs and DS3617xs won't be able to use the "face recognition" feature, according to this Synology article:

     

    https://kb.synology.com/en-uk/DSM/tutorial/Which_Synology_NAS_models_support_the_facial_recognition_feature_on_Synology_Photos

     

    There is only DS918+ model listed. 

    I'm not sure about that. Currently I'm working on DSM 6.2.4 from ds3615xs and face recognition is working very well.

    Video transcoding is not working because I couldn't find valid SN and MAC for ds3615xs.

     

  11. 9 hours ago, haydibe said:

    But, you did notice the v4 at then end, didn't you? Xeon E3-12xx v3 and newer should be compatible. I am running it without any problems on a E3-1275 v5. E3-12xx v2 and older are not compatible.  

    So in my case, software for DS918+ should work on my CPU. That would be great (I've working set of SN and MAC) :)

    Did you check /var/log/messages? I've got a lot logs like:

    kernel: DMAR: DRHD: handling fault status reg 3

    kernel: DMAR: [DMA Read] Request device [some numbers] fault addr some address...

    I can't remember exactly but if it can be helpful I can build loader again and check.

  12. Hi everyone,

     

    Ive successfully built and use loader for 980+. Unfortunatelly, I'm using Xeon E3-1265L V4 and there were many errors in system logs. System was hanging-up every few hours. It looks like DS918+ is using some new CPU/GPU instructions that are missing in my old xeon.

    After that I've tried DS3615xs loader. DSM 7.0 is in beta stage so I've tried 6.2.4. Everything is working great except moments. How can I find valid SN/MAC combination for ds3615xs?

     

    Seba

     

     

     

     

  13. Hi Everyone,

     

    I've question about NIC. I am using XPEnology on my ITX PC but with gnoBoot.

    I cannot use XPEnoboot because of network adapter. My PC is based on ECS KBN-I/2100 (V1.1) motherboard.

    After booting from XPEnoboot my NAS is not available in home network. It looks like XPEnoboot has no drivers for my network adapter (RTL8111E Gigabit Fast Ethernet Controller).

    Is there any chance that i can put some extra boot parameters to XPEnoboot to force loading module for my NIC?

     

    Thanks in advance for replies.

    Regards,

    Seba

  14. i bought an usb3 controlleur low profile card and plug my ups on it.

    problem solved (hp nl40)

     

    thx , it works (hp n36l+dlink usb3 card+eaton 5110 ups)

    Could you give the full name of working usb3 controller (full model name).

    Thanks in advance

×
×
  • Create New...