Jump to content
XPEnology Community

unmesh

Member
  • Posts

    167
  • Joined

  • Last visited

Posts posted by unmesh

  1. Well, you have 2 choices:

    1. Take the "hypervisor HDD, mount it in another PC and start the ESX installation there. When done, just move the HDD back to the Q1900 PC.

    2. Attach a standalone GPU to the Q1900 MB and perform the installation directly.

     

     

    Sent from my iPhone using Tapatalk

    For option 1, would one need to inject drivers into the installation while still in the temporary PC? If not, I could move one of my ESXi boot hard drives to the Asrock temporarily and see if it boots.

  2. Today I installed Hyper-V using Windows 10 and then installed a lightweight Linux distro called Elementary OS as a VM. It is possible that I did something incorrectly but it was way slower than on my N54L with ESXI6 whose CPU is supposedly slower than the J1900.

     

    Waiting for my PCI-E extender cable to arrive to install ESXI6 with a VGA card and see what that performance is like.

  3. Trying building my own or get the HP N54L Micro Server, what are the Pros and Cons?

     

    Which one is more stable and faster?

    N54L is fast enough and it will be hard for you to assemble a compact NAS case like it on your own with parts.

     

    It is not hard but not sure if it makes sense to build one economically.

    Fair enough since "hard" could be interpreted as meaning "difficulty of effort".

  4. Then boot up the EX495, in my case I have to remove SATA0 shortly so it can boot from USB for a few seconds then place SATA0 drive back on so it can continue to boot (Headless server, no VGA).

    How are you timing the removal and subsequent replacement of the hard drive for reliable full boot of Xpenology? This is the main thing that has been holding me back from converting my EX495.

  5. They are typically tied to the same release nowadays. Meaning, use 5592.x of the boot image for 5592 builds of DSM. But the boot image is really just to give the appropriate HAL for the DSM to run (trick DMS into thinking it is on Syno hardware).

    yes i know that.

     

    so if i shut down my n54l and unplug the usb stick,

    plug it to my pc

    and copy/paste all the contents to another usb stick

    would i have a back up of the original bootloader usb stick?

     

    thanks

    Using imaging software to make a backup and then restoring to another USB stick will work fine.

     

    I use Win32DiskImager on Windows.

  6. May I know how can I use the internal disk to perform boot-up with DSM?

     

    I'd like to know on how we can use that please. Or just a confirmation that it;'s possible.

    Someone had done a hack with an older version of DSM to allow booting from a hard drive but you were then limited to one drive only. As things are currently, you have to use a USB stick with the bootloader on it.

  7. I did a manual install of open-vm-tools_bromolow-5.1_9.10.0-2476743-1 while I had open-vm-tools_bromolow-5.1_9.4.6-1770165-3 installed and now Package Center does not show open-vm-tools installed. When I try to reinstall it, Package Center says it is already installed.

     

    Any ideas about getting this working again will be greatly appreciated.

     

    Thanks.

  8. Various people have observed that it is the J1900's graphics controller that is not supported by VMware. This board's ASPEED AST2300 BMC must be what makes the difference in comparison to the other J1900 boards.

     

    I have an ASRock Q1900DC-ITX and can confirm that neither ESXi 5.5 nor 6.0 will boot on it and am waiting for the first confirmation that it boots on the J1900D2Y

  9. Hello,

     

    i have DSM install on esxi N54L. But i realize i don't need to use virtualization and i should prefer use bare-metal install (smart disk information can be useful).

    How can i do to migrate without losing any configuration ?

     

    Thanks for answer :wink:

    You could do it if you were using your hard drives in RDM aka passthrough mode, else you will have the problem sbv3000 mentioned.

  10. I was successful doing this using Raw Disk Mapping of my 2-HDD pool to DSM as the guest OS. I use nanoboot but DSM should not know the difference except potentially seeing a different MAC address for the N54L if you had not modified gnoboot to pass along the real MAC address

  11. Hello, my name is yosus and I'm new on this forum, I want to thank everyone for the support and I hope someone can help me.

     

    I'm trying to build a NAS using this motherboard and xpenology. I've create the usb drive and boot from it using nanoboot, then select "Synology DSM 5.0 (upgrade/Degrade)" and then "Synology DSM 5.0-4493" (or other version). My problem is nic seems not to be recognized since I have the message "eth0 not RUNNING".

     

    What do i have to do to make ethernet being recognized?

     

    Thanks

    Which version of nanoboot? And are you using the defaults or did you edit any of the files?

  12. I run it bare metal and works fine. Maybe an OS+virtual machine+DSM is too much for the AMD processor in the n54l?.

    I don't have the benchmarks at hand but I can barely tell the difference in performance between bare metal and ESXi 5.5.

     

    I am using raw device mapping for the hard drives though.

  13. I am using my TS140 solely to serve files over CIFS and have no packages installed. With 1GB of memory allocated in ESXi, I see 9% RAM utilization when first booted and it shows up at 75% in a couple of days. I don't know if it went up suddenly or slowly over time but am wondering if any of the ESXi users have seen something similar.

     

    Thanks.

  14. I've been running DSM5 on my HP N54L as a bare metal install and this thread inspired me to try to run it on ESXi 5.5. I added a hard drive, installed ESXi 5.5 to it with a datastore, created a nanoboot VMDK and uploaded it to the datastore, created a VM and was able to boot the VM with no hard drives for data.

     

    What I have not been able to do is to add virtual RDM drives to the VDM since the VMDK files do not show up in the dialog for Add -> Hard Disk -> Use existing virtual disk.

     

    Here are the screen dumps from creating the virtual RDM files in a SSH session.

     

    ~ # ls /dev/disks

    t10.ATA_____SAMSUNG_HD753LJ_________________________S13UJ1KPC25795______

    t10.ATA_____SAMSUNG_HD753LJ_________________________S13UJ1KPC25795______:1

    t10.ATA_____SAMSUNG_HD753LJ_________________________S13UJ1KPC25795______:2

    t10.ATA_____SAMSUNG_HD753LJ_________________________S13UJ1KPC25795______:3

     

    ~ # vmkfstools -z /vmfs/devices/disks/t10.ATA_____SAMSUNG_HD753LJ_________________________S13UJ1KPC25795______ /vmfs/volumes/datastore1/Samsung750G.vmdk

     

    Update: I tried recreating the virtual RDM VMDK files and this time it worked so I must have done something wrong the first time around!

×
×
  • Create New...