• Content Count

  • Joined

  • Last visited

Posts posted by neox

  1. Hello


    Sorry to have a noob question, i am under Proxmox and when i am connected to the Syno via winscp,

    and i dont have any /volumeUSB1/usbshare

    So i don't know where i can find vender file.


    If someone can help me, it would be glad.






    Sorry but I never ever use Proxmox. I think volume name just as same or maybe named with different suffix number (eg. /volumeUSB2/ or /volumeUSB3/...)


    Well, if you use proxmox, you probably don't mount the img as a usbkey but rather as an IDE drive and get your data drive as SATA drive.

    I'll try to check this tomorrow as I also run proxmox kvm for testing xpenology.

  2. Ceci est la traduction de mon post fait en anglais hier ( )





    juste pour confirmé l'installation sans souci du XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) sur un Proxmox v3 en utilisant la virtualisation KVM.


    Je me suis inspiré de la configuration pour un virtualbox que j'ai adapté ou c'etait necessaire.


    1°) creer la machine KVM avec :

    - un disque IDE-0, taille 33MB (mettre 0.032 dans la case du proxmox)

    - autant de disque SATA que vous voulez et qui seront utilisés pour les DATA


    2°) convertir le fichier synoboot...img fournit dans le repack v1.2 dans le format de votre disque IDE-0

    en utilisant la ligne de commande de votre proxmox


    sur ma machine (ou ma VM a l'ID 106) cela donne

    qemu-img convert -f raw -O qcow2 synoboot-trantor-4.2-3211-v1.2.img vm-106-disk-1.qcow2


    3°) demarrer la machine virtuelle


    4°) utiliser l'assitant synology pour detecter votre VM et installer le .pat fournit.


    5°) pendant l'installation, la VM doit rebooter, mais l'installeur a efface le disque IDE-0,

    il suffit de stopper la VM, refaire l'etape 2, relancer la VM


    6°) Voila, ca boot sur votre DSM4.2 KVM




    20131122 : Edit : les disques data doivent etre >4Go sinon l'installeur se plante lors du formatage de la partition systeme

  3. [...]

    Is it be fast enough for XPE? Will XPE work on this configuration?



    should be enough, I run it on virtual machine with one core 1.7Ghz, 512MB RAM, 4GB Hard drive for OS, multiple virtualdisk for data



    Is it possible to lower the power consumption with XPE? At the moment it need about 40w in IDLE, because there are power saving options on OMV.



    even if I did not look at specific option, it is intend to be a NAS environnement running on low power hardware

    so it must be low power even on real machine.



    Is it possible to install XPE on the 160gb system drive separately from my data on the two Samsungs hdd to prevent my data on coming updates?


    I would say yes, just dont create the SHR while you install.

    then on first login, go create a custom volume and select the Samsungs hdd for data disk

  4. ver2.1.xlsb doesn't work for me

    looks like it is write protected thus I can't modify the MAC address cell's :sad:


    btw I found this simple trick.


    6 packs are the MAC address, 7th pack is the checksum

    but checksum is pretty simple

    it looks like it is a simple sum of bits.


    in my case, I add 1 to the last pack of MAC Address, then add 1 to the checksum


    and as pictures show you can add 1 wherever you want inside the MAC.

    ex :

    first is : 00:22:32:08:D6:3C, checksum : 6e

    second is 00:24:32:08:D6:3C, checksum : 71 (6E +2)


    I have a simple Serial like B3J4N00310

    in the hexedit it appears as B3J4N003105


    I juste update my serial by 1 makes : B3J5N00311

    and change checksum to 6


    works like a charm

  5. Hi,


    just to confirm I was able to install XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) on my proxmox v3 server using KVM virtualisation.


    I just followed the virtualbox howto and adapt where need.


    1°) create a KVM machine with :

    - IDE harddrive, size 33MB (set 0.032 in the proxmox menu)

    - any SATA drive the size you want but more thant 4GB that would be used as data


    2°)according to the disk format you setup in step1, convert the synoboot...img into vm-xxx-disk-1.qcow2 using this command line in the proxmox shell

    on my machine this gives me (my VM id is 106):

    qemu-img convert -f raw -O qcow2 synoboot-trantor-4.2-3211-v1.2.img vm-106-disk-1.qcow2


    3°) boot this machine


    4°) launch the synology assistant and install the pat file provided


    5°) the first reboot failed as installer reformat the IDE0 drive,

    simple workaround : just redo the step2 to recreate the IDE0 drive


    6°) finally boot into your brand new DSM4.2 KVM.




    20131122 : Edit : if data drive are 4GB the installer fails while formating system partition, I directly upgrade to 8GB and installer works fine