oktisme

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

1 Neutral

About oktisme

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. oktisme

    Working DSM 6

    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.
  2. oktisme

    Working DSM 6

    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.
  3. oktisme

    Working DSM 6

    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.
  4. oktisme

    Working DSM 6

    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.
  5. oktisme

    Working DSM 6

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

    Working DSM 6

    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.
  7. oktisme

    Working DSM 6

    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.
  8. oktisme

    Working DSM 6

    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
  9. oktisme

    Working DSM 6

    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?).
  10. oktisme

    Working DSM 6

    Sure DSM 6 (11 No SS).7z
  11. oktisme

    Working DSM 6

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

    Working DSM 6

    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.
  13. oktisme

    Working DSM 6

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

    Working DSM 6

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

    Working DSM 6

    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...