oktisme

Even on the real DSM there's no protection in the boot loader, so DockerDSM not having a boot loader doesn't mean anything. Well, to get it working right now, yeah. If you really want it running in QEMU, there's this thread on the QEMU mailing list about adding e1000e emulation. I havent checked it all so I don't know if it got merged or not.

Yeah but VirtualDSM talks with the real DSM to get some info about CPU, serial number, and some other things. You can't just pick it up and put it in KVM somewhere else. You could emulate the host's side of the communication, or patch VirtualDSM.

It's totally possible to run the VirtualDSM version instead of one made for real hardware. That's not the problem. The problem is that we don't have the drivers for any non-Synology hardware, and we can't compile them since Synology hasn't realease the kernel source code, or at least the kernel headers. Without that, no matter which version you want to run, you can't do it on hardware for which the version doesn't have the drivers. It's perfect for virtualisation in KVM. VirtualDSM uses VirtIO drivers, which are, AFAIK, only supported by KVM.

Once you add another disk and let time to the RAID 1 to rebuild you're good, but before that it's the only place where it is. The other disk (Boot) doesn't have the install.

WHAT?! NO!! You can't remove the 8GB, this is the ONLY place where it is installed...

By doing that, you're trying to run the v6 files with the 5.2 "core". I don't even know on how many levels of wrong this is, but even if it did work you would not get anything over staying with 5.2.

Yeah this has to do with one of the patch which doesn't fulfill all the operations required to tell the "boot steps manager" that everything is ok, so it just waits until it times out before letting you log in. As per this comment in usr/syno/etc.defaults/rc.sysv/serv-bootup-timeout.sh # Increase bootup timeout from 180 to 600 when pgsql is update database it looks like your observation of 3min is spot on.

Thanks for the info. I created one with v10 hardware from scratch. Changes: - Both disks are now SATA (instead of one SCSI and one SATA) - Everything is v10 If someone could test it in ESXi and report back, thanks. DSM 6 (HW v10).7z

That's not the only file. There's protection in the web code from, IIRC, as far as 4.3. Plus libsynosdk which has some... irregularities when running on non-Synology WRT networking and the serial number. Even better: you can install linux and recover/use your drives from there (see How can I recover data from my DiskStation using a PC?).

Sure DSM 6 (11 No SS).7z

Use a clean drive and do Install (only once) and then Run.

Yep, that's what I'm referring to by As for it's because the Install part uses XPEnoboot, while the Run part is, mostly, unaltered Synology.

Perhaps the last post from Lost ability to boot from ISO - ESXi 6.0

In the current state, it can't run in VirtualBox since none of VB's NICs are supported.

That's what I'm telling you. You don't just have to have the ISO in, you need to tell you VM to boot from it. The black screen you get is your VM trying to boot from the drive which has nothing to boot from...

After the install, your VM will try to boot from the HD, but that's not where the boot is. You need to make it boot from the ISO every time. Moreover, DSM resets the BIOS, so you can't change the boot order in the BIOS (at least not in Workstation).

If you boot it with Run and find.synology.com is prompting you for installation, it means that it can't see the "DSM 6.vmdk" drive, which contains the installation of DSM.

Unless you are installing it manually with the ISO and the .pat, you MUST NOT use the Install option. THAT'S WHY THERE'S NO TIME TO CHOOSE.

Here are the file if you want to install it yourself. Here are some things to note about the configuration of the VM before installing: - It supports only a handful of NICs. On Workstation I configure it to use the e1000e driver, plain e1000 doesn't work. - It only sees SATA disks. - If you want console access (I don't know how that would work on ESXi though) you need to add a serial port. - You need 2 SATA HDs: one to install Synology on and one to use as storage. How to install: 1 - Boot with the Install option 2 - Go to http://find.synology.com 3 - Upload the .pat file 4 - Reboot with the Run option. You only boot with Install once 5 - Go to http://find.synology.com and configure 6 - Done! The reason the VM I posted uses a Boot HD is because DSM resets the BIOS and you have to manually (ESCAPE during boot) tell it to boot via ISO. I don't know how this will play out on ESXi. DSM_DS3615xs_7393.iso DSM_DS3615xs_7393.pat

Here, I downgraded it to 10.x since it tells me that 9 doesn't support SATA, which is required, and that 10 is supported by ESXi 6.0. DSM 6 Workstation 10.x.7z I haven't tested all packages, but so far they work. Volumes are accessible and stay mounted. I just tried the document viewer with pdf, xlsm, docx and it works. I can configure the indexed search and it tells me that the indexing is done; don't really know how to test if it really works though.

I don't plan on doing that ATM.

You MUST NOT boot it with Install (that's why there's no time to choose). Let it boot, and go to find.synology.com. If you've booted it once with Install, you should restore the latest snapshot to make sure it didn't mess anything. And yeah, there's no console on screen with Synology's kernel. So after the "Booting the kernel" message, the screen doesn't change but it's running in the background. If you really want console access, read the initial post.

I'm pretty sure they are plenty capable of doing what I did, but just don't want to for some reasons.

I found the protection code and patched it. I guess this isn't a new protection with v6 and that XPEnology did the same thing for v5, so I don't know why a v6 hasn't already been done. It's somewhat already possible to install that on a physical machine, but the only drivers included by Synology are the ones for their hardware. To make it usable somewhere else you'd first need to compile the drivers.

So I got DSM 6 (6.0.1-7393) working (volumes stay mounted). Here's a VMware VM if anyone wants to try it. You can use VMware Player to run it. Just add a new SATA hard drive before booting. If you want console access, use PuTTY to connect to the named pipe \\.\pipe\com_1 (speed 115200) to connect to the VM's serial port. This is pretty much it: add a SATA disk, boot and go to http://find.synology.com, configure and you're done. DSM 6.7z