hpk

oh sorry, I wasn't precise enough ... I know how to edit grub.cfg, however, I need to know, what lines I need to modify or add so that I can boot from the fourth harddisk instead of the first, that is default ...

can someone with good Unix knowledge help me? How should I modify grub.cfg, if I want a baremetal installation on my HP ProlLiant MicroServer Gen8 to boot from the HDD in Bay 4 instead of Bay 1?

Today I had a new version for my physical Synology DS214+ Therefore, it will not be long, until it's available for our XPEnologies As soon, as I have it, I'll test and report ... What's new:

and the performance has improved significantly, now, the limiting factor seems to be the 1Gbps Network ... But I can live with that

Was a syntax issue: [root@localhost:~] vmkfstools -z /vmfs/devices/disks/vml.0200020000600508b1001ce164482da257de5d2e8a4c4f47494341 "/vmfs/volumes/Bay1 SSD DataStore/HPEsynology/bay3.vmdk" this worked ...

I get the following error: [root@localhost:/dev/disks] vmkfstools -r /vmfs/devices/disks/vml.0200020000600508b1001ce164482da257de5d2e8a4c4f47494341 bay3.vmdk -a lsilogic Option --adaptertype is deprecated and hence will be ignored Failed to create virtual disk: Unknown object error (6475) Without the adaptertype option: [root@localhost:/dev/disks] vmkfstools -r /vmfs/devices/disks/vml.0200020000600508b1001ce164482da257de5d2e8a4c4f47494341 bay3.vmdk Failed to create virtual disk: Unknown object error (6475) Any idea, what's going wrong?

Thank you, I'll read it carefully and try it out. Currently, I'm doing a backup wich takes ages, the volume is really the limiting factor. About 1GB per minute is really slow ...

What do you have to do, before you're able to pass a disk through as RDM disk? The option is not available, when I try to add a disk. My setup: - HP ProLiant MicroServer, Xeon, 16GB RAM - SSD Disk in Bay 1 for ESXI and Virtual Machines - HDD Disk in Bay 2 as DataStore for Virtual Machines, except DS3617XS - HDD Disk in Bay 3 as DataStore for DS3615xs All three disks are on the same Controller, and I'd like to have best performance for the disk in Bay 3 (exclusive for XPEnology ...) As mentioned, I don't have the option to add an RDM Disk. I guess, it needs some prerequisites to be able to pass the HDD in Bay 3 exclusively through to XPEnology. Who can help?

tried something according to an howto ... but killed my server. By changing the B120 Raid Controller to passthru in the hardware settings, you can't set this back. Neither in the GUI nor in the esx.conf ... after reboot it's always on passthru ... And I want passthru to a disk, not the whole controller Anyway, setup will take a few minutes or up to an hour ... Back from the beginning ... it's weekend

Interesting ... How do you pass through a drive to DSM on ESXi 6.5?

Do I understand you right? After a day or so, you're not able to connect to the DS3617xs via webinterface? Sounds like we have the timebomb again ... I got my HPE MicroServer with Xeon Processor yesterday and did two tests based on 1.02b and 3617xs: - Running a baremetal installation of XPEnology ... no issues at all, took me less than 10 minutes - Installing ESXi 6.5 and setup a virtual DS3617xs. Took me two hours or so, as I did some silly mistakes Unfortunately, I did not run the baremetall installation for a long time, so I can't confirm, if there is an issue in general as you see it. The VM is running since yesterday, backups running all night, filling up the disk nicely ... When I'm finished with the installation (a Linux and a Windows VM), I will take out the ESXi disks and run the baremetal one for a few days to see, if I can reproduce your error. But that will be next week ...

Can you give some technical informations about your installation? Baremetal or VM? What processor, memory? How did you update to 1.02b? It's difficult to help, if there are so few infos.

I guess, many users of XPEnology do have a physical Synology as well, so they might know, when a new update is available. But basically, you're right, people come here, when they screwed up something to get help ... With my post regarding the firewall rules I just wanted to show an option to solve the thread starters problem. Everyone should decide for himself, if it's suitable in his situation or not ...

You're right Polanskiman ... except, they read here regularly, then they know, when there's an update that can be installed without killing the running system I would not update my XPEnology system, when a new version is suggested. I'd rather read hear first, what experiences others made ...

