All Activity

This stream auto-updates     

  1. Past hour
  2. Salut, @TaliskerBien joué déjà pour être parvenu jusqu'ici Plusieurs choses : ce que tu appelles datastore, ce n'est pas ça. Un datastore est un espace de stockage attaché à l'hyperviseur sur lequel on stocke les données des VM (<=> les vmdk, les fichiers de descriptions de VM, certains ISO, ou autres). Dit autrement, un vmdk n'est pas un datastore et un vmdk est stocké sur un datastore. Ton pb provient du fait que tu as alloué les vmdk au controlleur SATA0:1 alors qu'il faut les mettre sur le SATA1:x. toutefois le seul vmdk qui doit rester sur le SATA0:1 est celui qui fait 50MB (celui qui correspond au loader) Si tu as 3 disques de 2To alors oui je te conseilles fortement de te lancer dans le RDM : Si tu suis bien le tuto tu devrais t'en sortir. A la fin tu devras avoir 3 fichiers vmdk de 2To (1,81To réelle) sur le datastore. Mais en fait ce n'est qu'un lien symbolique (sorte de raccourci) vers tes disques en aucun cas tu auras 3 vrais fichiers qui pèsent chacun 2To sur le datastore.
  3. Today
  4. hello Donc voilà suivant tes conseils j'ai installé un ESXi sur le server J’ai ensuite déployé l'image dsm Mais là je bloque, j'ai alloué 3 datastores à l'image mais il continu à me dire qu'il n'y a pas de disque alloué ... il serai peu être mieux d'allouer les disques directement en raw que de créer des datastors (fichier) dessus, non ? Mais la je ne sais pas comment on fait merci
  5. Based on the filename of the bootimage, that bootimage is the specified DSM version, so you might need the assosciated .PAT file to complete the install before adding the update 6.
  6. I've tried the last set of extra/2.lzma and it works well for my DS918+ (6.2.2) on top of esxi 6.7. While it's running fine - I'm having issue with mptsas crashing on load when I enabled LSI SAS - is t his expected and similar to what is happening for the ds3615x ? Also I didn't find the mpt2sas in any of the extras bundle - I assume if the former is not working that won't help. On a side note the atlantic driver also crashed when I tried passthrough of the xc card- not sure if it would work with SRIOV but it's not an option w/ esxi in my case anyway. The card works well with vmnet3 at 10gb under esxi so no biggy there Thanks! -M
  7. Я и не говорил, что проблема в Syno. Я как раз написал, что проблема в роутере. Роутер Qtech QFR-200-4T-W
  8. I think one of this option will be solve my problame for the future, I have a single gigabit intel Nic at home, never tried with just that, only with integrated, the reason is that I want to make my server to be Dhcp server, with one input lan from modem and an output to switch.
  9. Can you explan me please, what is that mean? Sounds good, keep it up! Thank you for you help
  10. @trox I worked around my predicament by ordering HP NC360T dual-gigabit NIC from eBay. This one seems to play nice with 6.2.2 without any extra.lzma changes. They are about $11-14.
  11. Можно и не балансировать конечно. Речь о том, чтобы завести правила которые маркируют трафик средствами iptables с конкретной пары ip:port и направляют в отдельную таблицу маршрутизации, где будет другой шлюз по умолчанию. В open wrt это можно реализовать как в ручную так и через специальный пакет - mwan3.
  12. Outcome of the update: SUCCESSFUL - DSM version before update: DSM 6.2.2-24922 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs and DS3617xs and JUN'S LOADER v1.04b DS918+ - Using custom extra.lzma: No - Installation type: VM - ESXi 6.7u3 - Additional comments: Reboot required
  13. Yesterday
  14. It's time to find something else to do with my old N40L. I have an Asrock FM2A88X-ITX+ with 16GB of DDR3 and an A8-5600K APU and I want to use it to run XPEnology. Any idea if this combo is compatible ? Which bootloader and DS version can I choose ? Thx
  15. My board has 6 sata all being used atm I'm willing to try a clean install i have 3 spare drives, CPU i5 4460 What you mean by this? "if you want to stay with 3615/17"
  16. yes, discovered that lsi 9211 controller do not worked, only mpt2sas driver from dsm itself (6.2.2) does work atm (had to organize a new test computer to get the lsi 9211 with 3615/17 running), still looking whats the cause of the crash, driver loads when controller has no disks connected but crashes when disks are connected also ata_piix, mptspi and mptsas driver do not work (mostly used for vmware and kvm i guess) , have removed them for now but network drivers are mostly latest and working
  17. with the right usb flash drive and the right tool you can do what manufacturer in china do and enter your own vid/pid i did this last year but had not much use for it and gave it to someone here in the forum i was using DynaMassStorageProductionTool, maybe even wrote about it here in the forum (can't remember) that was the initiator article edit: still have one for testing Device Type: Mass Storage Device Protocal Version: USB 2.00 Current Speed: High Speed Max Current: 500mA USB Device ID: VID = F400 PID = F400 Device Vendor: Synology Device Name: Diskstation Device Revision: 0100 Manufacturer: Synology Product Model: Diskstation Product Revision: 0100 Controller Vendor: SMI Controller Part-Number: SM3259AA1 - ISP 161122-DG1 Flash ID code: 45DE9493 - SanDisk SDTNRGAMA-008G - 1CE/Single Channel [MLC-16K] -> Total Capacity = 8GB
  18. Tu as bien changé le pid/vid dans le fichier GRUB ? Si oui essaie une autre clé voir les autres ports USB disponible. Courage ça va le faire
  19. no, if you updated to 6.2.2 the only thing that helps is a working extra.lzma (that can be copied to usb after the update and failed boot) or a propper downgrade just as a example to access your data you can also boot up open media vault from a different media and it will detect the raid with your data (its just a normal linux mdadm and lvm) - that's my plan B when dsm fails and and i'd need access to my data hopefully i will be out of test hardware soon an will stop finding new problems in the 3615/17 extra.lzma, still need to write a lot of text as its not so simple as just using a new extra.lzma with 3615/17 and loader 1.03b, the loader needs to updated too i have a good amount of ideas what a want to test and do for a new 918+ extra.lzma
  20. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 3 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: Yes (strippped out some drivers) - Installation type: BAREMETAL - Asrock J3455-ITX. - Additional comments: Couple of reboots required - took a while.. Just leave it..
  21. Thank you @IG-88 for your quick answer. Just for example: If I update it accidentally to 6.2.2 and and the problame will be the same, the only thing is enough to change the extra.lmza to the original and after that it goes back to 6.2.1, and can reach my datas? Sorry for these stupid questions I'm also new here, but I couldn't find answers in the forum to my exact problames :)) I'm patient, and can wait for your 918+ project. atm.. thanks for your hard work
  22. Outcome of the update: SUCCESSFUL - DSM version before update: DSM 6.2.2-24922 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXI 6.7  - Additional comments: No
  23. you dont loose your data when a update goes wrong, you just loose access to your data, the update only changes the system partitions on the disks and does not touch you data raid, in such a semi brick it can be enough to add a new extra.lzma to the usb and on next boot it finishes, had that last week with someone accidentally updating to 6.2.2 with a 3615, test version of a new extra.lzma fixed it so your date are even more safe in a semi brick state of a dsm installtion, no trojan or ransomeware will be able to harm your data :-))) if my extra.lzma 918+ 6.2.2 loader 1.04b does not work then you cant update for now, you can try if a different nic solves your problem atm i'm doing 3615/3617 extra.lzma, after this i will revisit the 918+ and look more closely into it
  24. J'ai pris exemple sur "@prad" Avec le loader JUN'S LOADER v1.03b - DS3615xs et le DSM 6.2.2-24922 Update 2 J'ai essayé avec le DSM 6.2.2-24922 qui fait un taille de 276 670 Ko puis avec le Update 2 qui fait une taille de 30 341 Ko et le Update 3 qui fait une taille de 41 748 Ko Je part du principe qu'il faut en premier installer le 6.2.2-24922 avant de procéder aux Updates J'ai formaté la mémoire interne (une mémoire flash en SATA), je n'ai pas créé de partitions pour laisser le système faire le nécessaire. J'ai également essayé directement sur un disque dur HDD en SATA. J'ai essayé de refaire l'installation sans passer par le premier DSM avec et sans avoir reformater. J'ai toujours le même résultat : C'est évident que je dois louper quelque chose. Je vais relire les tutoriels que vous m'avez mentionné. Merci.
  25. Hi @bateau @IG-88 I've exactly the same problame with my optiplex 7020. - Outcome of the update: FAILED - DSM version prior update: DSM 6.2.2-24922 Update 3 - FIRST INSTALL - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Dell Optiplex 7020 (I7-4770 - 8GB - NIC: I217-LM) The only DSM 6.2.1 works me fine, but after I wanted to make a fresh install of 6.2.2 update X, install goes to the end and after restart, network is not respond, cant find my server through synology assistan, ip scanner and my router also cant see it ( seems to turn off), but nic is working and blinking. Is there any solution or extra.lzma? How can I try a new update safely without loosing all my data? (try with new pendrive or same pendrive but with a fresh hardrive?) I tried with your extra.lmza and extra.lmza2 test6 @IG-88 but the issue is the same. Thanks for help.
  26. Outcome of the update: SUCCESSFUL - DSM version before update: DSM 6.2.2-24922 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: No - Installation type: BAREMETAL - Dell Optiplex 980 - Additional comments: reboot required
  1. Load more activity