Joly00

Members
  • Content count

    18
  • Joined

  • Last visited

  • Days Won

    1

Joly00 last won the day on July 26

Joly00 had the most liked content!

Community Reputation

1 Neutral

About Joly00

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Well, if you have done the installation in the way i described it, then i dont know how to solve this issue, but can u give us any further information? Some screenshots of the virtualbox seetings u choose and what exactly doesnt work?
  2. Joly00

    Ds916+ or Ds918+ in Virtualbox

    You could try and install it on your vm baremetall and not VMWare/ESXI. And btw, have u edited the .vmdk file? Because it points to the .img file and is specificly defined with a name, so you should check that name and change it, if it is false.
  3. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Well, you have to download the old loader version, with the .vmdk file (if you cant find it, create a .vmdk file with this in it " # Disk DescriptorFile version=1 CID=6ccf51e5 parentCID=ffffffff isNativeSnapshot="no" createType="vmfs" # Extent description RW 102400 VMFS "synoboot.img" 0 # The Disk Data Base #DDB ddb.adapterType = "lsilogic" ddb.deletable = "true" ddb.encoding = "UTF-8" ddb.longContentID = "7e24a756b77e33e24ac940cc6ccf51e5" ddb.thinProvisioned = "1" ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62" ddb.virtualHWVersion = "10" ddb.uuid.image="4b2539af-3baa-4d1d-9b66-767de4b8210d" ddb.uuid.modification="f4047fa2-67cb-456a-bbb0-066f2c69a462" ddb.uuid.parent="00000000-0000-0000-0000-000000000000" ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000" ddb.geometry.cylinders="101" ddb.geometry.heads="16" ddb.geometry.sectors="63" ddb.geometry.biosCylinders="101" ddb.geometry.biosHeads="16" ddb.geometry.biosSectors="63" "in it and the new loader. Now rename the new 1.03a2 file to synoboot.img and place both files in the same directory. after this, open virtualbox and create a new virtual machine. Select Linux version 2.6/3.x/4.x (64 bit) and and select "no harddrive". Then ok. Right click on the new virtual machine and edit it. First go to harddrives and delete everything that is in there. Click the first button on the bottom to create a new controller and pick sata (that worked for me). The click on the second button of you new controller and add a harddrive, but pick "existing one" and now select your .vmdk file. After this, click again on the second button of you controlle and add a harddrive but ths time, create a new one, minimum about 15gb as far as i know. After this, change to the network settings tab and anc change from "NAT" to "network bridge" (this could be changed, but this worked for me) Open the advanced settings and make absolutly sure, that you have this "001132112233" as you mac adress. For better compatibility you should choose "Promiscous mode: for all vms and the host" and for the adaptertype "Intel PRO/1000MT Desktop (82540EM)" Everything should be fine now and you can start you virtual machine, after about 5 minutes max you should be able to find you NAS with find.synology.com or with the synology assistant. Find.synology.com sometimes was not able to find it, but synology assistant was always able to find it. I hope this helps you
  4. Joly00

    Progress of 6.2 loader

    Well you need a Movie on your NAS and Emby (a programm to organize movies and other things). Then you have to go into the settings of emby and enable hardware acceleration (intel quick sync) and start a video in another resolution. Finally check for the load on your Cpu and if it is as low as normal, then it works, if it goes above ~50% load, then it doesnt work.
  5. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Ok, forget it, it worked.
  6. Joly00

    Progress of 6.2 loader

    Could you check, if hardware encoding using intel quick sync is working with emby or plex?
  7. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Ok, i was able to make it bootable in Virtualbox, but even after 10 Minutes, i cant see it in find.synology.com neither in synology assistant.
  8. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Könntest du das vllt nochmal erklären, also wie ich die Loader datei einbinden muss in Virtualbox? Wäre sehr nett
  9. Joly00

    Ds916+ or Ds918+ in Virtualbox

    Hey, i wanted to test some things, but in an seperated enviroment like Virtualbox. I found some articles, that it is possible to boot Xpenology in Virtualbox but only the 3615 version with the 1.02a loader. So is it possible to boot the Ds916+ with the 1.02b loader or the Ds918+ with the new 1.03a2 loader, and if so, how?
  10. Hello, i have built my Xpenology NAS based on a J5005 Gemini Based Mainboard from Asrock. Everything worked fine until i checked for the Ip adresses in my Router. First it showed 3 different Ip adresses with 3 different MACs, then somehow i was able to get rid of one, but now there are still 2 different Ip adresses with 2 different MACs. I can change the MAC in grub to fit the one, that gives me the UEFI, but then the both Ip´s just swap their MACs. Can someone tell me, why this is happening and how i can fix this? i dont want to see 2 Ip adresses in my Router.
  11. Joly00

    Xpenology+Hardware Acceleration+j5005

    I know, that this wasnt an answer to me, i just wanted an answer and quoted just the last post u made. Ofc i understand, that u have other problems atm, but the last two posts i did are maybe helpful.
  12. Joly00

    Xpenology+Hardware Acceleration+j5005

    Have u read my last 2 messages?
  13. Joly00

    Xpenology+Hardware Acceleration+j5005

    @IG-88 To understand it fully, i asked him, if Hardware encoding works on his current system by using plex or emby and he wrote this: "I do not know for sure. It definitely works for Video Station (using the Synology video license). My understanding that the Linux device /dev/dri needs to be present and functional for hw encoding to work in either Plex or Emby. I don't believe that the Synology video license has anything to do with that. At one point in the past, I had a Xeon V5 (Skylake) with Quicksync and when I booted it on the 916+ image, /dev/dri was enabled. My current usage of the 916+ image on the ASRock Apollo Lake/Gemini Lake chipsets, I do not see /dev/dri and have not investigated why since I do not need video hw acceleration. It's possible that the version of the dri driver baked into the 916+ DSM may not support the Apollo Lake/Gemini Lake CPU's for some reason. This might be something that can be addressed with extra.lzma if you ask IG-88, but you'll need to find a dri distribution that clearly offers support for the chip. I didn't try this, but you might want to try the alpha 918+/DSM 6.2 install on your J5005 to see if /dev/dri is functioning on that platform. I don't really recommend it for production yet, but it might help you with planning."
  14. Joly00

    Xpenology+Hardware Acceleration+j5005

    @IG-88 I write again to the guy who also uses a Gemini Lake as a base for his Xpenology NAS and he says, that he uses the 916+ firmware but isnt quite sure, if hardware encoding works, because he dont use it in his current NAS. He said, that in earlier versions of his NAS (he used a Xeon at this moment) he was able to use hardware encoding but that needed a /dev/dri, dont know actually what this is, some folder or so. He also said this:"This might be something that can be addressed with extra.lzma if you ask IG-88, but you'll need to find a dri distribution that clearly offers support for the chip." What do you say about this?
  15. Joly00

    Xpenology+Hardware Acceleration+j5005

    If you would use Plex or Emby, something to stream Videos, the software can encode these Videos to make the needed Bandwidth smaller, and some Cpus are able to encode these with hardware, what speeds the encoding process up