• Announcements

    • Polanskiman

      DSM 6.2-23739 - WARNING   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs
    • Polanskiman

      Email server issues - FIXED   06/14/2018

      We have been experiencing email server issues. We are working on it. Bear with us. Thank you. ------------- Problem has been fixed. You might receive duplicate emails. Sorry for that.

LeaderGL

Members
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LeaderGL

  • Rank
    Junior Member
  1. Hi, i'm receiving errors about and i cannot access anymore my DS. Someone can help me please?
  2. XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    is it possible to update the synology station directly from version DSM 5.0-4528 Update 2 to the DSM 6.0.2?
  3. Drivers requests for DSM 5.2

    could be very usefull to have m.2 wifi/bluetooth adapters driver. eg. Killer 1535 Wireless AC Adapter http://www.killernetworking.com/products/wireless-ac-1535 or something like that
  4. Volume locked after disk crash

    i haven't the "Repair" link...the volume is in crashed status the only button enable is the "Remove" one... there aren't shell script for force the volume repairing?
  5. Volume locked after disk crash

    Hi all, i've a NanoBoot DSM 5.0-4528 with Update 2 (the one in signature) currently locked (https://dl.dropboxusercontent.com/u/109559700/volume1_crashed.png) The issue is due to the SATA power cable bad contact that trigger a found/not found disk at runtime. So my NAS crashed locking my volume. There is a way to unlock it? Currently i've access to the whole system, with all data available and all disks S.M.A.R.T. info are good. Thanks a lot
  6. cpufreq and powernow-k8 modules

    is this compatible also with dsm 5.0.x version?
  7. Asrock Q1900-ITX/Q1900DC-ITX

    thank you, it work right
  8. Problema con porte usb

    Anche a me da lo stesso problema astock q1900dc-itx con ultima versione di bios
  9. Asrock Q1900-ITX/Q1900DC-ITX

    I installed the 64 bit versions (ds3615xs); XPEnoboot_DS3615xs_5.1-5022.3 and all works fine except for USB ports...i don't see any flash storage attached... do you have some suggestions?
  10. number of disks in dsm

    and there are no side effects changing both files with the real numbero of esata, usb, sata ports in our systems?
  11. NEW DSM 5.1-5004 AVAILABLE !!

    try with: 1. http://hallard.me/how-to-install-kernel-modules-on-synology-ds1010-dsm-4-1/ 2. http://xpenology.com/wiki/en/building_xpenology
  12. [DRIVER] Sitecom WL-349 v3 (RTL8188S)

    it seems that there is a bug in some 3.2.x kernel version with the r8712u.ko module during the firmware upload. there is a way to rebuild the driver with the latest realtek version for our kernel?
  13. XPEnology gnoBoot

    hi, which kind of modification is needed in synobios.ko in order to be patched? i see that SetMicropID was modified, also other stuff need changes? i'd like to know more about it.
  14. Hardware Build Suggestions?

    i'm very gratified from my configuration: Motherboard: Asrock AM1H-ITX (4xSATA_III + 1xGIGA_LAN + 4xUSB_3.0 + 4xUSB_2.0 + mPCIE + PCIE + DC POWERED) CPU: AMD Athlon 5350 (QuadCore 20W) RAM: Kingstone XyperX Fury 8GB HDD: 3x3TB WD RED CASE: X-Case NAS-4 BOOT: Sandisk Ultra Fix 16GB USB 3.0 improvements: for system boot the best could be use a USB FMD like http://www.amazon.it/dp/B000RAHMM2/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=1163MGRQN0BQA&coliid=IS6W6XVV16QVG is was inside the case, invisible and leave an external usb port free. for the external case maybe the U-NAS could be also a great choice, i don't know internal space
  15. Thanks. Is it possible to use the extra space on my usb key for other stuff? Create an additional partition for something else...i don't know what... and further more...is it possible to hide the primary boot partition (where nanoboot is) in dsm but keeping visible the secondo partition?