Balrog
-
Posts
143 -
Joined
-
Last visited
-
Days Won
1
Everything posted by Balrog
-
@4sag: Thank you very much! The tools are working.
-
I use a Dell H200 flashed to IT-Mode and it works very good with the loader 1.02b (under DSM 6.1.3 Update 4 as a VM under ESXi 6.5 Update 1 as passthrough ). The H200 is similar to the IBM M1015.
-
If you have installed DMS bare metal on the Gen8 you need to install a software for reading the sensors. Without the sensors values the Gen8 will run in a "save mode" with enhanced fan speed. Search the forum for "AMS". Here is a good start: http://xpenology.com/forum/index.php?/topic/4242-HP-microserver-Gen8-and-hp-ams
-
In your case I would try an installation via ESXi and fool the DSM to only have one CPU socket. On every installation I see DSM sees every cpu core from the first CPU socket. Only the information page from DSM shows only 2 cpu cores but I think this is hard coded. A proof with "cat /proc/cpuinfo" and an installation of "htop" via qnapware shows easily that every cpu core will be used. What do you want to do with such many cpu cores on a NAS?
-
As I played around I found that even the 3615xs offers the new "F1 -Format" if it detects 3 SSDs.
-
I hope I'm wrong but I saw today the same thread on the official synology forum. Even with "...updated with Juns loader". It is more than silly to post an issue with Xpenology on an official synology forum. Just my 2 cents. https://forum.synology.com/enu/viewtopic.php?f=39&t=134716
-
As I wrote: You are able with this to access a direct console at every time. Like an insurance if things go bad. Even without loaded nic-drivers in the VM or disabled SSH. In the past this was the access via iLO for me as DSM was installed bare-metal on a HP Microserver Gen8.
-
A little help for everyone who struggles a little bit with enabling the serial console in ESXi. This manual works 1:1: https://www.juniper.net/documentation/en_US/vmx15.1f4/topics/task/configuration/vmx-vm-connecting-vmware.html in short: # at ESXi: open Firewall for serial Console # at VM: add Serial Port 1 - Use Network - Connect at Power - Direction: Server - Port URI: telnet://:8601 In PuTTY the connection will be made as: Type: Telnet Hostname: IP-of-your-ESXi-Host Port: The-port-you-entered-in-the-config-of-the-VM (e.g. 8601) With this you have at every time contact to the Xpenology-VM-Console even a driver wont be load with a upgrade (like in Loader 1.02a).
- 13 replies
-
- 4
-
-
-
- vm
- serial port
- (and 1 more)
-
I outsourced the info about how to connect easily a VMware ESXi VM to a serial port and how to connect it from a pc in a own thread:
-
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
Balrog replied to Polanskiman's topic in Tutorials and Guides
You can user the vmdk-file from loader 1.02a as a base for loader 1.02b. It's only text file with information: open it with a text editor and your will see what I mean. -
Thanks for the info. Here is the link to the original thread which is better to read: https://homeservershow.com/forums/topic/9602-esxi-notes/?do=findComment&comment=137174
-
Just make it so like described here: https://kb.cyberoam.com/default.asp?id=2193
-
On bare metal you have to have a real serial port built into the server where you can connect a real serial RS232-cable to a real serial port (e.g. a usb-2-serial-converter). Then you are able to use putty and can work over this connection. Or you have a HP Gen 8 server. Then your are able to enable a virtual serial port over iLO. The howto to this solution is in this forum, you must search it. @Ronny: nice to read that the information is useful and working.
-
You can add a virtual serial port to the vm in esxi and connect over this way. This might give a clue what I mean: https://www.fir3net.com/Virtualization/VMware/esxi-connecting-to-a-named-pipe-serial-conenction.html
- 48 replies
-
- 2
-
-
- 6.1.2-15132
- update
- (and 1 more)
-
If you have an extra controller like e.g. an IBM M1015 or similar in "IT Mode" you can give the whole controller to the VM (called "passthrough") and have no need for making RDMs for the single hard disks.
-
How to build and inject missing drivers in jun loader 1.02a
Balrog replied to IG-88's topic in Tutorials and Guides
Thanks for the guide! -
Thank you very much for the tutorial!
-
Thanks for sharing the how to. Might be handy some time.
-
Thanks for the feedback! Very helpful. I have also a HP Microserver Gen 8 with a Dell H200 flashed to it mode as LSI 9211 currently running DSM 5.2. I will remember your thread if I make the way to DSM 6.1 (but I think I will wait till a updated loader is available).
-
Thank you very much for your modifiying-scripts. You change your raid-settings very heavily but if it works stable for you its all fine. If I have time I will test which mode works for me best (all harddisks as single raid0 or to put the B120i-controller in plain AHCI-Mode). I read that a lot people have performance problems (slow reads and writes) under ESXi 6.5 with the onboard B120i-Controller (the harddisks/ssds for the the VM-storage are affected by this problem not the disks given to Xpenology itself).
-
@gits68: Thank you very much for your detailed upgrade-how to!! Do you run the builtin controller B120i in RAID-mode or AHCI-mode? Do you suffer from bad performance from ssds or harddisks which are connected to the B120i? These questions are the only things holding me back to go from baremetal Xpenology to ESXi.
-
@JBark: Thank you very much! I just installed an Dell H200 HBA (flashed to IT-Mode) and installed it into the Hp Microserver Gen8: With your tar.gz-archive and installing as you described even all harddisks connected to the H200 will be shown with their current status at the iLO-Webpage (for now only tested under DSM 5.2-5967 Update 1)!!! Awesome!
-
You don't need to use USB drive for bootloading into xpenology under esxi. That is just the way I wanted it to work, so to a) save space on my SSD even though it is only few hundred MBs, b) making use of the already there internal usb port, in fact I even use the MircoSD slot for running esxi, c) in relation to previous point, booting from USB drive means I could easily backup and replace bootloader in case anything went wrong. The entire concept of my setup is to isolate Xpenology as much as possible from the other VMs on the same Gen8 physical machine, so to up the reliability and increase .... Thank you very much for the informations! I have a similar setup but I want give the additional Dell H200 (flashed to IT-Mode) to the xpenology-vm. I am currently on bare metal under DSM 5.2 (with Virtualbox on top) which is rock stable. So it is the third time I read that there are issues with Esxi 6.5 and the Gen 8 Microserver. I will stay at my current setup and read on how the things will go. As DSM 6 aren't able to run Virtualbox I must change my whole setup. Hopefully there will be a future solution for Esxi 6.5 and the Gen 8 (fingers crossed).
-
I only used esxi 6.5 (custom iso made by HP) for about a week, didn't noticed any issues in this time. However, on esxi 6 the problems with the slow transfer appeared mostly when I run 2 or more vm's on the same datastore. While on esxi 6.5 I only had one xpeno vm running full time with a few other (also xpeno) for testing, a lot of reboots... so I can't be sure if the problem is there or not My advice is to use esxi 6.5 as it is for some time, and only if you have problems to downgrade the hpvsa driver to scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib witch was the latest good one for esxi 6. A lot of good info on hp gen8 and esxi you can find here : http://homeservershow.com/forums/index. ... /88-gen-8/ Thank you for the answer! So I will do some tests on my spare machine and decide afterwards if I go from bare metal to esxi.
-
I only used esxi 6.5 (custom iso made by HP) for about a week, didn't noticed any issues in this time. However, on esxi 6 the problems with the slow transfer appeared mostly when I run 2 or more vm's on the same datastore. While on esxi 6.5 I only had one xpeno vm running full time with a few other (also xpeno) for testing, a lot of reboots... so I can't be sure if the problem is there or not My advice is to use esxi 6.5 as it is for some time, and only if you have problems to downgrade the hpvsa driver to scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib witch was the latest good one for esxi 6. A lot of good info on hp gen8 and esxi you can find here : http://homeservershow.com/forums/index. ... /88-gen-8/ Thank you for the answer! So I will do some tests at my spare Gen 8 and decide afterwards if I go from bare metal to esxi.