darthf1

Fixed it! I was looking further into the grub.cfg and the first menu entry there was not the ESXI one. So i removed the first two options only letting the ESXI menu entry active. And now it worked fine. *DOH*

Yeah i used the same application, but using the .img or the converted .vmdk is giving me the same results. Yes, all my disks are on the SATA controller. This is the exact same setup which was working on the 3615xs on loader 1.03 with DSM 6.2.

It was 4, i changed it to 666 and although i have more available slots it didnt change anything

Well the most important data is backed up, but i would prefer to fix this over to starting over again. Unforunately i dont see any disks under "External Devices"

Hi, Yesterday i tried to created a new ESXI VM based on the new 918+ 1.04b loader by Jun. It booted fine, so I shutdown the VM and attached my SATA controller as a passthrough device. I got the option to migrate from the 3615xs to the 918+ and all went fine. After my first login, I got the message that my Volume1 had crashed. Looking at the disks that Synology detects, i see the following: - 2x 4TB WD RED - 1x 50mb VMWare Virtual SATA HDD What i would expect to see here, are my 4x 4TB WD RED. The 50mb VMware hdd is new for me, which make me believe i did something wrong in the VM config. So i SSH'd into the device, and with fdisk I learned that all my 4x 4TB disks are detected. Theyre just not visible in the WEBUI. The RAID 5 (/dev/md2) consists of only 2 of 4 disks. Next thing is that I used mdam to stop and recreate the /dev/md2 raid5. I mounted the /dev/md2 to /volume1 again and I can see all my original files there. This makes be believe theres nothing wrong with the disks. After this, i dont know how to proceed. I recreated the raid with mdam, but in the webui i still can only see my 2x 4TB and 1x 50mb. After a restart, i get the same volume crashed errors and I have to recreate the raid again. Does anyone have any experience with this? My VMDK file synoboot.vmdk This VMDK just links to the .img file. I have also tried converting the .img to a .vmk, but i get the same result. Storage Manager VM Settings ESXI Hardware / Version

Hi all, I currently have Xpenology 6.1.4-15217 Update 5 running on baremetal with Jun's loader 1.02b. I want to do more with VM's and the VMM is currently not doing the trick for me. Is it possible to migrate my current baremetal installation to an ESXI installation, without losing data? (I can live with losing my config) If it helps; i have a spare SSD which i could use to install the ESXI server on, and add as a first HDD, so i dont have to touch the Xpenology's HDD's.

Hi all, Specs: DS3617xs with Juns loader I3-7100 8GB DDR4 MSI B250i Gaming Pro AC Im having troubles running Windows 10 on a VMM. I tried multiple versions, but they ultimately end in the same result: When I boot the VM with Windows 1704 ISO (Creators update), I get instant BSOD so I can't even get to the installer When I boot the VM with Windows 1607 ISO (Anniversery Update), I can get to the installer, load the Virtio HDD controller driver and the installation starts. When the VM reboots after installation I get the BSOD. When I boot the VM with Windows 1507 ISO I can get through the install and boot into Windows without issues. Then I continued with installing the neccesary drivers. Then i started Windows update, and the upgrade to the latest Windows 10 has started. After the installation is finished I get a BSOD after first reboot. The BSOD i'm getting is: Kmode_exception_not_handled. In the blue screen, there is nothing mentioned about a driver, so i'm not sure which driver triggers the BSOD. From the installation of the third bullet, I enabled the legacy boot menu and started Windows via Safe mode, but thats also giving me an instant BSOD. Disabling fast boot doesnt help either. I even tried all images above and incorporating the Virtio drivers in the image, but that doesnt help me either.