All Activity

This stream auto-updates     

  1. Today
  2. There is no place like 127.0.0.1 ... Then, to be able to access it you must: 1 - Change IP 2 - Add a route to the new IP from "the outside".
  3. @Griffen Hi, and welcome. You are not the first one to try it out on the EX4xx series, as can be seen here and right here is another new user as well.
  4. Funcionó perfectamente en una placa Asrock j4105. Un saludo, gracias Enviado desde mi Redmi 3S mediante Tapatalk
  5. synology original system are headless by default, even if you connect a monitor, after the kernel start you don't see anything, you would need to connect a serial null modem cable to get a (local) console everything you need after booting is a network connection and i suggest the "Synology Assitant" Application you can download from Synology, its easy to search for DSM systems in the local network with this if it does not show up in network then in most cases its a problem with the network adapter (not supported) or in the case of 918+ loader/image you need at least a 4th gen intel (haswell) to make the kernel start
  6. Synology sees the rackstation on but with a different mac all together unsure from where its getting that from. After modifing the vender file, I am now getting a different msg on the screen. Before it was system booting please wait, not it recognises that the is no dsm on the drives and asks to install it via gui or syno assistant but the value for sn is still blank. and now when I try to load dsm on the drivers, I get error 15 from syno assistant.
  7. Hiya unfortunately synology has a close grip on that and dont even want to sell me a dom. You guys here are my only support. I have a RS3412xs Would I be able to use the flash from there to make a loader for this one I wonder. Could anyone advise. Thanks again though for all the support
  8. I will read up on the link you provided. The reason though I ask about the headless system though is because the original system is installed using a windows connector program (this being the very thing that WHS has trouble with). Thanks for the reply
  9. no "initialized" for a disk means it crates ~two 2GB partitions (one dsm system, one linux swap) and the rest is free to create a raid array the same way a headless original unit is used, only difference is you have a "external" usb flash drive i'd suggest you read the faq to give you some basics https://xpenology.com/forum/forum/83-faq-start-here/
  10. Narco

    Debit transfert Nas-Win10

    Bonsoir tout le monde ! Je me tourne vers vous pour un problème assez étrange entre mon Nas (DSM 6.1.7-15284 Update 3) et mon PC sous Windows 10. Lorsque je veut copier un fichier ou regardé une vidéo stocké dans le Nas en passant par l'explorateur Windows le débit est catastrophique (en moyenne 2mo/s 😶) ! Je suis bien sur en 1Gbit et n'avais aucun problème il y a quelque jour a attendre un taux de transfert d'environ 100Mo/s. Ce qui est étrange, c'est que lorsque je passe par Chrome en me connecté à l'interface DSM, je vais dans l'explorateur de fichier et lance le téléchargement d'un gros fichier (+60Go) le taux de transfert monte facilement a 100-105Mo/s... De plus un test de debit sur Nperf me donne un score d'environ 850Mb/s, ce qui ne laisse pas de doute quand au faite que le matériel n'a pas de soucis, non ? Le PC et le Nas sont relié en ethernet sur une box SFR. Je précise aussi que j'ai tenté de connecté un PC portable sous Windows 10 également, à la place de mon PC fixe, et le débit est bon ! En espérant avoir était clair et trouvé une solution, Merci d'avance 😁😏 PS: J'ai testé des copie de fichiers d'un disque à un autre et pas de problème...
  11. I recently purchased a secondhand HP EX490 media server with Xpenology on it I am completely new to media servers and nas though am quite software capable. I was expecting windows home server to work (since I also got the original software along with it) but quickly discovered this not to be the case. I hesitated to use Xpenology but must admit it's actually quite good. The seller is long gone from the online market place I purchased it from which is a pity because I have some questions about xpenology. The first one is in have a loader program on a usb stick and the DSM on a harddrive. Is it possible to have the bootloader and DSM on a usb stick? Am I able to also save my media on the same harddrive as where DSM is located? And probably the most pressing question is how can I install Xpenology and DSM on a headless system (just in case I ever want to receive install it)? All up though I was reluctant to use Xpenology / DMS at first I am now very happy I gave it a go... Kind regards Griffin
  12. just install the last 5.2 (highest build number) and then on top the latest update pack (v9 from end 2018)
  13. your way with that hardware is the 3615 or 3617 loader (1.03b) and 6.2 image if you want the latest dsm version as it has a realtek nic i guess you will only use 6.2.(0) as 6.2.2 needs different drivers and i've not made the new driver package available (yet) but if you use a different usb to boot and disconnect your normal disks you can play with different versions of dsm 6.x
  14. Adic

    SOS

    Меня смущают все цифры
  15. Приветствую, на второй свободной железке тестирую переход на 6.2.2_24922 update 3. обновляется без проблем с заменой extra.lzma но после обновления транскодинг работает один раз, потом не заводится. стоит ли ждать, что заработает в верисии update 4,5 2019-10-22T19:58:05+05:00 nas synoscgi_SYNO.VideoStation2.Streaming_2_open[18822]: json_utils.cpp:147 Failed to parse json file [/tmp/VideoStation/enabled] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.436459] BUG: unable to handle kernel NULL pointer dereference at 00000000000000f8 2019-10-22T19:58:29+05:00 nas kernel: [ 267.444467] IP: [<ffffffffa050fa8c>] send_vblank_event+0x2c/0x60 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.451145] PGD 23e20067 PUD 23d21067 PMD 0 2019-10-22T19:58:29+05:00 nas kernel: [ 267.455535] Oops: 0000 [#1] PREEMPT SMP 2019-10-22T19:58:29+05:00 nas kernel: [ 267.641999] CPU: 1 PID: 18840 Comm: ffmpeg Tainted: P OE 4.4.59+ #24922 2019-10-22T19:58:29+05:00 nas kernel: [ 267.649776] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./J1800N-D2H, BIOS F8 10/03/2018 2019-10-22T19:58:29+05:00 nas kernel: [ 267.659941] task: ffff880074481380 ti: ffff8800327f8000 task.ti: ffff8800327f8000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.667547] RIP: 0010:[<ffffffffa050fa8c>] [<ffffffffa050fa8c>] send_vblank_event+0x2c/0x60 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.676669] RSP: 0018:ffff8800327fbba0 EFLAGS: 00010006 2019-10-22T19:58:29+05:00 nas kernel: [ 267.682070] RAX: 00000000000000f0 RBX: ffff88006fa50000 RCX: ffff8800765d8958 2019-10-22T19:58:29+05:00 nas kernel: [ 267.689316] RDX: 00000000000038e0 RSI: ffff8800765d8940 RDI: ffff88006fa50000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.696558] RBP: ffff8800327fbba0 R08: 0000000000000006 R09: 0000000000060000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.703805] R10: ffff88006fa50000 R11: 0000000000000000 R12: ffff8800765d8940 2019-10-22T19:58:29+05:00 nas kernel: [ 267.711063] R13: ffff8800327fbbb0 R14: 0000000000000000 R15: ffff8800769ed000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.718303] FS: 00007f5a0d338740(0000) GS:ffff880079300000(0000) knlGS:0000000000000000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.726523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2019-10-22T19:58:29+05:00 nas kernel: [ 267.732365] CR2: 00000000000000f8 CR3: 0000000023f3b000 CR4: 00000000001006f0 2019-10-22T19:58:29+05:00 nas kernel: [ 267.739612] Stack: 2019-10-22T19:58:29+05:00 nas kernel: [ 267.741660] ffff8800327fbbe0 ffffffffa050fb0b 000000000000010a 00000000000e8b71 2019-10-22T19:58:29+05:00 nas kernel: [ 267.749231] 0000000000000000 ffff88006fa501d8 ffff88006f11e000 ffff88006fa50000 2019-10-22T19:58:29+05:00 nas kernel: [ 267.756827] ffff8800327fbbf0 ffffffffa050fb45 ffff8800327fbca8 ffffffffa0620bfb 2019-10-22T19:58:29+05:00 nas kernel: [ 267.764423] Call Trace: 2019-10-22T19:58:29+05:00 nas kernel: [ 267.766933] [<ffffffffa050fb0b>] drm_send_vblank_event+0x4b/0x70 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.773666] [<ffffffffa050fb45>] drm_crtc_send_vblank_event+0x15/0x20 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.780843] [<ffffffffa0620bfb>] intel_atomic_commit_tail+0x32b/0x10a0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.788187] [<ffffffffa05887ab>] ? drm_atomic_helper_swap_state+0x14b/0x2f0 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.796853] [<ffffffffa0621d2e>] intel_atomic_commit+0x3be/0x4e0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.803676] [<ffffffffa0527aa5>] ? drm_atomic_add_affected_connectors+0x25/0xe0 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.811722] [<ffffffffa05274f2>] drm_atomic_commit+0x32/0x50 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.818074] [<ffffffffa058da76>] restore_fbdev_mode+0x156/0x280 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.825677] [<ffffffffa058f3ae>] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.835151] [<ffffffffa063dd34>] intel_fbdev_restore_mode+0x34/0xb0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.842235] [<ffffffffa05a6029>] i915_driver_lastclose+0x9/0x10 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.848953] [<ffffffffa050c229>] drm_lastclose+0x29/0x130 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.855054] [<ffffffffa050c596>] drm_release+0x266/0x390 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.861070] [<ffffffff811368ca>] __fput+0xca/0x1d0 2019-10-22T19:58:29+05:00 nas kernel: [ 267.866023] [<ffffffff81136a39>] ____fput+0x9/0x10 2019-10-22T19:58:29+05:00 nas kernel: [ 267.870989] [<ffffffff81062760>] task_work_run+0x80/0xa0 2019-10-22T19:58:29+05:00 nas kernel: [ 267.876477] [<ffffffff810020e7>] exit_to_usermode_loop+0xa7/0xb0 2019-10-22T19:58:29+05:00 nas kernel: [ 267.882673] [<ffffffff810023d3>] syscall_return_slowpath+0x63/0x70 2019-10-22T19:58:29+05:00 nas kernel: [ 267.889047] [<ffffffff8156a8c2>] int_ret_from_sys_call+0x25/0x93 2019-10-22T19:58:29+05:00 nas kernel: [ 267.895242] Code: 87 d8 01 00 00 85 c0 74 53 55 89 56 68 48 8b 01 48 89 e5 89 46 60 48 8b 41 08 48 8d 4e 18 89 46 64 48 8b 46 38 48 05 f0 00 00 00 <48> 8b 50 08 48 89 48 08 48 89 56 20 48 89 46 18 48 89 0a 31 c9 2019-10-22T19:58:29+05:00 nas kernel: [ 267.915517] RIP [<ffffffffa050fa8c>] send_vblank_event+0x2c/0x60 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 267.922264] RSP <ffff8800327fbba0> 2019-10-22T19:58:29+05:00 nas kernel: [ 267.925815] CR2: 00000000000000f8 2019-10-22T19:58:29+05:00 nas kernel: [ 267.929203] ---[ end trace dd4d613583dcfc34 ]--- 2019-10-22T19:58:29+05:00 nas kernel: [ 268.111260] ------------[ cut here ]------------ 2019-10-22T19:58:29+05:00 nas kernel: [ 268.115964] WARNING: CPU: 1 PID: 18840 at kernel/softirq.c:150 __local_bh_enable_ip+0x65/0x90() 2019-10-22T19:58:29+05:00 nas kernel: [ 268.307239] CPU: 1 PID: 18840 Comm: ffmpeg Tainted: P D OE 4.4.59+ #24922 2019-10-22T19:58:29+05:00 nas kernel: [ 268.315017] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./J1800N-D2H, BIOS F8 10/03/2018 2019-10-22T19:58:29+05:00 nas kernel: [ 268.325173] 0000000000000000 ffff8800327fb8a8 ffffffff812b96fd 0000000000000000 2019-10-22T19:58:29+05:00 nas kernel: [ 268.332767] ffffffff81722924 ffff8800327fb8e0 ffffffff8104917d 0000000000000201 2019-10-22T19:58:29+05:00 nas kernel: [ 268.340337] ffff880074481380 ffff8800744819f8 ffff880074481380 ffff8800715e7be8 2019-10-22T19:58:29+05:00 nas kernel: [ 268.347916] Call Trace: 2019-10-22T19:58:29+05:00 nas kernel: [ 268.350421] [<ffffffff812b96fd>] dump_stack+0x4d/0x70 2019-10-22T19:58:29+05:00 nas kernel: [ 268.355643] [<ffffffff8104917d>] warn_slowpath_common+0x7d/0xc0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.361753] [<ffffffff81049276>] warn_slowpath_null+0x16/0x20 2019-10-22T19:58:29+05:00 nas kernel: [ 268.367683] [<ffffffff8104c9e5>] __local_bh_enable_ip+0x65/0x90 2019-10-22T19:58:29+05:00 nas kernel: [ 268.373795] [<ffffffff8156a275>] _raw_spin_unlock_bh+0x15/0x20 2019-10-22T19:58:29+05:00 nas kernel: [ 268.379812] [<ffffffff810c464b>] cgroup_exit+0x4b/0xa0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.385132] [<ffffffff8104bacd>] do_exit+0x36d/0xab0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.390270] [<ffffffff810072a4>] oops_end+0x84/0xc0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.395316] [<ffffffff8103b44b>] no_context+0xfb/0x2b0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.400626] [<ffffffff81566535>] ? __schedule+0x275/0x730 2019-10-22T19:58:29+05:00 nas kernel: [ 268.406208] [<ffffffff8156653e>] ? __schedule+0x27e/0x730 2019-10-22T19:58:29+05:00 nas kernel: [ 268.411781] [<ffffffff8156653e>] ? __schedule+0x27e/0x730 2019-10-22T19:58:29+05:00 nas kernel: [ 268.417363] [<ffffffff8103b670>] __bad_area_nosemaphore+0x70/0x1f0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.423727] [<ffffffff8103b7fe>] bad_area_nosemaphore+0xe/0x10 2019-10-22T19:58:29+05:00 nas kernel: [ 268.429742] [<ffffffff8103bb96>] __do_page_fault+0x1c6/0x390 2019-10-22T19:58:29+05:00 nas kernel: [ 268.435583] [<ffffffff8103bd9c>] do_page_fault+0xc/0x10 2019-10-22T19:58:29+05:00 nas kernel: [ 268.440993] [<ffffffff8156bf02>] page_fault+0x22/0x30 2019-10-22T19:58:29+05:00 nas kernel: [ 268.446228] [<ffffffffa050fa8c>] ? send_vblank_event+0x2c/0x60 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.452779] [<ffffffffa050fb0b>] drm_send_vblank_event+0x4b/0x70 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.459512] [<ffffffffa050fb45>] drm_crtc_send_vblank_event+0x15/0x20 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.466692] [<ffffffffa0620bfb>] intel_atomic_commit_tail+0x32b/0x10a0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.474027] [<ffffffffa05887ab>] ? drm_atomic_helper_swap_state+0x14b/0x2f0 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.482710] [<ffffffffa0621d2e>] intel_atomic_commit+0x3be/0x4e0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.489532] [<ffffffffa0527aa5>] ? drm_atomic_add_affected_connectors+0x25/0xe0 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.497577] [<ffffffffa05274f2>] drm_atomic_commit+0x32/0x50 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.503946] [<ffffffffa058da76>] restore_fbdev_mode+0x156/0x280 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.511552] [<ffffffffa058f3ae>] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.521022] [<ffffffffa063dd34>] intel_fbdev_restore_mode+0x34/0xb0 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.528126] [<ffffffffa05a6029>] i915_driver_lastclose+0x9/0x10 [i915] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.534847] [<ffffffffa050c229>] drm_lastclose+0x29/0x130 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.540965] [<ffffffffa050c596>] drm_release+0x266/0x390 [drm] 2019-10-22T19:58:29+05:00 nas kernel: [ 268.546996] [<ffffffff811368ca>] __fput+0xca/0x1d0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.551950] [<ffffffff81136a39>] ____fput+0x9/0x10 2019-10-22T19:58:29+05:00 nas kernel: [ 268.556907] [<ffffffff81062760>] task_work_run+0x80/0xa0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.562392] [<ffffffff810020e7>] exit_to_usermode_loop+0xa7/0xb0 2019-10-22T19:58:29+05:00 nas kernel: [ 268.568580] [<ffffffff810023d3>] syscall_return_slowpath+0x63/0x70 2019-10-22T19:58:29+05:00 nas kernel: [ 268.574954] [<ffffffff8156a8c2>] int_ret_from_sys_call+0x25/0x93 2019-10-22T19:58:29+05:00 nas kernel: [ 268.581142] ---[ end trace dd4d613583dcfc35 ]---
  16. H_U_L_K

    SOS

    А то что в графе "свободно" цифра 18,6 гб не смущает?
  17. As you are trying to 'restore' a geniune synology unit, have you looked at their forums? There may be advice there. I dont speak Russian but looking at the thread there are links to a 1511 boot loader and how to edit the mac/serial (it looks to be the same process as for creating an xpe boot loader - of course If you could find the loader for the RS you might be able to 'reflash' the module. Also, if you have connected the DOM to a PC, have you looked at editing it using ofsmount and the hex editor and re-add the serial (which should be on a label on the unit)
  18. I can't remotely access the virtual machine: The address for remote connection is 127.0.0.1:9000 and it is not reachable, of course. Do you have any idea how to solve this please? I attached VirtualBox network and VM remote option
  19. It is working with 1.04b / 918+ only with DSM 6.2.1-23824 Update 6 DSM 6.2.2 not working.
  20. Нет новостей насчет последних 6.2 версий по Hyper-V? А в чем там сложность что 6.0 запускается, а более свежие нет? Надо драйверы пилить в загрузчике или что?
  21. Bonjour, @EVOTk Tout d'abord, merci beaucoup pour ta réponse rapide. Comme tu l'as demandé, j'ai fait mon propre sujet (https://xpenology.com/forum/topic/22101-besoin-daide-pour-problème-hdd-non-visible-dans-dsm/#comment-124059). Désolé d'avoir "pollué" ce post, et encore merci d'avoir pris le temps de ma répondre. Cordialement,
  22. Merci beaucoup pour vos réponse. En effet, j'ai pris la version DS3615XS car a priori la plus "compatible". Sur un autre forum, j'ai trouvé ceci: On vois qu'il utilise le loader v1.03b, mais avec la version DS3617XS, donc, ce n'est pas le même loader. Des drivers supplémentaires? Le matos qu'il utilise est quasiment similaire au mien : G4400, DDR4 2133, LSI 9260-8i. Quand pensez-vous? J’essaie la version loader v1.03b - DS3617XS? Par contre, si je comprend bien, il utilise la version DSM 6.2 update 2. (c'est a dire? version 6.2-23739-2, c'est bien ça? Je commence a voir du mal a suivre avec toutes ces versions...) Donc, si je récapitule, ce qui devrai fonctionner serait le loader v1.03b, version DS3617XS, avec DSM 6.2-23739-2. Après, pour l'histoire de la VMWare ESXi, ouch, ça m'a l'air bien compliqué. Alors oui, je suis pas très fan et a l'aise avec la virtualisation, donc si je pouvais rester en version BAREMETAL, ça m'arrangerai énormément. Je suis assez deg de pas pouvoir rester en 6.2.2 update 3 car tout à l'air de bien fonctionner sinon, grrrr, galère. Après, si je ne dis pas de bêtise, en version 6.2-23739-2, je devrai tout de même bénéficier des dernières versions de Plex, Logitech Media Server, et autres applis . . . J'attends vos réponses, mais je pense que je vais tester cette solution.
  23. Adic

    SOS

    dsm 6.1.7,установлено 20гигов оперативки,видны только 16,как исправить?
  24. "Так что скорее всего 6.1.7 это максимум." -> "Апнулся до 6.2 с 6.1.7" = 6.2😉 Но не выше.
  25. p.s For me it was easy to create a acronis backup image, I have a spare DS1511+ laying arround atm, and can put in a Synology usb flash drive, use a keyboard mouse and monitor.. But these cards are using a regular kind of mini usb plug, there are adapters for this I found in the past. you should google it, there are other solutions for this..
  1. Load more activity