koroziv

Members
  • Content Count

    147
  • Joined

  • Last visited

  • Days Won

    3

koroziv last won the day on June 3 2019

koroziv had the most liked content!

Community Reputation

8 Neutral

About koroziv

  • Rank
    Advanced Member

Recent Profile Visitors

1,280 profile views
  1. It should take the old vmdk-s with no issues, at most you will get an disk error at first boot, solved by a simple repair from dsm. I recommend adding one vmdk at a time, starting with the least critical one; that way you minimize the risk of a potential problem. I'm still using the same vm that I posted here with no issues, updated to the latest dsm availeble.
  2. Glad you solved the issue; I had the same behavior since 5.5 and a hpvsa downgrade always solved the problem; that's why I insisted (a little) with that solution.
  3. this: up to esxi 6.0 - downgrade hpvsa driver ( use "scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib" ) esxi 6.5 - downgrade hpvsa driver (same as above) and disable the esxi ahci module
  4. koroziv

    DSM 6.1.x Loader

    Set the boot drive to dependent, start the vm and recover; after that you can get back and set it as independent.
  5. https://mega.nz/#!dxgDjCpD!CNc0upEGoN3VGbZhAdM1MYpgxVq-yv5L8j_MGvyS1JQ ovf with static address 192.168.1.19, same user and pass. Just now when I started the vm to modify the ip settings the syno app and findsynology.com didn't find any address to connect to in my lan (I had 3); i looked in the router status page and all the ip's were listed there.
  6. The mac address in my ovf is the one you posted, Jun's one; stop any other xpeno vm on your lan. Also check your router for assigned ip's, findsynology.com and their app dosen't always work. I could assign an static ip to the vm and export to ovf but not everyone uses the same network values; I mean 192.168.1.101 but others might use 10.10..... or 192.168.0..., or the 101 might be already taken. PS: you have to change the mac and serial with valid ones in the grub.cfg file, changing the mac in vm settings does not help. I don't know how to debug, just that is possible.
  7. koroziv

    DSM 6.1.x Loader

    In this topic you wil find how to change mac and sn after installation: Never tried DS916 and DS3617, and I don't have much time to play with them; I can't make any promise, my resources are also limited (4gb free on the only datastore I have ATM) I transferred my data disk to a new created vm with no issues; I'm using RDM (vmdk files pointing to fizical drives). Remove the drives from the old vm, add them to the new one and boot; it will give an error message at start but it will fix it without losing the data. I do this one drive at the time, I think it is safer; try fir
  8. koroziv

    DSM 6.1.x Loader

    Here is an ovf with the latest version dsm installed (DS3615xs) https://mega.nz/#!t8xiVJ6K!aOmfjy8w-DSFTDKn7eX_8-0PSW6E1_PsWk8JDkJin7A It is dsm 6.1.3-15152 update 1; login with user admin and password 123456 I just created a volume and a folder in it to test, didn't touch any settings in there. working fine on esxi 6.5 on a hp gen8 microserver the vm is hw version 13, you need esxi 6.5 to use this ovf; you can convert to lower hw versions for older esxi If you have another xpeno vm running check the mac address and change if necessar
  9. Here is an ovf with the latest version dsm installed (DS3615xs) https://mega.nz/#!t8xiVJ6K!aOmfjy8w-DSFTDKn7eX_8-0PSW6E1_PsWk8JDkJin7A It is dsm 6.1.3-15152 update 1; login with user admin and password 123456 I just created a volume and a folder in it to test, didn't touch any settings in there. working fine on esxi 6.5 on a hp gen8 microserver hw version 13, you need esxi 6.5 to use this ovf; you can convert to lower hw versions for older esxi I can't edit the first post to add the new file. If you have another xpeno vm running check t
  10. koroziv

    DSM 6.1.x Loader

    Might be an esx issue; read about it here, there is also an easy fix; read at least the last 3 pages : https://homeservershow.com/forums/topic/9602-esxi-notes/?page=10 this is the solution, from that topic (working for me with esxi 6.5): " downloaded the hpvsa-5.5.0-88.zip archive (as per HP advisory) and uploaded the vib to the datastore. eg /datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib via the ESXi web interface http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c05026755 8. remove the exsisting scsi-hpvsa_5.5.0.102-1O driver (vi
  11. koroziv

    DSM 6.1.x Loader

    Thanks How did you obtain that vmdk file ? I want to edit the grub.cfg and make a new one. And what linux version I chose for os when creating a new vm ? No usb 3 for "other linux 64"
  12. The last vm I posted is using Jun's alpha loader for 6.1; I'm still using it with no issues, didn't update to 6.1.1. I don't have the time to try and test other loaders
  13. Just create a new vm and add the drives from the old one to it; you will loose your settings and config but not the data. At least that was the case from 6.0 to 6.1, not sure about 6.1 to 6.1.1, no time for tests
  14. I have similar hadware, 6.1 on esxi 6.5 and drives added to dsm using RDM; the thing is mine are not AHCI, I'm using raid (from gen8 bios) and can't use the same testing method (no smart info) I also disabled the vmware driver and downgraded to the old hpvsa driver (.88) for better performance; I can't give you specific numbers to compare performance but if you know other testing methods that will work for both of us we can compare the results.
  15. Thanks, I actually forgot about the vm tools and didn't install on 6.1. Sent from my SM-G930F using Tapatalk