Jump to content
XPEnology Community

codedmind

Member
  • Posts

    90
  • Joined

  • Last visited

Posts posted by codedmind

  1. 1 minute ago, flyride said:

    6.2.1 DS3615 (loader 1.03b) does not work with vmxnet3, only Intel e1000e virtual

    6.2.1 DS918 (loader 1.04b) does work with vmxnet3, but you will need a Haswell+ processor

     

    I realize it's a lot to keep track of, but the information is out there:

    https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

     

    Thanks for your feedback!!!

     

    Now i really understand. I have the 6.2.1 ds3615 right now.

     

    I see i cannot use 1.04 because i iave g1060t. What cpu do you have in your microserver gen8?

     

    Again thank you.

  2. 7 minutes ago, flyride said:

    Nothing special.

     

    Haswell or later processor is required in order to run DS918.  VM standard install, add 2nd SATA to connect vdisks or RDM devices, or alternatively passthrough a controller

     

    On my test instance, I need DiskIdxMap=0C00 to hide the boot loader and get the SATA vdisks to show up in the right place.

     

    Humm so i thinnk e can not run that.. i have the gen8 with the default cpu GT.. maybe i will upgrade but for the xen 1625 😕

  3. 2 minutes ago, flyride said:

     

    I am running an XPEnology instance on ESXi right now with 1.04b DS918 and it works with vmxnet3

    Well that is good news... do you have done something special to have it run in esxi? or only add a second sata controller?

    Can you provide an ova?

  4. @flyride with a microserver gen8 with esxi what is your sugestion to "prevent" network related issues with xpenology? Buy a new network card and passtrought it to the vm?

     

    Not that i pretend go that road... because i already have my pcie fill with a raid controller, but in esxi using e1000e the network speed is very poor when compared with vmxnet3

     

    Thanks

  5. @timonych good to know ;) i don't really use proxmox... i'm trying to switch from esxi... Some feedback,

    After the restore do manual upgrade to DSM_DS3615xs_23824 : result no network
    New restore:
    Manual upgrade to synology_bromolow_3615xs_23739-1 : result sucess
    Manual upgrade to synology_bromolow_3615xs_23739-2 : result sucess

    Manual upgrade to DSM_DS3615xs_23824 : result no network

  6. On 1/1/2019 at 5:18 PM, Charles said:

    I have a Xpenology DSM 6 running on Proxmox successfully for several months now, and I am testing emergency scenario's such as how to recover the data in case something goes very bad. 

    The system has 2 X 8TB disks that I have mirrored with mdadm in a plain debian prior to installing Proxmox. I don't have any spare disks that I can "passthrough" to Xpenology.
    At this moment I am testing different storage types, and trying to mount them on other linux VM's in case something goes wrong. 
    What works well is a SATA disk on the local storage with a QCOW2 image, I can mount that on another VM and read the data. 
    But when using a SATA disk as an image, I can see that there is an LVM created for that storage, but I cannot get to that data unfortunally.

     

    Any idea ? 

    Charles. 

    Are you able to run proxmox with sata controller? How do you add it? I add a sata disk but but in the options still appear scsi controller..

  7. Just now, jadehawk said:

    I go manual install. however this time I tried it both ways and both worked. Also I am on SATA with my 3 drives in RDM..

     

    Well... last question do you have the synobootboot (50mb) drive and 3 rdm drives or do you have another small vm disk where do you install the synology ?

     

    My vm configuration as of today is the synoboot(50mb) (sata) and then 3 passthrouh drives  (scsi)

  8. 42 minutes ago, jadehawk said:

     

    As of right now. my VM is running DSM 6.2.1-23824 Update 4.

     

    As Always you should ALWAYS verify this on your own (I made another Test VM to see if it worked) BEFORE making any changes (Updates) to your "Production" Xpenology install.

    My hardware is an HP Microserver Gen 8. If you have something different it may not work out the same.. VM or NOT.

     

    Best Practice is always to test on a disposable copy of your XPenology install, for us running VM's is simple to just add another VM and see. You are ultimately responsible for your data.

     

     

     

    ESXi VM.png

    I'm on the same boat... i have a gen8 and esxi, i have a lsi1015 instead off hp.

     

    I will clone my vm and try... do you update manually each pat or do only use the last one?

     

    Are you running scsi or sata?

     

  9. 15 hours ago, jadehawk said:

     

    Looking At your screenshot. I think you are trying to install the incorrect .PAT file.

    You need to install the one found here : https://global.download.synology.com/download/DSM/release/6.2.1/23824/DSM_DS3615xs_23824.pat

     

    I just tested that again on a new VM and it get's you up to Latest Version as of today 01/02/2019

     

    Hope this helps.

     

     

     

    So... we can run jun 1.03b in a vm until 01/02/2019 patchs? Is that correct?

  10. On 12/11/2018 at 8:12 PM, luchuma said:

    i run disk bench on windows vm

     

     

    and direct from dsm ssh

    vol1 - btrfs raid1

    sudo dd bs=1M count=256 if=/dev/zero of=/volume1/testx conv=fdatasync
    Password:
    256+0 records in
    256+0 records out
    268435456 bytes (268 MB) copied, 2.71714 s, 98.8 MB/s

     

    vol2 - btrfs raid0

    sudo dd bs=1M count=256 if=/dev/zero of=/volume2/testx conv=fdatasync
    256+0 records in
    256+0 records out
    268435456 bytes (268 MB) copied, 2.15798 s, 124 MB/s

     

     

    and cpu 

    dd if=/dev/zero bs=1M count=1024 | md5sum
    1024+0 records in
    1024+0 records out
    1073741824 bytes (1.1 GB) copied, 2.56942 s, 418 MB/s

     

     

    I have rdm, in hp all the discs are raid0, in dsm:

    volume1 is basic (esxi disk in ssd) -> 195 MB/s

    volume2 is hybridraid (rdm drive 2 in gen8) 79 MB/s

    volume3 is raid 1 (rdm drive 3 and 4 in gen8) 117MB/s

     

    cpu 233 MB/s (gt1060)

     

     

  11. 22 hours ago, blessendor said:

    There is no SATA images format in PVE therms - it's only variant of the bus. 

     

    From my example you can 

     

    Just edit "/etc/pve/qemu-server/VM_ID.conf"

     

    sata1: /absolute/path/to/your/img/file/synoboot.img

     

    After saving config - you will see this disk in your PVE GUI as SATA.

     

     

    And what are the changes needed in the args line ?

  12. 6 minutes ago, luchuma said:

    b120i driver downgrade is usefull only when you use internal raid :)

    with RDM and sata mode it will not help...

     

    for me this speeds are acceptable :) earlier when i used new driver and internal raid, performace was awfull - 50MB/s disks write/read speed. now is 110MB/s and up to 500mb/s with SSD in ODD port...

     

    maybe in future i'll buy other pcie raid controller

     

    How do you do the test? 

  13. Ok, some feedback

     

    Following @blessendor settings:

    - Started with dsm 3615xs-6.2-2379 -  Success

    - Clone VM, upgrade manually to dsm 3615xs-6.2-2379Update1 -  Success

    - Clone VM, upgrade manually to dsm 3615xs-6.2-2379Update2 -  Success

    - Clone VM, upgrade manually to dsm 3615xs-6.2-23824 -  No boot... stop before terminal login

     

    Try change some settings, but if i change scsi controller from megaraid to others i can boot into terminal login but then loose the network.

     

×
×
  • Create New...