Leaderboard


Popular Content

Showing content with the highest reputation since 09/13/2018 in all areas

  1. 2 points
    11.06.18 как поставил 918 6.2 так до сих пор ВСЁ работает, железо 3150 скорость копирования как была раньше 1 гиг так и осталась вы просто меньше читайте этот форум а больше пробуйте самостоятельно здесь тусуются те у кого ничего не работает большинство как поставили xpenology так больше сюда и не заглядывают, кроме как только узнать о выходе нового релиза и не более
  2. 2 points
    A kernel config related to pci is changed, so all non official pcie device drivers are broken. 通过我的 ONEPLUS A5000 上的 Tapatalk发言
  3. 1 point
    Hi, everyone, Thanks for you patience. I've uploaded a beta version of 3615/3617 loader to mega, please test and give your feedback. https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw note: uefi boot still has issue, it will be fixed when I have more time. ---Beginning of addition by polanskiman--- ---End of addition by polanskiman---
  4. 1 point
    Recently I deployed Bitwarden (https://bitwarden.com/) in Synology Docker and thought I would share my experience for others looking to do so. ***For experienced individuals comfortable with synology command line and linux environments with docker, I take no responsibility for any issues encountered*** ***Read fully before considering*** History: I've used a number of password managers (lastpass, keeper, keepass, etc) and still use some for professional reasons. For personal use I was using KeepassX so I could control the safe (in Dropbox) and did not want my personal data cloud hosted. I need it to run on linux, windows, osx as well as mobile (android) support. I also am a strong proponent of two factor authentication, keepass offers it but is a lackluster implementation. I wanted a more robust self hosted password manager that I could host on my synology. Feature Requirements: There is a number of things I wanted in my personal password management that Bitwarden offered over the others TOTP (Time Based One Time Passcode) Two factor authentication with Authy or Google Authenticator Self hosted password manager with central database stored on my synology Robust device and application support (Linux, Windows, OSX, IOS App, Android App, Browser integrations etc) Push syncing of changes so conflicts in password safe are avoided or less likely Secure software with good development (bitwarden has a cloud hosted solution as well as self hosted, so they are diligent in ensuring updates are made regularly https://help.bitwarden.com/security/ and community involvement is very good) Free for personal use and open source Setup Requirements: You will need to have the following requirements met to follow this guide: Latest XPenology/Synology: Currently on DSM 6.1.6-15266 with JUN'S LOADER v1.02b - DS3617xs Latest Synology Docker Package: Currently on 17.05.0-0370 (https://www.synology.com/en-global/dsm/packages/Docker) Your own public domain (in this use case I use a personal public facing domain with public DNS) An understanding of Domains, Extenal DNS, SSL Certificates (Lets Encrypt), Reverse Proxies, Linux/Synology cli, Docker Process: Please fully read the bitwarden self hosting documentation (https://help.bitwarden.com/article/install-on-premise/) before attempting any of these steps Create your bitwarden external DNS record (I used bw.<mydomain> this guides example will be bitwarden.domain.com) You have two options for your dns record: "A record" which is a record to the External IP address you use to reach your synology/xpenology device (eg: bitwarden.domain.com A record to Your public IP) "CNAME record" which is a record to the existing DNS Record of your synology/xpenology device (eg: bitwarden.domain.com CNAME record to nas.domain.com) Create an SSL Certificate using Lets Encrypt within DSM Certificate Manager Go to "Control Panel" -> "Security" -> "Certificate" -> "Add" "Add a new certificate" -> "Next" Description "Bitwarden Certificate", "Get a certificate by Lets Encrypt" -> "Next" Domain name: "bitwarden.domain.com", Email: "<your email address>" -> "Apply" Create a Reverse Proxy in DSM to the docker port used by bitwarden Go to "Control Panel" -> "Application Portal" -> "Reverse Proxy" -> "Create" Description: "Bitwarden https reverse proxy" Source: Protocol: "HTTPS", Hostname: "bitwarden.domain.com", Port: "443", HSTS and HTTP/2 "Unchecked" Destination: Protocol: "HTTP", Hostname: "localhost", Port: "8123" Associate Reverse Proxy with Certificate Go to "Control Panel" -> "Security" -> "Certificate" -> "Configure" Services: "bitwarden.domain.com" Certificate: "bitwarden.domain.com" -> "OK" Ensure docker is installed and collect docker folder location Install docker from the package manager Confirm docker shared folder location "File Station" -> folder "docker" right click properties and collect path (mine was "/volume1/docker" and will be referenced as the path in this article) SSH connect to synology/xpenology internal IP address or hostname as administrator account linux/osx terminal command: ssh admin@<nas internal ip or dns> (enter admin user password) windows use putty or bash for windows to connect (provide admin user and passwords as credentials) Switch to root user for docker access command: sudo su - (enter admin user password when prompted for password) Change to the docker folder command: cd /volume1/docker (or whatever your path to docker shared folder may be) Follow bitwarden self hosted setup procedure (reference https://help.bitwarden.com/article/install-on-premise/) Get a self hosting installation id and key here https://bitwarden.com/host copy these value to be used when running installation Import bitwarden.sh script command: curl -s -o bitwarden.sh \ https://raw.githubusercontent.com/bitwarden/core/master/scripts/bitwarden.sh \ && sudo chmod u+x bitwarden.sh Run installation using script command: ./bitwarden.sh install follow prompts in code block: root@nas:/volume1/docker# ./bitwarden.sh install _ _ _ _ | |__ (_) |___ ____ _ _ __ __| | ___ _ __ | '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ | |_) | | |_ \ V V / (_| | | | (_| | __/ | | | |_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_| Open source password management solutions Copyright 2015-2018, 8bit Solutions LLC https://bitwarden.com, https://github.com/bitwarden =================================================== Docker version 17.05.0-ce, build 9f07f0e-synology docker-compose version 1.14.0, build c7bdf9e (!) Enter the domain name for your bitwarden instance (ex. bitwarden.company.com): bitwarden.domain.com (!) Do you want to use Let's Encrypt to generate a free SSL certificate? (y/n): n 1.17.2: Pulling from bitwarden/setup Digest: sha256:cf55e0288b6392ee9c35022089396c3c561773ddc963945f1afea8fce359757f Status: Image is up to date for bitwarden/setup:1.17.2 (!) Enter your installation id (get it at https://bitwarden.com/host): <my_installation_id> (!) Enter your installation key: <my_installation_key> (!) Do you have a SSL certificate to use? (y/n): n (!) Do you want to generate a self-signed SSL certificate? (y/n): n !!!!!! WARNING !!!!!! You are not using an SSL certificate. Bitwarden requires HTTPS to operate. You must front your installation with a HTTPS proxy. The web vault (and other Bitwarden apps) will not work properly without HTTPS. !!!!!!!!!!!!!!!!!!!!! Generating key for IdentityServer. Generating a 4096 bit RSA private key ....................................................................................++ ......................................++ writing new private key to 'identity.key' ----- (!) Do you want to use the default ports for HTTP (80) and HTTPS (443)? (y/n): n (!) HTTP port: 8123 (!) Is your installation behind a reverse proxy? (y/n): y (!) Do you use the default ports on your reverse proxy (80/443)? (y/n): y (!) Do you want to use push notifications? (y/n): y Building nginx config. Building docker environment files. Building docker environment override files. Building app settings. Building FIDO U2F app id. Building docker-compose.yml. Setup complete Once setup is complete you will need to create some missing folders (this is due to the docker version on synology not creating bind mount locations on container creation, likely a version bug) there should be a new folder creating in your /volume1/docker location called /volume1/docker/bwdata create the following folders in the bwdata directory from your current location (/volume1/docker location) command: mkdir bwdata/core bwdata/core/attachments command: mkdir bwdata/ca-certificates command: mkdir bwdata/logs bwdata/logs/admin bwdata/logs/api bwdata/logs/identity bwdata/logs/mssql bwdata/logs/nginx bwdata/logs/notifications bwdata/logs/icons command: mkdir bwdata/mssql bwdata/mssql/data bwdata/mssql/backups If there are any failures on the ./bitwarden.sh start stating "ERROR: for <container name> Cannot start service <container name>: Bind mount failed: '/volume1/docker/bwdata/<path>' does not exists" make sure to create that missing <path> specified in the error Run setup using script command: ./bitwarden.sh start if there are not missing folders as per notes above the service should now be running on port 8123 and reachable from your external dns entry https://bitwarden.domain.com Run updatedb using script command: ./bitwarden.sh updatedb this will run database migrations on bitwarden for any latest database changes to run Additional changes to consider: modify your bwdata/env/global.override.env for the following features add smtp email disable registrations after you create your accounts other override features specific to your use case restart containers after change to global environment vars Update bitwarden version: To update to the latest version run: command : ./bitwarden.sh updateself command: ./bitwarden.sh update Hopefully this guide is helpful to anyone looking to host bitwarden on their synology/xpenology device.
  5. 1 point
    my guess is that your motherboard now "wants" to boot from the hard drive with the DSM OS installed. You may need to go to the BIOS, and change the boot order to first start from your USB drive.
  6. 1 point
    Many thanks, FOXBI! The shell script works great! PS I recently had a trip to Korea. Korea is a beautiful country populated by wonderful people.
  7. 1 point
    I am not a professional developer I am a bit embarrassed every time I release the source ,, Please see below.
  8. 1 point
    Thank you, FOXBI! Can you publish last version shell script?
  9. 1 point
    FOXBI! You are TOTALLY making us happy, I have been wanting to change this CPU INFO forever, so you're hard work in finding where it is, and how to change it - IS WONDERFUL!!! if you search through the forum, you will see many people regularly say that it "could not be changed, as it was hard coded..." and you have clearly proved these statements to be totally uneducated and wrong. I appreciate your work, you are in no way rude or need any forgiveness, you are making great things happen!! 😎 Just trying to help you as best I can, I APPRECIATE you and your creativity/work.
  10. 1 point
    But it's wrong though. In Image #2, 4 it's showing 4 cores, which isn't correct as validated by Image #3 directly from the BIOS. This is a bare metal install, no VM, no HT option to enable/disable. The i3-4130 is the default CPU info from the DS3615xs, my system is the i3-3220 (BIOS image #3). But CORES and THREADS are different, not the same. Seems you are display for CORES, the what is actually the THREADS. As far as the CPU frequency goes, 3.29Ghz where is it getting that from, since it should be 3.30Ghz and none of the command line data or BIOS indicates that value. 🤔 Do I make sense? 🤓
  11. 1 point
    cheromecast dongle, Denon AVR-x4200w это одно и тоже блин, что мешает попробовать просто или Denon AVR-x4200w нет в наличии ещё, не пойму никак
  12. 1 point
    Поставьте пакет "Сервер мультимедиа" и упражняйтесь на здоровье. Или "Audio station".
  13. 1 point
    10G for sure but raid6 might give you enough speed and more space to use, if assembled you can try by installing dsm and creating/deleting the data volume in different raid configurations, you can expect 400-500 /MB/s from, also keep in mind even if you can read with 900 MB/s most disks (even ssd's with sata interface) cant handle that speed, you might be able to measure it with same network tools but ... raid10 for safty? there is no replacement for backup, more important data results in more frequent backup (and/or storing backups in a different location where burglar or fire cant harm them) you might reconsider this, sata ports and energy also cost money, 8 or 10TB disks and less ports might cost the same and give you more room to expand (usually you will have such system for 3-6 years), so compare the price $ per TB and plan to double your capacity after 2 years (witch is much cheaper if you can add disks instead of replacing 12 disks) ssd's for reading will only speed up things if they are already in ssd cache, so mostly on systems where many users access data, a system used by one user will not see much gain from a read cache for writing cache dsm will need two ssd's (running internal as raid1), also here its important to have a closer look, to achieve faster write your source where the data comes from hast to be fast enough, a normal sata ssd will max out with 600MB/s so you would need nvme ssd on both ends to max out 10G network (btw there is also 40G available ...), for using nvme you will need the 918+ image (baremetal install) my system has 12 ports, 11 x 4TB disks (stated with 6), no ssd cache, nvme ssd on client side there might be some special cases like video editing where big files are often written but if its for a single person local storage for editing and nas (10G nic, 500MB/s) storage/archive is more cost effective and gives better speed and latency depends on the software and how you implement the nas you can use iSCSI for disk replacement if a software does not want to write to a network drive but in that case its called SAN and latency and I/O per second gets more important (like using fiber instead of 10GBaseT) so basically yes, with iSCSI you can do it if you are that kind of hardware beginner then you might start with a smaller project or let someone with more experience assist you (not just some people over the internet, more a friend with hands on capabilitys) keep in mind that the default xpenology config (kicking in after a bigger update) is 12 disks, if you user 12 data disks and 2 ssd's for cache you will be at 14 ports and loose something after a backup (back to 12 ports) and will have to restore config manually - nothing for beginners and people without linux knowledge my advice, keep reading about xpenology and its problems (dig into some of the problems people report and how often it happens) and consider a different system (like free nas for more safer storage with ZFS or open media vault when its less about special features in dsm) more back to you question, it depends on how you plan, there are boars with 12-20 ports but they can get spendy, if full atx or flex atx is possible you have more options, keep in ming that most of the boards have no 10G nic, so you will have to plan on (at least) pcie 4x slot for the 10G nic and one at least 8x slot for a storge controller, like 4 or 8 port, if its just 4 port then plan 2 slots so on most systems you will have 4-6 sata onboard + 8 sata you add to get 12-14 your ports plan 4 port cards if you stick to ahci (safer way when it comes to xpenology and the efforts of synology to prevent using dsm on other hardware)
  14. 1 point
    Hey there - THANK YOU SO MUCH FOR MAKING THIS POSSIBLE! It's been one of those little annoying things there was never a resolution for, until you worked your MAGIC! Seems like there might still be some bugs, with the CPU SPEED and number of CORES. Image #1:Original Info Center Image #2:After running ch_cpuinfo Image #3: BIOS Info Image #4: Mobile Info Center root@CentralNAS:/volume1/homes/admin/shc-3.8.9b# dmidecode -t processor # dmidecode 2.12 # SMBIOS entry point at 0x000f0000 SMBIOS 2.7 present. Handle 0x005E, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Core i3 Manufacturer: Intel(R) Corporation ID: A9 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 58, Stepping 9 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz Voltage: 2.9 V External Clock: 100 MHz Max Speed: 3300 MHz Current Speed: 3300 MHz Status: Populated, Enabled Upgrade: Socket BGA1155 L1 Cache Handle: 0x003A L2 Cache Handle: 0x003B L3 Cache Handle: 0x003C Serial Number: Not Specified Asset Tag: Fill By OEM Part Number: Fill By OEM Core Count: 2 Core Enabled: 2 Thread Count: 4 Characteristics: 64-bit capable root@CentralNAS:/volume1/homes/admin/shc-3.8.9b# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz stepping : 9 microcode : 0x19 cpu MHz : 3292.436 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx f16c lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6584.87 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz stepping : 9 microcode : 0x19 cpu MHz : 3292.436 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx f16c lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6584.87 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz stepping : 9 microcode : 0x19 cpu MHz : 3292.436 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx f16c lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6584.87 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz stepping : 9 microcode : 0x19 cpu MHz : 3292.436 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx f16c lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6584.87 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: I hope you find this helpful/useful! If there is anything I can do to help, please let me know! Thank You
  15. 1 point
    Yes you can, however performance may be affected.
  16. 1 point
    Told you... Sent from my iPhone using Tapatalk
  17. 1 point
    Истину говоришь дружище! Отправлено с моего iPhone X используя Tapatalk
  18. 1 point
    Works perfectly on Proliant Gen8 with Xeon 1230 V2. Thank you so much for this useful utility. Etienne
  19. 1 point
  20. 1 point
    It would depend on how the "bad" sectors are created, if it was a pending error, re-initialize the disk would also eliminate them, especially SMR drives. but like @benjistarksaid, don't trust them any more.
  21. 1 point
    If the HDD has bad sectors it will only get worse. That HDD should not be part of your raid or you might regret it sooner rather than later. Sent from my iPhone using Tapatalk
  22. 1 point
    Hi, there was a known bug with samba system that it would report root capacity with the *nix systems. But I guess yours' is a little bit confusing. I strongly suspect that you have create all 3 sub-volume on the same volume (presumably you would be using Btrs) Please check the following Check Storage manager, check how many storage pools and volumes you have. If you want to use 3 drive as 3 separate volume, you should have 3 pool and 3 volume Check Control Panel -> Shared Folder, you should have at least 1 shared folder on each volume, it could be chosen when created or be moved afterward. Hope this solve your problem
  23. 1 point
  24. 1 point
  25. 1 point
    I uploaded a new version file that supports mobile. It's possible to use !!