Popular Content

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

  1. 1 point
    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: ---End of addition by polanskiman---
  2. 1 point
    Bist Du so vorgegangen, wie hier beschrieben? https://www.synology-forum.de/showthread.html?98583-ecoDMS-Backup-wiederherstellen
  3. 1 point
    @NetproНет, hw не заработает, sw работает.
  4. 1 point
    Nur zum Verständnis: woher kommt das Backup? Aus einer Windowsinstallation, Docker, ...? Auf der Nas hast Du den Container für ecoDms „gezogen“ und dort das Backup eingespielt?
  5. 1 point
    Am Anfang des Logs steht, dass er die Datenbank „ecodms“ nicht findet (PostGreSQL). Wie hast Du denn gesichert? Mit HyperBackup oder manuell? P.S: bitte Logs dieser Größe entsprechend wrappen beim nächsten Posting, da scrollt man sich ja nen Wolf
  6. 1 point
    I was able to fix this by deleting .xpenoboot ussing ssh. Thanks!
  7. 1 point
  8. 1 point
    Обновил ссылку 8.1.3-5473 https://mega.nz/#!2kFhSYqY!CtzlniTwXliXgFO9PhYesAoTtQ6fSF7oM_U__uLTgYw
  9. 1 point
    Обновил ссылку 8.2.2-5766 https://mega.nz/#!vpkhBQ6R!IeUl_VIw1FcAreLDZWDnk-U0xX63A7Ju90dJs9k6QgY
  10. 1 point
    What am I doing wrong? I keep getting: Invalid entry length (3). DMI table is broken! Stop. Invalid entry length (3). DMI table is broken! Stop. Invalid entry length (3). DMI table is broken! Stop. Invalid entry length (3). DMI table is broken! Stop. Also it seems broken in control panel now.
  11. 1 point
    That FAQ already exists but people seems to care little for the FAQs. That is why most of the time I don’t bother answering questions which answers are already in plain sight. In fact I have been trying for a while to implement a way to force new members to read the facts before beeing able to post or view any other thread. FAQs>Hardware FAQ>Faq #8 The faq does not provide brand names or models on purpose because that is a varying information. Also Flyride has published two excellent threads about native compatibility which are pinned. Other than going into people house to build their machines I am not sure what else we can do. [emoji56]
  12. 1 point
    The slots will be shown in DSM regardless of whether there is a controller available to service them. You are assigning meaning to the empty slots, and it doesn't tell you anything about what is and is not recognized in the system. You are connecting a large number of drives - not a typical, or simple installation. All three add-in SATA controllers are using port multiplication. I suspect the DSM drivers are having trouble with that many controllers along with port multiplication, which has been documented to have trouble in complex scenarios (which your configuration definitely is). Even your base motherboard configuration has FOUR controllers onboard (2x Intel SATA via PCH, 1 embedded 88SE9128 and the JMicron eSATA). A couple of points: Disable controllers you aren't using Each controller added may "remap" the active ports and order of drives in DSM (that's where SataPortMap/Idx comes in to play) Personally, I avoid multiple instances of the same controller type in one system. Intel SATA usually works well on DSM. If I were in your shoes, I'd back up and figure out why the Intel SATA II disks aren't working. Using the cheapest tech (Marvell) to support a complex configuration (11 drives) is part of the problem as it is making debugging and analysis very hard ESXi may help you support multiple controllers (and the Intel SATA). However, it doesn't like Marvell too much. There are some hacks to make it work, but again LSI is a much better option.
  13. 1 point
    are you using nics mac from your hardware?
  14. 1 point
    root@DS3615xs:~# dmidecode -t processor # dmidecode 3.2 Scanning /dev/mem for entry point. SMBIOS 2.8 present. Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: EA 06 09 00 FF FB 8B 0F Version: pc-q35-3.1 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 2 Core Enabled: 2 Thread Count: 1 Characteristics: None
  15. 1 point
    Увидет. Не предложит. Восстановит DSM до новой версии.
  16. 1 point
    Hmm, calling people out as arrogant isn't the way to curry favor for help. Anyone you could possibly reach with that comment has spent countless hours trying to help many, many people such as yourself. Based on your questions, both you and OP present with little or no evidence of effort to understand DSM and how the XPenology loader works. And only slightly below the veneer of that request is a challenge to be assured you won't lose data, which you cannot possibly get from someone on an online forum. It's your responsibility, nobody else's, to make sure your data is safe. Let's spell it out: All the loader does it let us boot DSM on non-Synology hardware. Nothing more, nothing less. Any other behavior is attributable to DSM, Synology's operating system. Yes, it's based on Linux, but that's not a limiting factor. Many XPenology users never launch the shell, nor do they need to. If you want to be successful running DSM on XPenology, it will be in your interest to know something about DSM. There are many, many places to learn about how to do things with DSM, not the least of which are Synology's forums. So here are a couple of key points that ARE, literally, embedded in the tutorials. Hopefully they will help steer you in the right direction. Upgrading DSM from 6.1 to 6.2 is a function of DSM. Not the loader. If you want to upgrade from 6.1 to 6.2, you'll need to install a 6.2 compatible version of the loader (either 1.03b or 1.04b), otherwise DSM will crash once upgraded The 6.2 compatible loader must also work with your hardware, which isn't a guarantee even if you were successfully running DSM 6.1. Installing a new loader is analogous to moving your disks to a new Synology Diskstation - DSM will prompt for migration or upgrade. Migrating and/or upgrading DSM isn't inherently a data-destroying process, if done properly. Again, this is a DSM behavior Any upgrade or migration operation can fail for many reasons, including loader incompatibility (ref hardware issues above) or user mistake. Those who attempt an upgrade or migration operation without a data backup plan are, bluntly, foolish To you, OP and anyone else who wants to upgrade - it's very much in your interest to build up a test environment and validate your upgrade plan each and every time before subjecting your production system and data to risk. This is repeated again and again in the tutorials. It is one of the benefits of a virtualized (i.e. ESXi) environment - it makes it very easy to test without extra hardware. Good luck to you and OP. Your linarrogant friends online will be waiting to help if you run into trouble.
  17. 1 point
    This is my output... looks like a kernel panic?
  18. 1 point
    I been running 3617(1.03b ) with Fujitsu D2607 (flashed to IT-mode) with 8 HGST without problem. 3615 doesn't support LSI cards. Try to use Intel NIC with following chip: 82575/82576/82580/I350/I210/I211 (as they are native to dsm) BIOS: Enable CSM (If there is) and set everything to Legacy, Don't use UEFI mode. Current DSM: 6.2.2-24922
  19. 1 point
    Updated powerbutton package to work with dsm 6.2 for ds3615, ds3617 and ds918+ POWERBUTTON_6.2-0002.SPK or https://www39.zippyshare.com/v/R3ftOA3X/file.html
  20. 1 point
    For those who are interested to be able to power off DSM 6.1.x VM via ACPI and get the shutdown working through Proxmox Virtual Environment, I have recompiled the button.ko and evdev.ko from the poweroff package of this post in order to get this working on dsm 6.1.x/DS3615xs. power-off_dsm61x_ds3615xs_x86.tar.gz