Jump to content
XPEnology Community

kim82

Member
  • Posts

    18
  • Joined

  • Last visited

Posts posted by kim82

  1. 18 hours ago, imran said:

    Hi Kim,

     

    Thank you for making suggestions. I just added the existing hard drive for the vmdk file. I didn't make any changes in terms of SAS controller with passthrough as you have suggested. How do I do that if it's required? Sorry but I am unable to find these settings. I tried below as attached but that does not seem to have made any difference.

     

    Hope you are able to advise. Thanks.

    Capture.PNG

    Hey!

     

    here is a guide you can follow for pass through https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010789

     

    do you actually have your physical disk connected to a sas controller ? If not you don’t need passthrough for dsm. If you are using virtual discs then just add new hard disk before you can install dsm.

  2. On ‎2017‎-‎09‎-‎23 at 0:05 PM, imran said:

    I am using "synoboot.img" as the boot loader and "synoboot.vmdk" as the only SCSI hard disk. No other disks.

    Hello imran!

     

    how is it going?

    so if I understand it correctly, you have created new harddrive(in esxi for the vm?) ----for install of dsm? and created existing harddrive for the vmdk file right?

    do you have a SAS controller with passthrough in esxi or just adding software discs images in esxi for dsm install?

     

    regards K

  3. 7 hours ago, imran said:

    Hi Kim, thank you for the helpful details. It's all clear except the bits where you mention, "I made the VM in esxi 6.0". Are you saying you created a new VM? If so, then how did it update your existing VM with Xpenology DSM 5.2? Sorry if it's something quite obvious and I cannot get my head around it. Thanks.

    hey again!

     

    yes I started all over in ESXI, created a whole new VM. I created Xpenology DSM 6.1.3 where I then uploaded the vmdk file and the boot file. When I turned on the new Vm and I got ip number from the xpenology nas. I then started the synology Assistant and in that I could see the Ip and it had found "dsm 5.2" filesystem on it. Status "migration able" or something like that. I guess the DSM filesystem is stored in the raid somehow?

     

    I typed the ip adress of the nas in IE and I came to the promt where to choose install/upgrade/Migrate my xpenology. I choose to keep my data etc and then chose the PAT file. Hit install and it did and then rebooted.

     

     

    when I checked everything was OK, I deleted my old dsm 5.2 VM in esxi.

  4. On 9/18/2017 at 6:43 AM, imran said:

    Hi Kim, have you posted somewhere your experience of updating your ESXi Xpenology VM DSM from 5.2 to the latest? Please share if you don't mind. Thanks.

    Hey!

     

    I can write exatly what I did:

    My hardware:

    Motherboard supermicro X10SL7-F with xenon E3-1265L, Passthrough SAS controller and I have 8discs. 

    ESXI 6.0

     

    I had dsm 5.2 and wanted the lastest 6.1.3 update 4 edition.

     

    I chose to read up on Tutorial: Install/Migrate DSM 5.2 to 6.1.x(juns loader)

     

    I downloaded the latest loader 1.02b ds3617. Then I opend the imagefile with OSFmount. edited the grub file like I wanted it to be. saved the changes and unmounted the image.

    I did not bother the vid/pid becasue im using ESXI.

     

    I made the  VM in esxi 6.0

    memory 4gb

    cpu number of virtual sockers 2 and number of core per socket 4

    hardidsk for the vmdk file(synoboot.vmdk)

    network adaoter 1

    my pci device 0 = sas card passthrough

     

    I uploaded the image(synoboot) to my datastore to folder Xpenology dsm 6.3.1

     

    I then created a notepad fil with this content:

    # Disk DescriptorFile
    version=1
    CID=5a3f7f5f
    parentCID=ffffffff
    isNativeSnapshot="no"
    createType="vmfs"
    # Extent description
    RW 102400 VMFS "synoboot.img" 0
    # The Disk Data Base
    #DDB
    ddb.adapterType = "lsilogic"
    ddb.deletable = "true"
    ddb.encoding = "UTF-8"
    ddb.longContentID = "5cfc609b86db2c06834ece425a3f7f5f"
    ddb.thinProvisioned = "1"
    ddb.toolsInstallType = "4"
    ddb.toolsVersion = "10247"
    ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62"
    ddb.virtualHWVersion = "10"

    I saved the file synoboo.txt to desktop. Then uploaded to my datastore in the same directory as before "Xpenology dsm 6.3.1. Then renamed that file to synoboot.vmdk

     

    I downloaded the PAT file DSM 6.1.3 PAT file for the ds3617xs

     

    started the VM and then opend the synology assistant program. 

    I never disconnected my raid from dsm 5.2 just left it. When I got the IP number of the nas I could choose migrate in the synology assistant. I could manually choose the PAT file.

    It ran the update rebooted and then I came to the login. 

    After it updated all the packages I ran the dsm 6.3.1 update 4 within the dsm without any problem. It then ran som raid scrubbing witch took som time (10TB data)

     

    It has now been up for some dats without any issues!

     

    any more questions feel free to ask.

     

    regards K

  5. Hello guys!

     

    I have just migrated from dms 5.2 to DSM 6.1.3-15152 update-4

     

    Works perfectly! Im using esxi 6.0. I can reboot my xepnology nas without any problems. running the ds3617xs.

     

    Motherboard supermicro X10SL7-F with xenon E3-1265L. Passthrough SAS controller and I have 8discs. 

     

    regards K

  6. 5 hours ago, Polanskiman said:

     

    It might be a good idea to share what you did so that if others who came across the same problem then they can use your experience. For the visible disk you might want to read this: https://xpenology.com/forum/topic/7613-disablehide-50mb-vmware-virtual-disk/?do=findComment&comment=73440

    thank you! Yes I will update how I did.

     

    one more qquestion. How much ram should I dedicate in esxi for the VM?(xpenology)

  7. On 2017-07-12 at 1:00 AM, tret said:

    Solved. 50MB VMware Virtual Disk is no longer showing in the list of available disks in DSM after making the following changes.

     

    - Added SATA Controller

    - Removed SCSI LSI Logic Parallel Controller

    - Changed vDisk to Independent Non-Persistent

    Hello!

     

    how do I add sata controller in esxi? I dont have that option, when im adding hardware...

  8.  

    40 minutes ago, Polanskiman said:

     

    I do not use ESXI so I am not sure what is going on. Check the forum there are several topics on the matter. All I can say is that your data should be safe since it is on separate partition so don't worry too much about that

     

    Anyway what NIC are you using in ESXI?

    Hey Polanskiman!

     

    I finally got it to work and with the latest update 4 aswell! 

     

    now my last issue; why is the 50mb "wmware disc" visible when I look at the disk slots? in dsm 5.2 I know that partition was invisible....

    can I hide that partition from dsm?

  9. Ok Guys! I BEG for help!

     

    I had my dsm 5,2 running on my esxi 6 and did work GREAT!

     

    now I wanted to try the latest and now I cant get it to work. 

     

    Please help me:

     

    I want to install dsm 6.1.3 on my esxi 6. What am a I doing wrong? When xpenology reboots, im not getting any ip number at all. But first time I boot and I choose migrate it work until reboot. then no ip number again. Im kinda stuck.....PLEASE HELP im so desperate, I have so many things I cant loose in my discs.

     

    regards Kim

  10. aha oki =) no worries

     

     

    Hey guys!

     

    sound strange because im running VPN without any problems at all. Im using the latest xpenology.

     

    Im using PPTP vpn. Using it on my iphone etc.

     

    Do you mind grepping 500, 1701, 4500?

     

    Never mind, just noticed you're using PPTP.

×
×
  • Create New...