Jump to content
XPEnology Community

Search the Community

Showing results for tags 'esxi', 'serial port' or 'vm'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. Привет всем. DS3617, Loader 1.03, установка на ESXi, при установке всё идет нормально и по плану, а вот после установки и перезагрузки XPEnology не видит scsi контроллер и подключенные диски. конфиг следующий: контроллер LSI logical parallel Диски прокинуты через vmkfstools -z ...И ещё при равных условиях DS918+ loader 1.04b грузится и работает нормально... если дело в дровах то может есть у кого exrta.lzma для 3617 с поддержкой scsi или подскажите в чем проблема.
  2. Hi Guys, Im having issues with my vitrualized XPE. I am running it on a dell R710 with a H200 HBA(IT-mode). The issue is that when I pass through the PCI-E HBA 4 all drives get recognized but Synology is reporting that 4 of them are 0 Bytes HDD. Ex. Esxi VM-settings: Version: DSM 6.2.1-23824 Update 4 Do any of you guys know what the cause of the issue can be ? In ESXI all drives are recognized. Kind regards, Mat.
  3. Hallo zusammen, hier ist eine Anleitung zum Update des Boot Loaders auf Jun's Bootloader V 1.02b.Basiert auf Synology DS3615xs und VMware ESXi v6.5. Upgrade des Jun's Bootloaders von V1.01 auf V.1.02b, damit man DSM 6.1.x (i.d.F. 6.1.5-15254 Update 1) installieren kann. 1. Vorher DSM ausschalten und die betroffene VM mit DSM bzw. Xpenology vom ESXi-Datastore auf lokale Festplatte sichern. Im Falle eines Problem ist somit für Backup vorgesorgt 2. In der gesicherten VM-Ordner befindet sich ein synoboot.img. Diese Datei entpacken und in der "grub.cfg" -Datei (synoboot\boot\grub\grub.cfg) nachschauen, welche Einstellungen aktuell hinterlegt sind. Dieser Textbereich ist relevant: set vid=0x058f set pid=0x6387 set sn=B3Lxxxxx (Eure SN-Nummer!) set mac1=011xxxxxxx (Eure MAC-Adresse!) set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' 3. Die aktuelle Jun's Bootloader (synoboot.img) in der aktuellen Version (derzeit V.1.02b) für DS3615xs hierüber herunterladen. 4. Die heruntergeladene synoboot.img mit der OSF-Mount Software mounten. Dabei beachten, dass beim Mounten die Optionen " Mount All Volumes" angehackt und "Read Only drive" nicht ausgewählt ist 5. Danach im Windows-Explorer in das gemountete Laufwerk navigieren. In der "grub.cfg" der gemounteten synoboot.img-Datei (\boot\grub\grub.cfg) die Informationen(MAC-Adresse, SN-Nummer usw.) von der alten "grub.cfg" -Datei übernehmen bzw. überschreiben und die Änderungen speichern. Danach die zuvor gemountete Datei wieder über OSF-Mount dismounten (Dismount All & Exit) 6. Die Alte "synoboot.iso" Datei auf dem VMware-ESXi Datastore löschen und durch die aktuelle synoboot.img ersetzen (hochladen) 7. Danach die VM mit DSM bzw. Xpenology auf dem ESXi wieder starten. Wichtig: Über die VMware Konsole unmittelbar nach dem Start mit der Tastatur "Jun's Bootloader for ESXi" auswählen und mit ENTER bestätigen 8. Im Web-Browser "find.synology.com" und mit ENTER bestätigen. Synology Web Assistant sucht jetzt nach der DSM und zeigt den Status als "migrierbar" an. Dort auf "Verbinden" klicken und auf die DSM verbinden. Dort steht jetzt: "Wir haben festgestellt, dass die Festplatten Ihres aktuellen DS3615xs aus einem vorhergehenden DS3615xs entnommen wurden. Bevor Sie fortfahren, müssen Sie einen neueren DSM installieren." 9. Nun kann man die .pat-Datei (DSM-Firmware) hinzufügen und manuell installieren lassen aber oder automatisch die neueste DSM Version vom Synology-Server (online) installieren lassen. Ich empfehle euch die manuelle Installation, da es keine Garantien gibt ob die aktuellste DSM-Version vom Synology-Server (online) mit eurem Xpenology Boot Looder funktiert. Ich habe meine (diese) Installation mit der DSM Version "6.1.5-15254 Update 1" erfolgreich hingekriegt. Hier könnt ihr diese Version herunterladen: DSM_DS3615xs_15254.pat 10. Nun auf "Installieren" anklicken und danach "Migration: Meine Dateien und die meisten Einstellungen behalten" auswählen. Auf "Weiter" und "Jetzt installieren" anklicken 11. DSM wird nun auf dem neuen Jun's Boot Loader installiert (dauert ca. 10 Minuten) 12. Nach der Installation im DSM anmelden und die durch den DHCP-zugewiesenen IP nach Wunsch wieder anpassen bzw. ändern Fertig.
  4. hi, all I use dsm 6.1.7 3615sx, and i have a serial port, but i can not login by the serail port, it just stop here, do not show the login prompt. I set the extra_args_3617 arg to 'earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' already, so is there another settings i have to set? thanks.
  5. Unfrotunately, I have an HP Switch, which doesnt support Etherchannel.. So it doesnt seem like i can get Port aggregation to work with Standalone ESXi.. LACP apparenty is an option with Vcenter - in a distributed switch - but I really would prefer to keep it standalone and there's not much point in a distributed switch when there's only one host.. IF I did add it to a separate Datacenter in VCenter? Would LACP still work if the VCenter server was not running? I would like proper LACP/Etherchannel, rather than just adding multiple physical NICs to the vswitch, because it's much, much, much better.. Any workarounds? Maybe command line? Many thanks! #H
  6. Hi ya all, I'm new to ESXi and XPEnology and mabe someone here can help me out with my problem. I have the problem that none of my harddisks are vissable in XPEnology Storage Manager. The SATA controller is setup as passthrough in ESXi 6.5 This is my setup: 2x Xeon L5640 @ 2.27GHz 64GB 1333MHz RAM 2x 250GB SanDisk NGFF SSD LSI SAS9201-16i 16-Port SAS/SATA controller (the card is set passthrough in ESXi) Software = ESXi 6.1 Update-1 XPEnology 6.1 DS3615xs 6.1 Jun's Mod V1.02-alpha Is there something I have to do to make XPEnology recognise all de harddisks that are connected to the SATA controller? Could it be that it is driver related, however I have read that my SATA controller 9201-16i is compatible http://xpenology.me/compatible/ Any help on this is greatly appriciated. Thanks in advance!
  7. Hi all, i've setup my XPEnology on HP Microserver Gen8 which is running ESXi 6.5 u2. I provisioned my data drive at 1.5 TB, but now i'm running out of diskspace. Can i extend this disk to 2 TB (using 2 * 3TB disk in ESXi) easily in DSM? Or is the best way to create a second disk (0.5 TB) and add this disk to XPEnonlgy (DSM)? thanks in advance for the answers! MAdD
  8. Hi , I have setup a dsm 6.1.7 on esxi 6.7. The setup is: - jun loader 1.02b vmware boot option - loader boot disk is alone on first sata port - unique data disk is on paravirtualized scsi controller - network is vmxnet3 10gb I've install all 6.1.7 updates , only packages installed are stock file station , universal search and open-vm-tools. The system will be a test environment for a spk package development so I don't need special package but need high i/o speed because my app move a lot of data. Using 10GBe as network and ssd as vmfs storage I get all performance I want. Now I'm testing the setup before starting to use it , doing that I found two problem: First , inspecting logs I see that /var/log/messages has a lot of: 2018-07-05T15:39:57+02:00 syn synostoraged: SmartDataRead(108) read value /dev/sda fail 2018-07-05T15:39:57+02:00 syn synostoraged: disk/disk_temperature_get.c:99 read value /dev/sda fail This is repeat every minute and the log file continue to grow... Now , I know that smart is not available in a vmware virtual machine but i would like to know if there's a way to disable smart check and continue error logging. Second , I've try to enable jumbo frame in the vm to maximize network performance , the virtual switch and the phisical one have both jumbo frame enable ( mtu 9000 ) and so is the client used for test. I've found a strange problem , when I use vmxnet3 ( only way to get 10gb without assign a direct nic to vm ) i can't raise mtu more than 3050 , I don't know why exactly 3050 , but if I set mtu to 3051 I get a kernel crash and the dsm hangs. This is the same raising mtu on command line or from dsm interface ( if someone would like to test the best way is use command line because a reboot solve the problem ). Using e1000e virtual adapter in place of vmxnet3 solve the problem and let me use a mtu of 9000 but obviously I get only 1GB connection. Is there some place where to see the source of the compiled modules contained in the loader or there's a way to report a bug to who maintain it ?
  9. Hi, I started my DSM VM (ESXI 6.1) with a esxi small disk2 (16G), so that I can easily export an OVF. Then I increased ESXI VMs disk2 to 2 tB. THe problem is that DSM volume doesnt increase . Is the volume not a dynamic one? Have I to install DSM only when the large disk size have been selected? Thank you Phil
  10. Hello everyone. Brand new on this forum and on playing with esxi. I set up jun's loader and get two DSM 6.1 running. Why two? I have a raid volume ( hardware, lsi) and want to secure there my pictures. Regarding music and films , I dont care much loosing it , so a simple volume would be ok. Not finding to do it with 1 DSM, I thought installing two, one with RAID volume and the other , the basic one. The problem is that I see on the net the first one installed, and the second one ( installed with OVF) doesnot show up . The MAC address for both is the same. I tried to enter a manual Mac one, but DSM replies error due to mac address being protected ( dont recall the specific message). What could I do? Would there be an alternative by using only one DSM; and the Hardware RAID? Thank you for any help or ideas. Phil
  11. Hi, I'm new to XPenology and trying it out on an Intel D2700DC mini-itx mainboard with an Atom D2700 processor and NM10 chipset. From what I read on the forum the Atom and chipset should work, however when booting the DS3615xs image it seems to get stuck on: Screen will stop updating shortly, please open http://find.synology.com to continue. I've left it for an hour or so and nothing happens, also no network activity. The same USB stick works fine on another machine. Notable is that this board does not have a serial port, and that the next thing that should show is "early console in...". Could this be related? I think that without a serial port I'm also not able to see any kernel messages, right?
  12. Hello folks, I have search on the forum and internet and I can't find an information on how to do it. There is some tutorial to do it without esxi but not with it. Currently, I don't have enough space on other disk to save everything and make a fresh install. So I would like to update without loosing any data. Does someone already did it ? For my understanding, I should select Jun's mod 1.02b vmdk file and start it as a primary drive. But will it update or overwrite the current xpenology? Thx, David
  13. Dear all, I was installing mine Xpenology with manuals and files from pigr8 https://xpenology.com/forum/topic/7667-how-to-clean-install-in-vm-using-102b/?do=findComment&comment=74129 All went fine, until 1st reboot. Afer reboot i lost RAID group and Volume. When Xpenology boot without RAID group and Volume, i can easybuild RAID group again and create Volume and it will work again untill 1st reboot (normaly if there were any data, all is lost). The RAID group and Volume creatad on VMware virtual disk won't diapear after restart: Hard disk 1: 8GB Thin provisioned SCSI controller 0, SCSI (0:0) Dependent Hard disk 3: 3TB Thick provisioned, lazly zeroed SCSI controller 0, SCSI (0:1) Independent - persistant Hard disk 4: 3TB Thick provisioned, lazly zeroed SCSI controller 0, SCSI (0:2) Independent - persistant System: HP N54L, 16GB RAM, 250GB HDD + 2x 3TB HDD in RAW mode mounted in RDM loader: 1.02b DS3615xs, DSM 6.1.4-15217 Update1 Hope nayone will have idea how to solve that, as i was searching forum and wasn't able to find solution how to solve. Thank you! Alex_G
  14. Hi, for quite a while I'm trying to find out why hard disks do not spin down after the set time with DSM 6.x and ESXi Hypervisor (6.0 or 6.5) using Jun's loader. Hard disks are connected to a passthrough SATA Controller (onboard, also tried PCIe). Exactly one and the same setup is working bare metal, also with DSM 5.2 on ESXi. I even tried using a boot iso (as with DSM 5.2) that uses the passthrough USB boot stick (like with bare metal) instead of synoboot.vmdk/synoboot.img combination. No spindown, hdparm -y does a spindown, however disks wake up at once again. I can't see any differences in the logs between running bare metal or on ESXi. Would appreciate any further ideas.
  15. Greetings everyone... I was just hoping someone might know where I can find Jun's most up-to-date loader files (1.02b is the most current at the time of writing) for VMWare Workstation. I am currently using 1.02a, and I'm concerned about doing the current DSM update while not having the freshest of loader files. Unfortunately, all I can find are iso and img files, which aren't used for Workstation. Any one have a link or something that they could share, that way I can safely update my rig? Thanks in advance! Tom
  16. Bonjour, je suis dans un environnement vmware esxi 6.5 je me pose la question suivante: si je mets une vm 3615xs, est-ce que si je lui affecte 4 vCPU les 4 seront utilisés? ou suis-je obligé de passer par la vm 3617xs étant donné que le 3617xs est un model avec un proc 4 cœurs contrairement au 3615xs qui est model avec un proc 2 cœurs. mog
  17. Turned my trusty HP54L off over the Christmas period for a few days when I wasn't using it. Came home, booted it and Esxi won't boot. While trying to boot, it gives: error loading /s.v00 fatal error: 6 (Buffer too small) This sounded to me like a RAM issue. 2GB RAM is successfully detected upon boot. When I initially installed Esxi years ago, I followed a guide to hack the Esxi install to allow 2GB RAM. I took the RAM out, gave it a technical blow, put it back into the other RAM slot. Re-booted and same error. Again, 2GB RAM is successfully detected. Any suggestions on how to troubleshoot further?
  18. Hi, - I have a DVB-Sat-Card in my System - Until yet i have used ESXI on my System and 2 VMs 1. XPEnology 2. VDR Server - With latest DSM we have a QEMU based VM inside the Synology My Idea is Stopping my ESXI Project and Using XPEnology as Baremetal with the Buildin Synology VM The project stops on the point that Synology has not enabled Passthrough. But based on the knowledge they use QEMU / libvirt it should be possible to mod the VM config files Has Anybody tried to modify the Settings of GUI generated virtual machines with modding the config files on file Base? i have checked for IOMMU working or not (yes it works): dmesg | grep -e DMAR -e IOMMU Running Service: /var/packages/Virtualization/target/usr/local/bin/libvirtd -d --listen --config /etc/libvirt/libvirtd.conf /usr/local/bin/qemu-system-x86_64 -name fabf0876-7580-............................ so checked on console : qemu-system-x86_64 --h anybody knows where the config parameters are stored and how to modify / expand it? Best Regards Synologix
  19. Hello I install xpenology 6.1.3 with bootloader 1.03b on esxi6.5 I want to attach physical disk to xpenology, so I mount disk as RDM. First I set disk like this but I fall in DSM install loop. So I made 8GB virtual disk in my ssd and attach it it like this. Than the installation process was find but when I made RAID group and volume and reboot my vm, all the RAID group and volumes are gone. I'm dealing this problem around 12hr but I don't know what the problem is...... Plz help me
  20. Ich habe hier auf zwei HP Microserver ESXi 6.5u1 laufen. Auf beiden habe ich zusätzlich ein vSwitch ohne NIC mit 9000er MTU erstellt. Auf beiden ESXi Host habe ich jeweils ein DS3617sx 1.02b mit folgender Konfig: - Nic1 ist auf vSwitch0 (mit pysikalischer NIC, MTU 1500) - Nic2 ist auf vSwitch1 (ohne pysikalischer NIC, MTU 9000) Bei einem von beiden Hosts, ist DSM nach der Umstellung von Nic2 auf MTU 9000 über kein Interface mehr erreichbar, so als wenn generell auf MTU9000 umgestellt würde. Bei dem anderen Hosts funktioniert das Ganze interessanterweise problemlos. In beiden Fällen handelt es sich um eine ehemalge DS3615sx 1.01 installation, die auf DS3617sx mit "Daten behalten" migriert wurde. Ich hab einfach das img genommen und die grub.cfg angepasst, mit StarWind V2V Image Converter zu einer ESXi Server vmdk umgewandelt, diese in den Datastore hochgeladen und dann die Bootfestplatte in der VM-Konfig ausgetauscht. Um die DS3617sx wieder zum leben zu erwecken, habe ich wieder die alte Bootplatte von DS3615sx genommen, gestartet und neu migriert. Dann VM gestopped und wieder die DS3617sx Bootplatte zu verwenden und erneut zu migrieren. Sprich: ich bin wieder auf dem Stand vor der MTU9000 Umstellung. Hat jemand eine Idee warum die Umstellung von Nic2 auf MTU9000 auch die MTU von Nic1 berührt hat?
  21. Всем привет. Столкнулся с проблемой вопроизведения фильмов в Video Station. DSM установлена на esxi 6.0. Сервер Supermicro, Adaptec Raid, диск WD 3Tb Green просто как Volume. Ресурсов нормально, Диски в DSM подцеплены как vmdk-ашки, полный проброс не могу себе позволить, живут еще виртуалки) Смотрю фильмы с iPad и ТВ-приставки на Android. Жил довольно долго на DSM 5.2, но сломались обложки, обновился на 6.0, какое-то время тоже было хорошо. Где-то месяц назад стал замечать, что пошли лаги (долго открывается, перематывать вообще не реально, некоторые видосики вообще не играет). Единственное что стояло, так это авто-обновление Пакетов. Соответственно обновился Video Station. Первое - подумал хард, проверил - ок. Дальше пробовал ставить более старые версии VS. Пробовал включать Video Conversion for Mobile Devices, проц грузит, толку нет. Обновил на 6.1, картина не изменилась. Собственно само странное поведение выражается тем, что сначала загрузка по 80Мбит, через минут 5 падает до загрузки равной битрейту (например в 20мбит), Причем странно, что как на чтение, так и на запись идет нагрузка. Если фильм остановить и начать играть заново, картина повторяется. Вот собственно скрин. Начал играть в 22:56 до 23:12, потом заново. Если смотреть это же фильм, но через DLNA или через SMB, все летает. Но так удобна эта чертова Video Station, что не хочу отказываться. Спасибо за любые советы. UPD, выяснилось, что такое происходит только с mkv.
  22. I have one ITX box and two SO-DIMM rams on J3455 but J3455 graph card not support pass-through in ESXI I'm searching ITX board and graph card with these features: 1. ITX board with 2 SO-DIMM slot, 4 SATA slot, 1 PCI-E 16x slot, support VT-D, support USB & SATA pass-through on ESXI 2. graph card support pass-through on ESXI I'm not sure whether ASROCK H110M-ITX can do so and it have 2 DIMM slot. Is that possible? Thanks.
  23. Hello, I have a nice N54L running 6.0.2 bare metal and I'm wondering if I should migrate to ESXi hypervisor. I know not much about ESXi, but would it be possible to make xpenology "see" an intel processor instead of an amd ? (would make 6.1.3 migration easier) Is there anything special to know about the migration ? Is this even possible without wiping all data ? (have 4x4 To in AHCI RAID 5) Regards
  24. Hello all, Unfortunately, I was unable to install 1.02b on esxi 6.0 Update 3 by following different guides throughout the forum. So after a few hours of testing, I wrote myself a guide for future use. I tested these situations: 1. DS3615 baremetal in basic disk -> VM 2. DS3615 baremetal in raid 1 disk -> VM 3. DS3617 baremetal in basic disk -> VM 4. DS3617 baremetal in raid 1 disk -> VM 5. VMs back to baremetal in both basic and raid 1 disk without losing any data. My personal guide is attached as a PDF. Install on ESXi 6.0U3.pdf
  25. Im running ESXi 6.5 on a HP Proliant MicroServer G8. I managed successfully to run the latest XPEnology on a new VM and I attached a couple of virtual disk on it for testing before I transfer my data. Everything looks fine until I tried to mount my USB Disk which will store my MacBook's Time Machine Backups. The same disk can be mounted on my Win Server VM but, not on the XPEnology one. I even tried to hard mount it via SSH without any luck. I installed vmware tools but nothing again. I tried both USB2 and USB3 ports. What else would you advised me to try in order to mount that disk?
×
×
  • Create New...