As an option, you might add a firewall rule, that blocks all traffic to and from update.synology.com (13.32.162.124) and global.download.synology.com (13.32.176.124). However, if you do this, you'll not be able to update packages from the Package Center as well .... Let us know, if a firewall rule helped you out ... You can find more infos here

Was für einem G8? Celeron, i3, Xeon? In welchen Disziplinen? Was hast du verglichen, dass du das so behaupten kannst?

If you have a good concept where to store files, then there's not a big benefit on 10GB bandwith. I guess, I would appreciate it for doing backups form one NAS to anotherone, not in the same room... But here as well, I don't care, if a backup takes two hours from 3am to 5am or 10 minutes ... Until now, I did not find a killer criteria to justify it. But I'd love to have it anyway

jep, just ordered one for around $630 ... will install ESXi next week and ad a few VMs including a 3617xs ... See, how it performs as NAS ...

Thanks ... so I'll go for a Gen8 with Xeon processor and ILO port ...

ups, stimmt, du hast ja eine Baremetal Installation ... So oder so, es wird sicher leistungsfähigere Umgebungen geben, um Windows 10 zu virtualisieren, aber wer gerne testet soll da mal Erfahrungen sammeln. Bin dann gespannt, auf deinen Feedback ...

As it looks like, hp's ProLiant MicroServer Gen10 will be available soon for $ 399.- However, as of now, only one model is available, the one with AMD Opteron X3216 processor. Are there any plans to support this platform with a 1.02c or 1.03 release of Jun's loader?

Hier haben wir wohl wieder mal einen klaren Fall von: "Nicht alles, was technisch machbar ist, ist auch sinnvoll" Ich war kürzlich an einem Synology Workshop, wo unter anderem auch der Virtual Machine Manager ein Thema war. Der Referent hat versucht, die Erwartungshaltung nicht zu hoch zu schrauben. Er meinte, Windows 10 laufe zwar, aber man dürfe keine Performance Wunder erwarten. Auf den DS-Appliances mit Xeon Prozessoren sei das einigermassen brauchbar, auf den anderen Intel Prozessoren lediglich für Basisapplikationen wie Mail und Web zu empfehlen. Und du gehst noch einen Schritt weiter. Du willst eine DS361x auf einem Rechner mit einem relativ schwachen Prozessor virtualisieren und in dieser virtualisierten DS mit dem Virtual Machine Manager eine Windows 10 Maschine bereitstellen ... Ohne das getestet zu haben, befürchte ich, dass das bei dir keine Begeisterungsstürme auslösen wird, höchstens eine Genugtuung, es grundsätzlich zum Laufen gebracht zu haben. Der Ansatz, der weiter oben schon empfohlen wurde, nämlich einen ESXi Server zu installieren und dann das zu virtualisieren, was du brauchst, ist sicher zielführender. Nicht zuletzt wegen all den Tools, die du zum ESXi Server nutzen kannst (Snapshots, Replikation u.s.w.) Aber falls du dich trotzdem für die Virtualisierung in der Virtualisierung entscheiden solltest, würde ich mich über deinen Feedback bezüglich der Performance freuen. Viel Erfolg!

Did a fresh install on an ASRock Vision 3D (Intel i3, 4GB Ram, 500GB Harddisc), wich was not used anymore. Runs with 1.02b as DS3617xs without any issues ...

Thanks for the new 1.02b bootloader. Now, DS3617xs with DSM 6.1.2-15132 runs well on ESXi 6.0. Did not have any issues so far. However, I use it only as Backup and Streaming Server. Installed and used Packages: Hyper Backup Hyper Backup Vault Cloud Station ShareSync Logitech Media Server On the latency of the 5TB Harddisk I have some room of improvement, but I had bad latency with 1.02a and DS3615xs as well ... As there are several Windows and Unix VMs running on this ESXi, I can't use Pass-Thru mode for the Synology VM

I'm quite new here, therefore not so familiar with the details even if I read a lot in the last few days. Is it correct, that the latest bootloader for ESXi Server is 1.02a and 1.02a2 and 1.02b are for baremetal installation on USB only? Will there be a zip version for 3617 installation on ESXi as well including the img, ovf, vmx and vmdk files? I read, this version does support the Xeon processors better than the 3615 version. Any hint or link for reading is appreciated. Thanks