OllieD

I created a topic under developer discussion so that meaningful work could be started on the development of a new loader. I clearly posted that it didn't work and the errors presented. People didn't understand and turned my thread into off topic discussion which caused the mods to merge it here. The upgrade will install successfully because the system is still DSM 6 until it reboots, at which point it becomes DSM7 and incompatible with the loader. DSM 7 does not work with the current loaders, do yourself a favour and stop trying to install it until a new or updated loader is released.

I have just received access to the DSM 7 Beta if any developers need any pat files etc to work on a new loader. Current loader fails to boot with: Let me know if I can assist with anything. Kind regards, Ollie

Looks like i will have to rollback to 6.2

Doesn't seem to work for me on 6.2.1 Just gone from ESXI to Baremetal. Kernel module seems to load but spits out the following: [ 265.910782] genirq: Flags mismatch irq 0. 00000080 (hpilo) vs. 00015a20 (timer) [ 265.910978] hpilo: probe of 0000:01:00.2 failed with error -16 The helper just returns this: This program requires the host to have a HP Integrated Lights Out 4 (iLO 4) BMC Would appreciate any help with getting this working 😀

Thank you @jun and @Polanskiman for your continued efforts to support this project. Could I please ask if it is possible to get an actual Console from the Loader rather than the "screen will stop updating" message. For many reasons, including a networking failure, having console access is useful! It was always present in loaders before to my knowledge and I am unsure of why it was felt necessary to remove it.

It's to have an synology VM within synology I guess Sent from my iPhone using Tapatalk DSM6 brought the ability to create virtual DSM servers within a single Synology server in order to share a device between users. Nothing to do with XPEnology. Unless you want to run multiple DSM servers under one install. Sent from my LG-H815 using Tapatalk

I migrated from an n54l to a G8 and the first month or so were hell because of this. I ended up loosing the majority of my data trying to resolve it. The basics of it are. when the Raid controller in the Gen8 is configured for AHCI mode it will not cooperate with ESXI which causes port resets and crashes the vm's (and sometimes the whole system). The agreed workaround is to enable the raid controller and if you want to add a single drive configure it as an array consisting of a single disk in raid 0 mode (single disk as raid 0 is treated as passthrough) I have 5 single disk raid 0 arrays. 4 of these are passthrough single disks to ESXI 6 and since i configured it this way i have not had a single crash or error.