Jump to content
XPEnology Community

haydibe

Contributor
  • Posts

    705
  • Joined

  • Last visited

  • Days Won

    35

Posts posted by haydibe

  1. Danke dir. Am Abspielgerät (Smartphone PLEX App, Chromecast, Chrome Browser, Raspi) wird es nicht liegen, da diese/r stets mit jeglichen Filmen keinerlei Probleme haben/hatten.

    Wenns selbst beim Raspi stockt, dann könnte es an den Datenrate liegen - mal den Raspi über LAN Kabel angeschlossen?

    Bei WLAN stockt es bei mir auch je nach Zimmer hin und wieder - und das Obwohl die Geräte Verbindungen mit über 200Mbit anzeigen!

    Die kommen natürlich netto niemals bei dem Gerät an...

     

     

    Ja, die 2000 Passmark-Punkte sind mir auch schon untergekommen - da ist mein N54L-Server definitiv zu schwach. Möchte auch umsteigen in was zukunftssicheres.

     

    Tendiere aktuell zum DELL T20-Server. In ihm werkelt auch ein Intel Xeon E3-1225 v3.

     

    Die CPU hat einen Passmark-Wert von 7037. Das sollte passen :wink:

     

    Wie würde denn das Vortranskodieren unter Plex bzw. xpenology eingestellt werden können?

    Wähl mal aus dem Kontextmenü "Optimieren" aus. Du müsstest den Fortschritt dann in den Einstellungen unter "Server" -> "Optimzied Versions" sehen können.

    Sicher bin ich mir nicht - da ich die Funktion nicht benutze.

     

    Es kann sein das es nur mit PlexPass Account geht!

  2. To be honest: I still use XPE with a passthrough LSI-Controller with attach 4x6TB drives. I use a second VM with DSM6 having a 100gb vmdk drive mainly for Docker. I mount fileshares from XPE into DSM6 and use them as data volumes for my Docker-Containers.

  3. In order to add a sata controller and drives you need either vCenter or the embedded VMware Host Client (ESXi 6.0u2 or later)

  4. Sobald das Abspielgerät die Video/Audio Codecs des Films nicht direkt verarbeiten kann, wird der Film in ein Format umgepackt/transkodiert, dass das Abspielgerät verstehen kann.

     

    Entweder Du hollst Dir ein Abspielgerät mit weitreichendem Codec-Support bspw. Raspberry Pi mit Plex (http://www.raspberry-pi-geek.de/Magazin ... dia-Server) oder Transkodierst die Filme vor (=kostet jede Menge Platten-Platz).

     

    Wenn Du das beides nicht willst, dann bleibt noch Den Server zu ersetzen, bspw mit nem HP Microserver Gen8 + Xeon CPU (mit etwas Glück kommst Du hier mit 500€ aus).

     

    Sprich Dein Problem ist durch wenig bis viel Geld lösbar

    a) neuer Client: Raspberry ist relativ günstig, nach etwas friemeln die günstigste Lösung.

    b) Filme vortranskodieren: Kosten für HDs in beliebiger Höhe und Zeit für das Vortranskodieren

    c) Server ersetzen: Du brauchst je 1080p Transkodierung ca 2000 Passmark Punkte. Die CPU sollte entsprechend ausgewählt werden! https://support.plex.tv/hc/en-us/articl ... my-Server-

     

    Auf meinem HP Microserver Gen8 mit Xeon E3-1260L CPU laufen bis zu 3 Transkodierungen parallel - DirectPlay kostet kaum Ressourcen.

  5. You are using the ovf package with the run option, aren't you?

     

    It's been a while now, since i used RDM disks, but did you "attach" them to a logical sata controller?

    Not sure if it works, if your drives are assigned to a scsi or ide controller.

  6. is it safe to update to latest DSM 6 version (6.0.1 7393 update2)?

    yes, it is.

     

    is it possible to use the 16GB disk also for packages installation? the system say there is no volume and if I add that disk to a new raid (basic) and volume it will format it, will I lose operating system in this way?

    yes, you need to create a volume on the 16gb drive if you want to use it for package installation.

    No, you won't lose the DSM installation on the disk. The operating system is in a different partition than the data volume (will be).

  7. Without version number:

    dsm> docker pull djey/pi-control-linux-x64

    Pulling repository djey/pi-control-linux-x64

    FATA[0003] Repository not found

     

    -> no latest tag!

     

    with version number:

    dsm1> docker pull djey/pi-control-linux-x64:0.1

    0.1: Pulling from djey/pi-control-linux-x64

    9b7301678506: Pull complete

    06984fada629: Pull complete

    cbd9326b4af3: Pull complete

    b4c9f3479366: Pull complete

    8e9b6908e7de: Pull complete

    b3137ee5cdae: Pull complete

    c66d3cde113e: Pull complete

    fb77b7df8877: Pull complete

    c4d65ff623c9: Pull complete

    b064f42ff405: Pull complete

    36c2eee769b2: Pull complete

    26bf9b3819fd: Pull complete

    Digest: sha256:7bb9da819495b9a7f04c878adce83ea1bf0f36f45c4575a47226f70088f5f834

    Status: Downloaded newer image for djey/pi-control-linux-x64:0.1

  8. Ich hab mir mal die 15 Minuten Zeit genommen und das mal für die 88f6281-Architektur gebaut.

     

    Das Paket sollte für folgende Syno-Boxen funktionieren:

    88f6281 (armv5)

     

    • x12 Series
    • DS112j - synology_88f6281_112j
    • DS212j - synology_88f6281_212j

    • x11 Series
    • DS211j - synology_88f6281_211j
    • DS411j - synology_88f6281_411j

    • x10 Series
    • DS110j - synology_88f6281_110j
    • DS210j - synology_88f6281_210j
    • DS410j - synology_88f6281_410j

    • x09 Series
    • DS109 - synology_88f6281_109
    • DS209 - synology_88f6281_209
    • DS409 - synology_88f6281_409
    • DS409Slim - synology_88f6281_409slim
    • RS409 - synology_88f6281_rs409

     

    https://mega.nz/#!fggz3IKR!ssBC84ldmqST ... ePOYE9spC8

    Bei Problemen bitte zuerst vollständig den Thread lesen :wink:

  9. My Xpenology server is bare metal, so no vSphere involved, hence the question about IB. I guess I would need to compile and load them against the kernel?

    yep

     

    For VMWare, they still support IB and with the correct switch with a subnet manager then its all just plug and play... My intention was to have my servers in the rack using IB for fast low latency access, supported by 1GbE connections, all fed through IB from the storage system.

     

    IB is still quite current, for homelabs as they're dirt cheap now compared to 10GbE copper.

    true that!

     

    Carry on and be the pioneer! :smile:

  10. Hello everyone !

     

    Currently running XPEnoboot 5.2-5967 on ESXi 6.

    Drives are connected to LSI 2008 directly presented to VM using PCI passthrough.

     

    Already tested DSM6 on ESXi and it works, but without PCI passthrough and LSI (using virtual disk only)

    Any experience with LSI and passthrough on DSM 6 ?

     

    BTW, it seems that current use of DSM6 on ESXi is still not very widely tested yet. Any though on that ? Thus not really for 'production' for now ?

     

    Thanks in advance !

    KR,

    Titi

     

    The required driver for your LSI2008 chip based controller is included in DSM6 (at least in the boot/pat combinaton that oktisme created).

    I assume that it would work.

     

    Ready for production? Depends on your expectations

    I do trust my application data (mostly from docker-containers) to dsm6 using a vmdk disk.

    I don't trust my harddisks to dsm6.. they are still assigned to a a XPE vm with direct io using a LSI2008 chip based controller.

  11. at least this time there was a new information: update 2 via WebUI works successfully :smile:

    Appart from that: same observations and follow ups to it can be found in the thread :wink:

  12. @substorm: you don't happen to have an lsi controller that is compatible with the included mpt2sas.ko driver?

    Would be interessting to see if it solves the boot problem.

     

    What you decribe as "freeze" is due the missing console output, because it's send to the serial port instead to the screen.

    success criteria: synofind is able to find the booted instance.

     

    If you want it simple, clean and easy: use the ovf/ova files from page 7 on ESXi6.

  13. Ich habe DSM6 in einer VM seit nem Monat oder so laufen... läuft ohne mucken seit Tag 1!

    Nur DockerDSM funktioniert nicht...

     

    Wobei ich zwei VMs auf demselben ESXi-Host verwende:

    1x XPE mit DSM5.2 mit weitergeleitetem LSI-Controller

    1x DSM6 für Docker & Co, hat nur 100GB SSD für Daten und verwendet für alles andere die XPE-Fileshares

  14. Bare-metal works great

     

    I got around the 'mount at reboot' by putting the mount command in /etc/crontab to run every minute.

     

     

    ** WARNING: Do not enable DockerDSM unless you have multiple NICs or you'll lost network connectivity to you box **

     

    I have a single NIC assigned to my VM running DSM6 in run mode: no such problem!

    BTRFS/Docker work fine. DockerDSM does not: on normal start permissions get removed inside the Docker-Container which cause DockerDSM to get stuck in the init phase. When started using details/start things seem fine (no permission problem), but DockerDSM is not reachable from the network.

     

    Disappearing Nics must be related to running DSM6 in install mode.

  15. Warum nicht einfach das modifizierte DSM6/Bootimage aus dem Forum hier ausprobieren? Der enthaltene be2net.ko Treiber ist für HP-Netzwerkkarten und könnte evtl die im Gen8 eingebaute HP 332i Netzwerkkarte unterstützen. Im Sata-Modus müssten sowohl der Controller, als auch die Platten erkannt werden...

     

    Es könnte gut sein, dass es funktioniert - oder eben auch nicht...

     

    Hinweis: standard XPE mit der normalen DSM6 pat-Datei wird nicht funktionieren!

    der be2net.ko Treiber ist wohl nur für einige HP 10Gbit Netzwerkkarten

     

    Damit würde ich es sein lassen DSM6 direkt auf der Microserver zu installieren.

    Was funktioniert ist ESXi6 auf dem Gen8 installieren und darin deine VM mit DSM6... Ist aber Geschmackssache!

  16. [spoiler=ls /lib/modules]8021q.ko carl9170.ko freq_table.ko l2tp_core.ko pci-stub.ko snd-mixer-oss.ko veth.ko

    8188eu.ko cbc.ko ftdi_sio.ko l2tp_ppp.ko ppp_async.ko snd-page-alloc.ko vfat.ko

    8192cu.ko cdc-acm.ko fuse.ko lfdd_drv.ko ppp_deflate.ko snd-pcm.ko vhost.ko

    8812au.ko cdc_ether.ko gf128mul.ko libcrc32c.ko ppp_generic.ko snd-pcm-oss.ko vhost_net.ko

    8821au.ko cfg80211.ko glue_helper.ko libiscsi.ko ppp_mppe.ko snd-rawmidi.ko vhost_scsi.ko

    ablk_helper.ko cifs.ko gre.ko libiscsi_tcp.ko pppoe.ko snd-seq-device.ko xfrm4_mode_beet.ko

    acpi-cpufreq.ko cls_fw.ko hfsplus.ko llc.ko pppox.ko snd-timer.ko xfrm4_mode_transport.ko

    adt7475.ko cls_u32.ko hid-generic.ko loop.ko ppp_synctty.ko snd-usb-audio.ko xfrm4_mode_tunnel.ko

    aesni-intel.ko compat.ko hid.ko lrw.ko pptp.ko snd-usb-hiface.ko xfrm4_tunnel.ko

    aes-x86_64.ko compat_xtables.ko hidp.ko mac80211.ko processor.ko snd-usbmidi-lib.ko xfrm6_mode_beet.ko

    af_key.ko cpufreq_conservative.ko hmac.ko macvlan.ko psnap.ko soundcore.ko xfrm6_mode_transport.ko

    ah4.ko cpufreq_ondemand.ko i2c-algo-bit.ko md4.ko quota_tree.ko stp.ko xfrm6_mode_tunnel.ko

    ah6.ko cpufreq_performance.ko i2c-i801.ko md5.ko quota_v2.ko synoacl_vfs.ko xfrm6_tunnel.ko

    amifldrv_mod.o cpufreq_powersave.ko i40e.ko mdio.ko r8712u.ko synobios.ko xfrm_algo.ko

    ansi_cprng.ko cpufreq_stats.ko igb.ko mlx4_core.ko rfcomm.ko syno_extent_pool.ko xfrm_ipcomp.ko

    appletalk.ko crc32c-intel.ko ioatdma.ko mlx4_en.ko rodsp_ep.ko syno_flashcache_control.ko xfrm_user.ko

    arc4.ko crc-ccitt.ko ip6table_filter.ko mlx_compat.ko rpcsec_gss_krb5.ko target_core_ep.ko xhci-hcd.ko

    ath3k.ko crc-itu-t.ko ip6table_mangle.ko mperf.ko rt2800lib.ko target_core_file.ko x_tables.ko

    ath9k_common.ko cryptd.ko ip6_tables.ko mpt2sas.ko rt2800usb.ko target_core_iblock.ko xt_addrtype.ko

    ath9k_htc.ko cts.ko ipcomp6.ko nf_conntrack_ipv4.ko rt2x00lib.ko target_core_mod.ko xt_conntrack.ko

    ath9k_hw.ko dca.ko ipcomp.ko nf_conntrack_ipv6.ko rt2x00usb.ko tcm_loop.ko xt_geoip.ko

    ath9k.ko deflate.ko ip_set_hash_ip.ko nf_conntrack.ko rtl8187.ko thermal_sys.ko xt_iprange.ko

    ath.ko des_generic.ko ip_set.ko nf_conntrack_pptp.ko rtl8192c-common.ko tn40xx.ko xt_limit.ko

    aufs.ko dm-snapshot.ko iptable_filter.ko nf_conntrack_proto_gre.ko rtl8192cu.ko tun.ko xt_LOG.ko

    authencesn.ko drbd.ko iptable_mangle.ko nf_defrag_ipv4.ko rtl_usb.ko tunnel4.ko xt_mac.ko

    authenc.ko e1000e.ko iptable_nat.ko nf_defrag_ipv6.ko rtlwifi.ko tunnel6.ko xt_mark.ko

    backports_dvb ecb.ko ip_tables.ko nf_nat_ipv4.ko sch_htb.ko udf.ko xt_multiport.ko

    bcm203x.ko ecryptfs.ko ipt_MASQUERADE.ko nf_nat.ko sch_netem.ko uhci-hcd.ko xt_nat.ko

    be2net.ko eeprom_93cx6.ko ip_tunnel.ko nf_nat_pptp.ko sch_sfq.ko usb-common.ko xt_NFQUEUE.ko

    bfusb.ko ehci-hcd.ko ipv6.ko nf_nat_proto_gre.ko sg.ko usbcore.ko xt_recent.ko

    bluetooth.ko ehci-pci.ko iscsi_target_mod.ko nfnetlink.ko sha1_generic.ko usbhid.ko xt_REDIRECT.ko

    bnx2x.ko esp4.ko iscsi_tcp.ko nfnetlink_queue.ko sha256_generic.ko usbip-core.ko xt_set.ko

    bonding.ko esp6.ko iscsi_trgt.ko nfsd.ko sha512_generic.ko usbip-host.ko xt_state.ko

    bpa10x.ko etxhci-hcd.ko isfl_drv_x64.ko n_hdlc.ko sierra.ko usblp.ko xt_TCPMSS.ko

    bridge.ko exportfs.ko isofs.ko openvswitch.ko sit.ko usbnet.ko xt_tcpudp.ko

    bsd_comp.ko fat.ko ixgbe.ko option.ko slhc.ko usbserial.ko zd1211rw.ko

    btrfs.ko flashcache.ko kvm-intel.ko output.ko snd-hwdep.ko usb-storage.ko zlib_deflate.ko

    btusb.ko flashcache_syno.ko kvm.ko p8022.ko snd.ko usb_wwan.ko zram.ko

     

     

    nic:

    be2net.ko (hp),

    e1000e.ko: Intel® PRO/1000 Network Driver - 3.1.0.2-NAPI

    i40e.ko: intel® Ethernet Connection XL710 Network Driver - version 1.3.47

    igb.ko: Intel® Gigabit Ethernet Network Driver - version 5.2.17

    ixgbe.ko: Intel® 10 Gigabit PCI Express Network Driver - version 4.3.13

    tn40xx.ko: ITehuti Network Driver, 0.3.6.11.2

    bnx2x.ko: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.00

     

    wlan: rtl8187.ko, rtl8192c-common.ko, rtl8192cu.ko, rt2800lib.ko, r8712u.ko, zd1211rw,ath3k.ko, ath9k.ko, carl9170.ko

    storage: mpt2sas.ko (LSI) version 20.00.00.00

     

    Those are the kernel modules i could identify (more or less)

  17. Accoring dmesg, dsm6 uses version 3.1.0.2 of e1000e.ko:

    [ 21.114377] e1000e: Intel® PRO/1000 Network Driver - 3.1.0.2-NAPI

    [ 21.115449] e1000e: Copyright© 1999 - 2014 Intel Corporation.

    [ 21.116475] e1000e 0000:03:00.0: Disabling ASPM L0s L1

    [ 21.118093] e1000e 0000:03:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode

    [ 21.119842] e1000e 0000:03:00.0: irq 73 for MSI/MSI-X

    [ 21.223181] e1000e 0000:03:00.0 eth0: registered PHC clock

    [ 21.224112] e1000e 0000:03:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:0c:29:b4:4a:d1

    [ 21.225487] e1000e 0000:03:00.0 eth0: Intel® PRO/1000 Network Connection

     

    https://downloadcenter.intel.com/downlo ... der-Linux-

  18. Unfortunately I don't see any VMDirectPath I/O pass-through devices on my HP Microserver so its RDM for me

     

    You need CPU support for DirectPath I/O - a Xeon or an i5+ I think.

     

    Xeon and i3 (not i5).

     

    Intel yielded to HP/DELL/Lenovo and enable direct I/O with an i3 CPU so the manufacturers can sell cheap servers for small businesses.

     

    That's only true for:

    - 4th gen i3 >= i3-4010U

    - 5th gen I3

    - 6th gen i3

     

    And almost all i5's do -> https://en.wikipedia.org/wiki/List_of_I ... processors

    The statement was fit for a HP microserver Gen8, which has no support for >= 3rd gen CPUs.

  19. so you are saying that your virtual box installation works flawless and every feature in DSM6 works like it should?

     

    Did you ever try to open a shell and take a look at the output of dmesg? No? You should do so, it looks everything else then trustworthy.

    Well the intendet use case has no error in dmesg at all.

     

    But hey, trust your personal data to an inconsistant os.. It's up to you!

  20. Make iso usb flash bootable and DSM 6 fine started on GA-H61M-S2PV motherboard...

    but i cant say that it,s working stable right now)

     

    what difference with boot option RUn and Install - because it dont working on run after install, but work on "install" boot option

     

    installing by internet explorer and finding synology by synology assistant. find.synology dont see new installation...

     

    Installation in virtualbox is working too...

     

    brtfs - dont working... only ext4

    Oktisme specificly created this for vmWare Workstation/Player 12 (hw version 12).

    We managed to convert it to an ESXi 5.5 compatible format (hw version 10) , which actualls works fine in ESXi6.0 (must stay at hw version 10).

    if synofind is not finding dsm6 or the installer is asking for the pat file: something went wrong! synofind should start at setting up the admin account.

     

     

    It does not support VirtualBox, Hyper-V or baremetal system. No network card will be found.

    The install mode does run a slightly modified XPE, which in fact does not work with BRTFS - it's not ment to be used like that!

×
×
  • Create New...