Leaderboard

Popular Content

Showing content with the highest reputation since 11/17/2020 in all areas

  1. Hey there, today was an interesting day. I finally got all parts together and decided to upgrade my server to support more drives. 5 hours later, and two heart attacks, I finally got everything running. But lets start from the beginning. (I am not mentioning my self-made problems of updating my BIOS which I shared here (3 posts total): So I ahave currently 10 disk plus two SSDs in my setup and want to expand my storage. Case has 24 hot-swap ports, so all fine. Already have 6 (4 usable via SAS cable atm) internal ports and am using an LSI SAS 9220-8i for 8 more ports. Of
    2 points
  2. Daily, there are questions regarding how to select a DSM platform, version and loader, usually after something has been tried that isn't working. This table and decision point example should help navigate the options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 11-Aug-2020 Loader DSM Platform DSM Version
    2 points
  3. edit 14.05.2020: 6.2.3 is back online as v25426, for newer coffeelake cpu's with problems using hardware transcoding (dev/dri present after boot) there is a new videostation that fixes the problem https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=144918 edit2 02.06.2020: as @richv31 pointed out here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=148564 there seems to be a serious problem with 918+ and scsi/sas drivers, at
    1 point
  4. @maximewell i'm cannot remeber... but try again ... create a volume try the update and it works. It was that step!!! Thanks
    1 point
  5. NOTE: This problem is consistently manifested when running as a virtual machine, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3 and under certain conditions, other 6.2.x versions. The fix can be implemented safely on baremetal installs. You can verify if you have the issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If these files are not present, your Synoboot devices are not being configured correctly, and you should install the fix script. If synoboot3 exists that is ok
    1 point
  6. Be sure to take out your loader USB with the drives and burn another one for the test, then when you restore your old drives, put your old loader back at the same time.
    1 point
  7. You have one virtual sata controller, with a 20GB virtual data disk in slot 0, the loader in slot 1 and a 50GB virtual data disk in slot 2. You can see you are booting from the loader on sata1. Best practice is to have two virtual sata controllers, this is easy in ESXi but I don't know ProxMox. vsata0 should have only the loader in slot 0 (sata0) and boot from that device. vsata1 should have your virtual data disks in sequence, slot0 = 20GB, slot1 = 50GB, etc. If it is hard to set up two virtualsata controllers, one vsata controller should work, with loader i
    1 point
  8. It does look a little strange. Can you share a list of the virtual controller and drives you are using? Do you possibly have two loader devices mounted to your VM by accident? The script (which is just part of the Jun bootloader code) tries to identify the loader partition by its size smaller than any valid RAID partition. If a targeted partition is mounted, this is characteristic of the eSATA automap problem, so it quietly dismounts it for you. If there are two block devices that present as a loader, it could get confused. This is a potential problem with Jun's loader with or
    1 point
  9. So, as anyone did it , I answer myself. Maybe someone is trying to make a "direct connection" between your computer and xpenology. After two days testing, errors and trying ... I can affirm that a direct connection can be made, and I got triple transfer speed. The most important thing is: 1) hardware speed ethernet (NIC 10G, 5G, 2,5G USB, Thunderbolt adapters or Cards) and 2) SET UP DHCP SERVER in DSM. DSM will do a new IP for your ethernet device and you can connect to Server by Samba... .I increase transferences from 108mb/s to w235-r275 mb/s. (without modem through)
    1 point
  10. Yes I'm using btfrs, no snapshots. I'm making backups with rsync on another xpenology nas, weekly, I've already formatted my infected nas and after checking integrity of storage pool I'l start copying files back from backup, which will take three days but, it is what it is
    1 point
  11. Yep, I guess you're right. Here are the cache creation wizard's results, upon a 700 GB JBOD
    1 point
  12. Just found hijack.explorer,sysytem.restore in Win10. Luckily I havenot power on my backup nas. I'm going back to linux and restore from backup.
    1 point
  13. - Outcome of the update: SUCCESSFUL DS3615xs DSM v6.2.3-25426-Release-final - DSM version prior update: DSM v6.2.3-25426 - Loader version and model: JUN'S Loader V1.03b - Installation type: WorkStation 15 Pro Win10x64 - Using custom extra.lzma: NO - Additional comments: Requires reboot No DOWNLOAD DS3615xs DSM v6.2.3-25426-Release-final
    1 point
  14. generell lohnt auch ein blick in die logs um zu sehen was dort an meldugen steht wenn es schon mehrfach vor kam dann lohnt auch eine statistische betrachtung die strom und sas versorgung ist in 2 x 4 geteilt, wenn das problem immer auf einer 4er seite ist dann sind es ziemlich sicher kabel probleme, wenn es sich verteilt dann kann man aber leider nicht viel sagen, es könnte dann auch noch an den kabeln liegen oder am netzteil (selbst unverträglichkeiten platte/controller sind nicht auszuschließen) ganz allgemein ziehen 2.5" platten nicht so viel strom aber es kann trotzdem am ne
    1 point
  15. Da Fallen mir zwei mögliche Ursachen ein: Unterversorgung der Platten mit Strom oder defekte Kabel Im Storage Manager im Bereich HDD/SSD, lohnt es sich bei jeder Platte mal "Health Info" anzusehen und dort den "Drive Reconnection Count". Sobald da bei auch nur einem Laufwerk die Zahl > 0 ist (und sich evtl. auch noch weiter erhöht) würde ich dringend die Verkabelung wechseln und/oder ein größerees Netzteil einbauen. Achte darauf das die Sata-Stromkabel von unterschiedlichen "Hauptsträngen" vom Netzteil abgehen. Minderwertige Verlängerungskabel können zu Problemen führen. Defekt
    1 point
  16. with 6.2.2 you would need to use jun's i915 driver by using "0.8_std ds918+" with 6.2.3 there is a newer i915 driver from synology on the same level is jun's diver was, supporting up to geminilake and lower tier 9th gen cpus ootb, only thing to do is to use my extra.lzma to remove jun's old driver (not working with 6.2.3 because of kernel changes by synology) and make the new one from synology active there is nothing special, it works with 6.2.2 it will with 6.2.3 the 1st post in this thread is also about updating from 6.2.2
    1 point
  17. Kommt darauf an was man unter "besser" versteht... Bei einer VM egalisiert sich das darunter eingesetzte Blech. Die Wahrscheinlichkeit eine VM-Plattform richtig unterstützt zu bekommen verheisst mehr Erfolg, als unterschiedliche Netzwerkkarten und Storage-Kontroller Konstellationen zu unterstützen oder gar gezwungen zu sein bestimmte Produkte erwerben zu müssen... Damit aus einem vermeintlichen Vorteil des direkten Betriebs auf Blech ein echter Vorteil werden kann ... muss es auf diesem erstmal laufen...
    1 point
  18. its also possible to simply check synology's homepage https://event.synology.com/en-global/dsm_preview its still in preview, then comes beta (1-3 month?), then RC and after that realese so its more like q2/2021
    1 point
  19. На 6.7 я знаю что работает с е1000е, прописав вручную мак из пары к серийнику.
    1 point
  20. I recently installed Xpenology on a Terramaster F4-220 I picked up during the holiday sales that were going on. I noticed the hard drives were consistently operating at a very high temperature (50+ C while idle) so I decided to investigate how to control the fans. I had read elsewhere there is some BIOS option to drive the fans faster, but lacking the VGA dongle to get into the BIOS I figured I'd investigate how to control them from Linux. So I discovered the hardware contains an IT8772E chip for which Google helpfully brings up this datasheet: https://master-chip.ru/fi
    1 point
  21. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.04b DS918+ - Using custom extra.lzma: v0.13.3 for 6.2.3 from IG-88 - Installation type: BAREMETAL - ASRock J5040-ITX, 16GB RAM, using onboard sata ports & nic - Additional comments: Real sn and mac. VT-d disabled in bios. Reboot and Shutdown works. "cd /dev/dri" okay. "cat /usr/syno/etc/codec/activation.conf" returns {"success":true,"activated_codec":["mpeg4part2_dec","h264_dec","h264_enc","hevc_dec","aac_dec","aac_enc","ac3_dec"],"t
    1 point
  22. https://mega.nz/folder/q80zQATS#1VAWvg4Dr0rfSnRjM5X9pQ
    1 point
  23. hi thank you for everyone soon I will announce my DESKTOP vDSM with Quickconnecte still functional on appliance.ova IN DSM.EXE version HERE IS A DEMO. BETA SHARING YOU DSM APPLIANCE 6.2.3 UPDATE.2 ??
    1 point
  24. I attach the file POWERBUTTON_6.2-0002.SPK
    1 point
  25. It seems to me a strange thing, mystifying… Try attached .so. libsynonvme.so.1
    1 point
  26. Hi all, in an effort to simplify the process, I've done some work towards that, but i think there is a lot of room for improovement. So far what i've done : - Translated about 100% all disk, kept original and translated original on a separate folder - Cleaned up the firmware process and kept as much many as i could from initial scripts - Added an automated process to figure out as many devices as i could during model.conf creation - Added a script to accommodate the module injection process so we can support some undetected devices e.g. vmxnet3, e1000 etc - Adde
    1 point
  27. Add "pcie_aspm=off" to common_args_XXXXX parameter (common_args_ds918 in ds918 loader and so on) in grub.cfg.
    1 point
  28. Minor changes. Dev Guys now do some more strict PHYSDEV parsing. Nothing special. libNVMEpatch.sh
    1 point
  29. This is a repost of an archive I posted in 2015. This method works for DSM 6.2 using Jun's loader 1.03b for me. 1) Enable SSH and ssh into your DiskStation 2) Become root ( sudo -i ) 3) Make a mount point ( mkdir -p /tmp/mountMe ) 4) cd into /dev ( cd /dev ) 5) mount synoboot1 to your mount point ( mount -t vfat synoboot1 /tmp/mountMe ) 6) Profit! admin@DiskStation:~# sudo -i root@DiskStation:~# mkdir -p /tmp/mountMe root@DiskStation:~# cd /dev root@DiskStation:/dev# mount -t vfat synoboot1 /tmp/mountMe root@DiskStation:/dev# ls -l /
    1 point
  30. Yeah, the only thing in that whole long terminal session that did anything was the copy file above. You're lucky the random shell action didn't do any damage as root. Now you need to make the script executable: Then reboot and your drive should show up in Storage Manager. Please do yourself a favor and only use R/O cache mode, not R/W ...
    1 point
  31. Сам отвечу на свой вопрос. Забегая чуть вперед скажу, что испробовал на себе, все заработало и проблем я не заметил. Что я делал: 1) Остановил приложение которое хотел перенести. 2) Разрешил доступ по SSH и зашел через WinSCP 3) Скопировал директорию /volume1/@appstore/xxx в директорию /volume3/@appstore/xxx где xxx - это папка с нужным пакетом 4) Далее пошел в /var/packages/xxx и отредактировал линк на директорию /target 5) Вернулся в веб-морду и нажал кнопку "Refresh" в диспетчере пакетов, после этого у меня приложение поменяло номер тома на нужный. 6) Запустил приложение. Проверил ч
    1 point
  32. Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительны
    0 points