• Announcements

    • Polanskiman

      DSM 6.2-23739 - WARNING   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs
    • Polanskiman

      Email server issues - FIXED   06/14/2018

      We have been experiencing email server issues. We are working on it. Bear with us. Thank you. ------------- Problem has been fixed. You might receive duplicate emails. Sorry for that.

johnduff

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About johnduff

  • Rank
    Newbie
  1. How noise is the HP Micro gen8 with XPEnology?

    Very quiet, both on esxi and bare metal.
  2. Idiot mistake

    did you try this ? https://wrgms.com/synologys-secret-telnet-password/
  3. Package Center error

    Hi I found the solution: wrong time and date on ESXi host. Fix: set proper time, date and also pool.ntp.org on esxi AND synology parameters. It just works
  4. DSM 5.2 is available

    Do you guys have the package center working with update 2 ?
  5. DSM 5.2-5565 Update 2

    No SSL after a security update... wow !
  6. Esxi questions

    Hi It is possible to migrate disks from a standalone xpenology or synology to a virtualized xpenology using RDM. I did it. It worked.
  7. S.M.A.R.T and hibernation

    is it possible to replace synodisk by something that reads RDM ?
  8. Hi Thank you for your advice. This is what I did: -Downloaded vmdk directly from here: http://www.xpenology.nl/boot-images/ -Uploaded vmdk to esxi's datastore -Converted the vmdk to the right format with the following command: vmkfstools -i XPEnoboot_DS3615xs_5.1-5022.2.vmdk XPEnoboot.vmdk If you don't do this vmdk import in esxi (I'm running 5.1), you get an error. -Installed the resulting vmdk in an Ubuntu VM that I have on my esxi. -Edited the syslinux.cfg (as described in post #1) -Shut down ubuntu and removed the disk from ubuntu VM -Removed Nanoboot from XPEnology VM -Added XPEnoboot disk instead -Booted the VM and selected "upgrade" -Browsed to the servers's usual IP: the interface prompted for a migration. I chose a migration with all the parameters. -Upon reboot, I had a syslog error. Ignored it. -Upgraded DSM to Upgrade 2. -Upon reboot, my disks vanished. -Rebooted again, my system is working ok. Thanks for all your advices, and to the guys behind XPEnoboot. The ubuntu trick can be useful for those who don't want to use winimage. Enjoy !
  9. Hi Panja Thanks for this very clear guide. What would you recommend in case of upgrade from gnoBoot for instance ? Let's say I want to upgrade DSM to 5.1 and I want to be sure none of my data will be erased, nor my settings.
  10. HP Microserver Gen8 + Esxi + XPEnology

    Hi Rémy In the link provided, at step 3, you have a link that ends up in vmware's website. You have to register, and also to apply for a free esxi license. I still haven't tried USB on my VM, but I know that you first have to add an USB controller to a VM before adding the device. I found somewhere (can't remember where, though) a package that adds open-vm-tools to your virtual xpenology. Worth adding.
  11. HP Microserver Gen8 + Esxi + XPEnology

    Hi Just set up mine, using this: viewtopic.php?f=2&t=2147 except that I boot from SD. I inserted a blank micro-SD (2Gb) and also a 2.5" HDD from a notebook. You can put a SSD, but you don't really need speed there. You can mount it in the optical drive bay, or if you already have an optical drive, double-side-tape it above the RAM modules. Very easy: use ILO console. Mount ESXI ISO from there. I used 5.1 as I read there are some limits to VM management in 5.5, and I didn't feel that the new features from 5.5 would be useful to me (mostly large capacities). If anybody sees something interesting, please explain. Then, during install, press yes,yes,ok,keep going,yes,ooh yes, and when prompted where to install vwmare, choose ilo-sdcard or something like that. After install, reboot. Start the vsphere client. You have to create the datastore on your HDD, and then tell ESXI to use it to store temp files (logs, etc.). And you're done ! Edit: I tried both with Raid controller enabled and disabled, and then raw-device-mappings. With raid controller disabled, I can actually see disks type, serial and especially SMART status, whereas in B120i controller mode I couldn't (shows instead generic information sent from the controller).