Jump to content
XPEnology Community

koalala

Member
  • Posts

    12
  • Joined

  • Last visited

Posts posted by koalala

  1. There is no output so it's perfectly normal that it stops at Booting Kernel. You have to connect through find.synology.com

    Unfortunately nothing to see Koalala, other tips or tricks? It does not appear on my router as well, no ip address assigned.

    What is your network card ? Only limited number of cards are supported.

  2. Thanks for loader. Great job!

     

    I'm hosting DSM at ESXi and want to create SSD cache.

    Is the way virtual disk to be recognized as SSD not HDD inside DSM Virtual Machine? RDM is not an option for me.

     

    Very easy, just assign your vmdk to the SATA controller instead of SCSI. I did it and it works fine.

  3. I'm also working on doing a legacy version because EFI version cannot be use on Hyper-V. EFI is only supported in hardware generation 2, but the network card from hardware generation 2 is not supported by Xpenology...

  4. Carlchan, I would advice you an Ubuntu Desktop live cd. Mount the EFI partition with the disk manager and simply edit the GRUb configuration file.

    Don't forget to put the disk as persistent before doing that, else the modifications will be lost (I put it as non persistent in the template).

  5. Hello everyone,

    did anyone had a problem installing DSM 6 (NO SS) on ESXi 6 (AMD E-350 board) and not being able to see connected drives?

    I have two 3TB drives connected on SATA Ports but in ESXi I cannot select SATA for this drives when mapping to VM.

    So now I have created 2 vmdk files for Raw Devices and connected them as SCSI drives, but Synology doesn't see them. Any suggestions what can solve this problem?

    (sorry if this is a stupid question, I am new to DSM)

     

    You cannot use RDM with the version from okstime because there is no added drivers (so no VMWare SCSI drivers). Use the build from jun, it's more reliable as it use another patching method. I compiled a version for ESXi here:

    viewtopic.php?p=72956#p72956

  6. Jun, I tried your VM image on ESXi 6.0. However it is HW version 12 so it's not usable (max v11).

     

    I converted it to V11 and for some reasons it does not work. There is exactly the same issue than the DSM6 from okstime, it installs fine but it wants to update every time you boot.

     

    We have to use HW v10 but your image cannot be converted because you selected Debian + EFI and this is not supported by VMWare Converter. Could you please provide a VM Image with HW version 10 ?

     

    Many thanks

  7. Hi,

    The are various check around DSM programs, especially in Web Interface, maybe some are still not found out.

     

    One kind is to make sure you are run on real DSM hardwares, specifically, it checks that you have pci devices the model should have. this check is a bit forgiving, i.e., if you only has 9 of the 10 devices, you may still pass the check.Some models have mcu to control powers, leds, funs, DSM also checks that it can communicate with the controller properly.

     

    Another kind check is to make sure you system does not has any clue that you pretend to be a DSM model, for example has some file named xpenoboot somewhere,or has pid, vid in kernel cmdline, these should not exists in a real DSM devices. sometimes, it also checksum each other to make sure system executables are not patched.

     

    if DSM determine that is is not run on intended hardware, it will try to umount all you volumes, shutdown the system, sometimes also corrupt some DSM system files etc. No sign of intentionally breaking user data is observed though.

     

    Clearly, your DSM software think that it is not run on a real DS712+ device, so it umount all you volumes.

    And what I did is to make sure DSM get what it wants, so it will running happlily and ignorantly.

     

    Then maybe we should take some inspiration from what was done for Hackintosh with OSX. The loaders are patching ACPI tables (DSDT & SSDT) to make the devices recognized properly. We can actually use GRUB to load modified ACPI tables. Using that approach we should be able to add virtual devices & rename existing ones. We would be able to use vanilla kernel without any modification (as long as the devices are supported).

  8. It will work on real hardware with the ISO as long as you have fully compatible hardware out-of-box. Drivers cannot be added without the kernel source. Few network cards are compatible but you can try.

  9. Hi all,

     

    For your information RDM on a SATA controller in ESXi does not work very well (no sleep at all). Only read & write instructions are transferred, no power management. So it's better to wait a new kernel with SCSI drivers included to get RDM fully working.

×
×
  • Create New...