oktisme
-
Posts
25 -
Joined
-
Last visited
Posts posted by oktisme
-
-
Just an update looking a bit in the Virtualisation package I see it's just QEMU. So nothing fancy I would say.
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.
-
I was looking around in this DSM 6 a bit. I had an idea, would it not be possible to extract the VM images or something like this from the in beta Virtual DSM and see how they made them work. Cause I see when you make a virtual DSM you also need to go true the install with it's own pat file. I know this version is a little bit more limited then the normal one but for must users it could be sufficient. And it could also be a pretty versatile build, cause it's perfect for virtualisation.
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.
cause it's perfect for virtualisationIt'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.
-
Removing it should not create any issues, as far as I know DSM gets installed on all drives; but didn't tried it on 6 so far...
WHAT?! NO!! You can't remove the 8GB, this is the ONLY place where it is installed...
-
If you have used the ISO file to do this, then you need to make some modifications to enable "run" to work.
I have got as far as using this to create a VMWare machine from scratch and I have been able to migrate data (but not settings or users) from 5.2.
You need to use a utility like winiso to edit the isolinux/isolinux.cfg file to look like this:
UI menu.c32 PROMPT 0 TIMEOUT 50 DEFAULT run MENU TITLE Synology LABEL run MENU LABEL Run KERNEL ../XPEnoboot APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 vga=0x305 LABEL install MENU LABEL Install KERNEL ../XPEnoboot APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 console=ttyS0,115200 upgrade=6.0.1-7393This also gives you the console listing.
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.
-
One other thing I noticed is the long time before you are able to login, about 3 minutes after I start the vm. If you try before that you get a message : system is getting ready, try again later. Maybe that's how dsm6 work's, I don't know.
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.
-
I figured why the package that oktisme provided did not run as expected on esxi. Neither the orignal (=hw version 12, snapshot) , nor the downgraded one (~=hw version 11, no snapshot).
The harddisk "dsm 6.vmdk" is created using hardware version 12, which is not supported by any esxi version (even esxi 6.0u2 does not!).
Even when the provided vm is downgraded to hw version 10 or 11 using "change hardware compatibility" in vmware workstation, the harddisk is still hw version 12! I took a look at the vmdk with a hex editor - the string ddb.virtualHWVersion = "12" is always present. So the harddisk gets not downgraded.
That said: there is no way to use the ootb solution in esxi. It is like oktisme said: if the migration wizard appears on each reboot, it is because the "dsm 6.vmdk" can't be accessed by the esxi...
What can be done is to remove the disk "dsm 6.vmdk", add a new one and use the iso installer to install dsm6.
@oktisme: i know that you provided a hw version 11 version of your vm, but can you recreate a new vm based on hw version 10 - it is a pitty, but downgrading the hw version using vmware workstation is not sufficient here.
@oktisme: converting it to hw version 10 using the vmware converter worked, there is no need to recreate the vm. Thanks for all the efforts you put into making this work!!
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.
-
The only protection feature I could find is the closed source kernel module synobios.ko which is not a new way for Synology to "protect" DSM.
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.
could I then just buy a Synology NAS and move my disks there without losing data?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.
-
boot ok on terminal, but no network card detected
Yep, that's what I'm referring to by
none of VB's NICs are supported.As for
it is strange that it works for the installation, but not for the classic bootit'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
Ran into an issue booting to a DVD.What I had to do was set the VM Options | Boot Options | Boot Delay to 5000 milliseconds. Mount your CD/DVD as you normally do.
Power on the VM, you'll see the Post BIOS screen, hit ESC to bring up the boot menu. Select CDROM. Then it booted from the DVD.
Going into the Setup BIOS screen as I have done in the past did not work. Also, the Boot Delay was set to 0 for this VM originally, so I never got to press ESC to get to the other boot menu.
Hope this helps someone.
-
i try this on VBOX, i've the same of haydibe ...
but DSM 6 is started but not enabled btrfs
In the current state, it can't run in VirtualBox since none of VB's NICs are supported.
-
I had the iso on at all times, but after the install attempt I don't get the same screen asking for run or install. The screen is just black, nothing happens.
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...
-
wait for reboot. Waited 15 minutes, nothing happens
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).
-
The odd thing is:
I did not boot form the ISO. When i boot with "RUN", the installer starts all over again on every reboot.
If i boot with Install: 1st boot: the installer runs fine, 2nd boot: configuration (and access dsm) , 3rd boot: login to dsm
When i want to create a volume, i am able to see the drives, but the creation throws an error on the last step.
Maybee it's worth mentioning that i am trying to get it up and running on esxi 6.0u2 (which does not support hw version 12).
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.
-
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.
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.
-
So how did you cracked it?
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.
will there be a iso for the new bootloader?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.
-
1
-
1
-
Working DSM 6
in Loaders
Posted
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.