Search the Community

Showing results for tags 'esxi'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • GERMAN
    • KOREAN

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 39 results

  1. Hi, for quite a while I'm trying to find out why hard disks do not spin down after the set time with DSM 6.x and ESXi Hypervisor (6.0 or 6.5) using Jun's loader. Hard disks are connected to a passthrough SATA Controller (onboard, also tried PCIe). Exactly one and the same setup is working bare metal, also with DSM 5.2 on ESXi. I even tried using a boot iso (as with DSM 5.2) that uses the passthrough USB boot stick (like with bare metal) instead of synoboot.vmdk/synoboot.img combination. No spindown, hdparm -y does a spindown, however disks wake up at once again. I can't see any differences in the logs between running bare metal or on ESXi. Would appreciate any further ideas.
  2. Bonjour, je suis dans un environnement vmware esxi 6.5 je me pose la question suivante: si je mets une vm 3615xs, est-ce que si je lui affecte 4 vCPU les 4 seront utilisés? ou suis-je obligé de passer par la vm 3617xs étant donné que le 3617xs est un model avec un proc 4 cœurs contrairement au 3615xs qui est model avec un proc 2 cœurs. mog
  3. Turned my trusty HP54L off over the Christmas period for a few days when I wasn't using it. Came home, booted it and Esxi won't boot. While trying to boot, it gives: error loading /s.v00 fatal error: 6 (Buffer too small) This sounded to me like a RAM issue. 2GB RAM is successfully detected upon boot. When I initially installed Esxi years ago, I followed a guide to hack the Esxi install to allow 2GB RAM. I took the RAM out, gave it a technical blow, put it back into the other RAM slot. Re-booted and same error. Again, 2GB RAM is successfully detected. Any suggestions on how to troubleshoot further?
  4. Hello I install xpenology 6.1.3 with bootloader 1.03b on esxi6.5 I want to attach physical disk to xpenology, so I mount disk as RDM. First I set disk like this but I fall in DSM install loop. So I made 8GB virtual disk in my ssd and attach it it like this. Than the installation process was find but when I made RAID group and volume and reboot my vm, all the RAID group and volumes are gone. I'm dealing this problem around 12hr but I don't know what the problem is...... Plz help me
  5. Ich habe hier auf zwei HP Microserver ESXi 6.5u1 laufen. Auf beiden habe ich zusätzlich ein vSwitch ohne NIC mit 9000er MTU erstellt. Auf beiden ESXi Host habe ich jeweils ein DS3617sx 1.02b mit folgender Konfig: - Nic1 ist auf vSwitch0 (mit pysikalischer NIC, MTU 1500) - Nic2 ist auf vSwitch1 (ohne pysikalischer NIC, MTU 9000) Bei einem von beiden Hosts, ist DSM nach der Umstellung von Nic2 auf MTU 9000 über kein Interface mehr erreichbar, so als wenn generell auf MTU9000 umgestellt würde. Bei dem anderen Hosts funktioniert das Ganze interessanterweise problemlos. In beiden Fällen handelt es sich um eine ehemalge DS3615sx 1.01 installation, die auf DS3617sx mit "Daten behalten" migriert wurde. Ich hab einfach das img genommen und die grub.cfg angepasst, mit StarWind V2V Image Converter zu einer ESXi Server vmdk umgewandelt, diese in den Datastore hochgeladen und dann die Bootfestplatte in der VM-Konfig ausgetauscht. Um die DS3617sx wieder zum leben zu erwecken, habe ich wieder die alte Bootplatte von DS3615sx genommen, gestartet und neu migriert. Dann VM gestopped und wieder die DS3617sx Bootplatte zu verwenden und erneut zu migrieren. Sprich: ich bin wieder auf dem Stand vor der MTU9000 Umstellung. Hat jemand eine Idee warum die Umstellung von Nic2 auf MTU9000 auch die MTU von Nic1 berührt hat?
  6. Всем привет. Столкнулся с проблемой вопроизведения фильмов в Video Station. DSM установлена на esxi 6.0. Сервер Supermicro, Adaptec Raid, диск WD 3Tb Green просто как Volume. Ресурсов нормально, Диски в DSM подцеплены как vmdk-ашки, полный проброс не могу себе позволить, живут еще виртуалки) Смотрю фильмы с iPad и ТВ-приставки на Android. Жил довольно долго на DSM 5.2, но сломались обложки, обновился на 6.0, какое-то время тоже было хорошо. Где-то месяц назад стал замечать, что пошли лаги (долго открывается, перематывать вообще не реально, некоторые видосики вообще не играет). Единственное что стояло, так это авто-обновление Пакетов. Соответственно обновился Video Station. Первое - подумал хард, проверил - ок. Дальше пробовал ставить более старые версии VS. Пробовал включать Video Conversion for Mobile Devices, проц грузит, толку нет. Обновил на 6.1, картина не изменилась. Собственно само странное поведение выражается тем, что сначала загрузка по 80Мбит, через минут 5 падает до загрузки равной битрейту (например в 20мбит), Причем странно, что как на чтение, так и на запись идет нагрузка. Если фильм остановить и начать играть заново, картина повторяется. Вот собственно скрин. Начал играть в 22:56 до 23:12, потом заново. Если смотреть это же фильм, но через DLNA или через SMB, все летает. Но так удобна эта чертова Video Station, что не хочу отказываться. Спасибо за любые советы. UPD, выяснилось, что такое происходит только с mkv.
  7. I have one ITX box and two SO-DIMM rams on J3455 but J3455 graph card not support pass-through in ESXI I'm searching ITX board and graph card with these features: 1. ITX board with 2 SO-DIMM slot, 4 SATA slot, 1 PCI-E 16x slot, support VT-D, support USB & SATA pass-through on ESXI 2. graph card support pass-through on ESXI I'm not sure whether ASROCK H110M-ITX can do so and it have 2 DIMM slot. Is that possible? Thanks.
  8. Hello, I have a nice N54L running 6.0.2 bare metal and I'm wondering if I should migrate to ESXi hypervisor. I know not much about ESXi, but would it be possible to make xpenology "see" an intel processor instead of an amd ? (would make 6.1.3 migration easier) Is there anything special to know about the migration ? Is this even possible without wiping all data ? (have 4x4 To in AHCI RAID 5) Regards
  9. Hello all, Unfortunately, I was unable to install 1.02b on esxi 6.0 Update 3 by following different guides throughout the forum. So after a few hours of testing, I wrote myself a guide for future use. I tested these situations: 1. DS3615 baremetal in basic disk -> VM 2. DS3615 baremetal in raid 1 disk -> VM 3. DS3617 baremetal in basic disk -> VM 4. DS3617 baremetal in raid 1 disk -> VM 5. VMs back to baremetal in both basic and raid 1 disk without losing any data. My personal guide is attached as a PDF. Install on ESXi 6.0U3.pdf
  10. Im running ESXi 6.5 on a HP Proliant MicroServer G8. I managed successfully to run the latest XPEnology on a new VM and I attached a couple of virtual disk on it for testing before I transfer my data. Everything looks fine until I tried to mount my USB Disk which will store my MacBook's Time Machine Backups. The same disk can be mounted on my Win Server VM but, not on the XPEnology one. I even tried to hard mount it via SSH without any luck. I installed vmware tools but nothing again. I tried both USB2 and USB3 ports. What else would you advised me to try in order to mount that disk?
  11. I'm out of ideas of how to debug this, but perhaps someone else knows what's going on. This is probably not an Xpenology specific issue, but I'm sure others here have experience using the LSI 9211-8i and ESXi together. I recently did a new build for my NAS with the following hardware: Ryzen 5 1600 ASRock B350 Pro 4 Mobo WD Green m.2 SATA SSD (used as VM datastore only) LSI 9211-8i SAS Controller I am running ESXi 6.5u1 on this setup which was perfectly stable until I added the LSI 9211-8i SAS Controller, since adding this card the system crashes if left idle for more than 30 minutes. Timeline of events: Initially using a LSI 3081E-R controller in pass-thru mode (with test drives since I didn't realise >2TB drives were not supported when I picked up the card for $30.) Online - Several weeks without issue until my LSI 9211-8i controller arrived. Added LSI 9211-8i controller to DSM VM in pass-thru mode with 4x 4TB WD RED HDDs Did disk parity check performed on new SHR array. Took about 8 hours. Offline - Less than an hour after parity check completed the system 'hard locks'. Thought it might be a one-off incident. Rebooted the system, did another parity check to make sure everything was ok. Offline - Again, less than an hour after parity check completed the system 'hard locks'. Updated the firmware on the LSI 9211-8i to v20 using IT mode. Thinking the problem was solved as I was now using ESXi supported firmware, started a data transfer task of 8TB of data, this took about 18 hours and the system stayed online the entire time without a hitch. Data transfer finishes, feeling pretty confident the firmware upgrade has worked since it's been online for this long, spend a few hours doing benchmarks and setting things up. System was online for over 24 hours. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. Thinking the issue might be IOMMU pass-thru support, I disabled pass-thru mode, installed the official driver from the vmware site for the LSI 9211-8i and mounted the disks into the DSM using ESXi Raw Disk Mappings. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. Realised it's only crashing when the system is 'idle'. Looked into power saving modes, disabled "C-State" and "Cool 'n' Quiet" in the host bios. Also disabled all power saving features in ESXi. Offline - An hour or so after I stop 'doing stuff' with the system, it's hard locked again. This morning I hooked up a screen to the host in an attempt to see if there was a PSOD or any message before it locks, there was not - just a black screen. System not responsive to short-press power button or keyboard. Offline - less than 40 minutes after sitting idle from boot, it's hard locked again. In addition to the steps taken above, I have tried to find a reason for the lock ups in the ESXi logs, there is seemingly nothing, one minute it's working fine, then nothing until it's booting up again after I power cycle the system. There are no core dumps. Each time nothing was displayed on the screen of the host . It just seems odd the system would crash only when sitting idle - it would make more sense if it was crashing under load. Now these issues only started to occur once I added the LSI 9211-8i to the mix, the LSI 3081E-R did not cause these same issues. Do I just have a dodgy card? I don't want to buy another LSI 9211-8i if I'm going to have the same issues. Is there another card I should get instead? Are there any other settings I should try to make this system stable?
  12. Bonjour, je voudrais savoir comment faire pour créer une sur vmware en partant du loader en .img ? soit avec ce loader ou bien celui ci D'avance merci
  13. I have installed multiple XPEnology DS3617 on ESXi server, and setup file sync using DSM's "Shared Folder Sync". Recently, there has problem in "Shared Folder Sync", an error of "Operation failed" is prompted when I press the [Create] or [Edit] button in the task list. This feature should works before, I'm not sure if any recent update in package center cause this issue. Recently, I have updated the "File Station" in package center, and a new version DSM 6.1.3-15152 Update 3 is ready to update, but I have not update yet. Anyone here encounter such problem in "Shared Folder Sync"? Is there any thing I can do to solve this issue? Thanks in advance.
  14. Bonjour, Je suis actuellement en pleine migration de serveur. J'était sur un ESXi en 5.5. J'avais un DSM 5.x. Aujourd'hui je passe sur un ESXi 6.5, cependant j'aimerais profiter de cette migration pour passer sur du DSM 6.x. J'ai essayé pas mal de choses que j'ai vu sur le net, ici et ailleurs. Rien n'abouti, VM qui de démarre pas et j'en passe. J'aimerais repartir de 0 en suivant vos conseil, vos lien de qualité. Merci d'avance pour votre aide.