• Content Count

  • Joined

  • Last visited

  • Days Won


mervincm last won the day on September 2 2020

mervincm had the most liked content!

Community Reputation

12 Good

About mervincm

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have not had any luck yet. I wonder if it is an issue with 918+? I have not been able to scare up any spare hardware to build a test xpenology yet either
  2. It doesn't think the CPU is a j3455, it is just that the info screen you are looking at is not build via a query, it is just a textual representation of the CPU that synology knows they installed in there. it is costemetic. I am surprised you have issue with your LSI SAS card. Mine works without issue.
  3. I can confirm on my 918+ xpenology system with 2 port 10 gig E intel card I see both NICs (my motherboard NIC is disabled)
  4. jmb585 worked without issue in ESXi 6.7u3? and 7.0u1 in my limited testing
  5. Thank you for testing! I used a 918+ image, same for you? I will build a test NAS on the weekend.
  6. I am trying to use remote/shared storage to facilitate vmotion between two esxi hosts. thus I am trying to mount an NFS share hosted on my XPE box as a datastore on both of my hosts. I believe I worded that correctly, but I admit that I don't understand your comment as I don't understand how else esxi can access an NFS share. Xpenology side Control Panel - file services, NFS and NFS4.1 checked to enable. NFS advanced settings at default. Control Panel - shared folder, created a share "NFS" NFS Permissions, added 2 entries, one for each host, by single IP, Read/Write, squa
  7. Is anyone using xpenology to supply NFS for esxi 7? I was not able to make it work. It does work as expected on my real Synology 1815+ running DSM beta 7.0, but no matter what I tried I could not get the esxi host to add a datastore on the XPEnology NAS. I can use nfs v3 and v4 to my real synology. if you are able to make it work I would appreciate some feedback.
  8. I ran this exact system on xpenology for years, rock solid. Internal NIC was fine in my experience.
  9. Thanks IG-88 I used teh supplied i915 to get plex transcoding working on my 6.23 U3 system. The only thing not working is the HDR transcoding, but that has requirements not yet available in Synology. OPenCL and Beignet.
  10. I didn't realize it was well known that update 3 was a new kernal and replaced all these drivers. I understant that this is always a possibility, and was lookingto point out that it did happen. I really do appreciate your assistance and will provide feedback on if the modified U3 version of i915.ko works. PS I am sure you notices but in case you didn't, the U3 build notes speak to fixing an issue with SAS and shutdown. Not necisarily exactly the issue that you were working on earlier (SAS and drive sleep) but I wonder if the changes in U3 help there? the newer JM585 cards largely
  11. This is the i915.ko (from /usr/lib/modules) , dated much later than the update 2 files, from my 918+ system post upgrade to Version: 6.2.3-25426 Update 3 I am not sure if I can simply replace it in /usr/lib/modules with your modified file from update2? i915.ko
  12. I believe that Version: 6.2.3-25426 Update 3 broke my hardware transcoding on my i9-9900k. I was using IG-88 modified i915.ko file. Perhaps update 3 included a newer i915.ko?
  13. I have run many Xpenology based NAS with plex hw transcoding, i3-8100 i3-8350K and i5-8600K were absolutely straight forward, no mess around with drivers etc. i9-9900K, i5-9600K were a bit more of a challenge, had to load a driver pack and a modified intel v driver as well.
  14. yes you can bond multiple nics in DSM
  15. if you want to see it graphically, install docker and netdata/netdata container. Here are my 8 cores.