Leaderboard

Popular Content

Showing content with the highest reputation since 05/07/2021 in all areas

  1. Ошибочное обновление на версию 6.2.4. Откат на раннюю версию DSM. Восстановление после утери пароля. Вы являетесь счастливым обладателем сервера на основе Хрени , обновлены до последней, возможной на данный момент, версии 6.2.3 и всё хорошо, но...... Зуд творчества и жажда познаний не даёт вам покоя, а тут ещё и обнова в Панели управления просится на установку. И вот вы нажали на "Обновиться", невзирая на массу предупреждений запретов размещённых на форуме, и вот беда подкралась незаметно....... Все, ниже приведённые скрины Обновления до версии 6.2.4 , показаны ради нагл
    2 points
  2. В этом варианте можно получть Больше гигов, но только от трёх дисков. Это аналог RAID 5
    1 point
  3. В обычном RAID_е нет. Если даже использовать SHR, то всё равно мало дисков. Посмотрите Калькулятор, там более наглядно видно https://www.synology.com/ru-ru/support/RAID_calculator?hdds=
    1 point
  4. На контроллере jmb585
    1 point
  5. https://gofile.io/d/HHbXQP - DS3615
    1 point
  6. Hi, everyone, Thanks for you patience. A new ds918 loader support 6.2/6.21 is uploaded. whats new: uefi issue fixed. i915 driver updated. link https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA (for DS918+) - v1.04b ---Beginning of addition by polanskiman--- link https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b link https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA (for DS3617xs) - v1.03b Please read this topic to know what loader to chose
    1 point
  7. For most systems, Legacy == CSM https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/
    1 point
  8. DS414 is a 32-bit ARM model and cannot be migrated directly to the platforms that XPe supports. Regardless, you should install DSM clean on an XPe box, then copy your data instead of migrate so that you are not hit later with the 16TB volume limit coming from the 32-bit platform. FMI: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Backup/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later
    1 point
  9. Technically more threads are better. In reality the difference will be imperceptible. However, the i3 has much newer silicon, which will benefit in 1) cooler operation and 2) better transcoding support, should you wish to do that.
    1 point
  10. Pour ma part je le fait toujours en ligne de commande : j'ouvre l'invite de commande windows : Puis : diskpart Cela m'ouvre une nouvelle fenetre : Ensuite : list disk Je repère le numero du disque étant celui que je veut formater, et je fait : select disk X ( ou X étant le numero du disque a formater ) Ensuite pour l'effacer : clean A partir de ce moment, le disque est vide Pour créer une partition : create partition primary Puis lui donner une lettre non deja utilisé sur ton ps, pour y avoir acces, par exemple G : as
    1 point
  11. War gebraucht auf Kleinanzeigen aber es ist der BR10i
    1 point
  12. I've read it twice but can't see where he made anything different then usual, the hardware is from 2011 (nehalem) and has uefi bios, doesn't make it special in any way any chance to get more information or a dmesg log from that system?
    1 point
  13. @bearcat please read the link you yourself have linked Yes you are correct, the 2017 is the last production SPP However is it not the last POST production SPP I mean even in the paragraph which state the bit about the 2017 has a link to Reducing Server Updates pdf which explains this! Gen8.1 IS a Post Production SPP So no its doesnt have "support for new technology, features, options and new major OS/hypervisor versions", but "When a server generation is in post-production, modifications to the firmware, drivers, and system software for that server generation is limited to bug
    1 point
  14. + я бы сделал резервную копию настроек системы, помимо гипер бекап. Панель управления - обновление и восстановление - резервирование
    1 point
  15. maybe your topic isn't right, from my point of view blaming drivers is not the best starting point as lack of documentation, reading or experience is more often the case, so phrasing more cautiously is advisable, pointing a finger into the direction of coders or maintainers without even a shred of proof ... not a good starting point in theory the driver for jmicron would be jme.ko and thats even available in jun's default driver set (i had to look, can't remember ever seen such nic irl, kind of exotic) so it seems not likely that it is a driver problem because the loader comes
    1 point
  16. Подключить один как внешний и на него сделать полный бэкап с помощью HyperBackup.
    1 point
  17. Sorry to hear about your troubles. While I don't have anything to contribute to a fix(Haven't been through this myself), I can at least help shed some light on best update practices going forward, and hopefully alleviate some of the 'update anxiety' 1. You can use win32diskimager to clone out your working thumb drive after booting into DSM and setting it up. If anything should come up, you can easily flash that to a different thumb drive. Good to keep versions of your configs with this. I have version fro 6.2.2, 6.2.3, with and without extra driver files, and every time I make a change
    1 point
  18. Если система в формате Ext4, то можно винт подкинуть и смотреть vlc плеером
    1 point
  19. Yes exactly is what you are thinking!! But there are some traps Yes we can run xpenology on docker fully functional but inside a KVM VM but works pretty fine really. Right now what I have is a simple docker that execute an instance of xpenology (clean, so the page of installation is shown to install) I thinking which features do you think could be interesting for you? give support to docker volumes inside the xpenology? -v /myhost/data:/Volume1/myshare ? Please let me know what do you think could be interesting for you. when I have a more stable ve
    1 point
  20. First welcome to the forum, second there is no need to upgrade to 6.2.4 as it doesn’t bring anything new & 6.2.3 is stable. Going forward it’s unlikely there will be any effort given to make 6.2.4 work given that Synology will be releasing DSM 7 later this year so it would make sense for jun or anyone else to concentrate on that.
    1 point
  21. there are a lot of nice looking components that will things go south, you need to look very careful for specs and chips on cards like this one, hyper duo ? sounds like marvell, might only have one at best two pcie lanes and can only do pcie 2.0 i looked it up and its a 88SE9230 so its 2 lanes pcie 2.0 resulting in max 1000MB/s for the 4 drives, so not optimal the M.2 is pcie 3.0 x4 and there are M.2 to pcie 4x slot adapters with flex cable, so the m.2 can become a pcie 4x slot https://www.amazon.com/ADT-LINK-Extension-Express-Extender-R42SF/dp/B08DRDT47K (i b
    1 point
  22. I am not trying to be rude also but this question was answered so many times already in different posts. There is no road map and this forum does not have a "development" team to work on loaders but very experienced members for troubleshooting. Is there a future? No one knows if this is the end of XPEnology or not. This is up to Jun or any other person with coding skills... As @flyride said on another post with similar question. If he was Jun, he would not spend his time creating a new boot loader just to support this last update. DSM 6 is at the end and the
    1 point
  23. @xReppa: you opened samba port to the world and you're surprised with the attack? Only safe way to share samba over internet is through Virtual LAN like ZerotierOne. There is Zerotier client for most of devices including DSM and any linux/android/windows etc. So you just need to register on their webpage, create virtual network, share network ID with clients and when they join you just accept them in your admin console. All traffic is encrypted and safe. Apart of that, it's good to separate upload section from download section. All downloads should be read-only for all external clien
    1 point
  24. Через консоль это как? Ставил ее как пакет, слетала после +- час-два работы(
    1 point
  25. So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved.
    1 point
  26. Mod DSM to enable Root access: 1) Login on the putty as admin 2) command to go to root sudo -i 3) command to insert root password synouser -setpw root insert-your-new-root-password 4) command for edit sshd_config vi /etc/ssh/sshd_config 5) find text #PermitRootLogin prohibit-password 6) replace into PermitRootLogin yes UsePrivilegeSeparation sandbox 7) save#quit reboot nas
    1 point
  27. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: YES - Installation type: ML-350 G6, CPU-X5690, 36Gb-RAM, 2xLSI9211-IT with 12x2Tb in RAID6, 2x512Gb CACHE-SSD, DELL X520-2T 10Gbe - Additional comments: Downloaded and applied the update through DSM control panel. after reboot no network connection, no activity.
    0 points
  28. @bearcat And what exactly is your point? Apart from like another main member of this forum who seems to have a stick up their arse to stroke their own ego and arrogance?! Serious if you aint gonna post anything helpful, just ******* off.
    0 points
  29. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: unRAID KVM - Additional comments: INSTALLED AND REBOOTED, AFTER 30 MIN. NOTHING. CANNOT FIND VM ANYWHERE.
    0 points
  30. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3.25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: No - Installation type: TheCUS N5550 - Notes: Would not complete install, system still worked
    0 points
  31. Outcome of the installation/update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: Jun's Loader v1.03b - DS3617xs - Using custom extra.lzma: YNO - Installation type: Custom Hardware - Additional comments: Help
    0 points
  32. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.2_24922 Update 6 - Loader version and model: JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: HP ProLiant MicroServer Gen10 Plus - Additional comments: Fresh Install - Update seems ok, but it doesn't boot after restart - Synology Assistant can't find the server.
    0 points
  33. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: appears to complete the install, no reboot
    0 points
  34. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25432 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP ProLiant MicroServer G7 - N54L - Additional comments: Update seems ok, but it doesn't boot after restart. Recovery doesn't work.
    0 points
  35. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.4-25556 - Loader version and model JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: KVM - Additional comments: Fresh Install of DSM 6.2.4-25556 failed with va not found Failed to process header
    0 points
  36. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.4-25556 - Loader version and model JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: Proxmox VM - Additional comments: Fresh Install of DSM 6.2.4-25556 failed with va not found Failed to process header
    0 points
  37. Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: appears to complete the install, reboots and hangs at 100% CPU utilization immediately after the bootloader initializes Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Not
    0 points