gadreel

Members
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    1

gadreel last won the day on April 15

gadreel had the most liked content!

Community Reputation

4 Neutral

About gadreel

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: UNRAID - ASRock H370M itx/ac - RAM 32Gb DDR4 NON-ECC - Intel Core i5 9400F - Pass-through Integrated LAN Intel I211 - Additional comments: Reboot required by the update - This was on a TEST VM Machine. Also, I realized after the reboot DSM was mounting the USB bootloader. I reapplied the grub.cfg with some new Vendor and Product IDs and they disappeared.
  2. https://www.synology.com/en-global/releaseNote/DS3615xs
  3. I think they are open but I am sure the problem is that Synology takes a lot of time to make the update available all around the world.
  4. Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 5 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: UNRAID - ASRock H370M itx/ac - RAM 32Gb DDR4 NON-ECC - Intel Core i5 9400F - Pass-through Integrated LAN Intel I211 - Additional comments: Reboot required by the update
  5. Today I received the notification of the update. Could you close it please?
  6. @mrme01 I am using the synology assistant instead of the find.synology.com
  7. I do not think so, but give it a minute or two is a good practice. More than that your router is bad.
  8. Yes indeed. I am attaching my XML to try once more with Unraid, but as you said if this does not work it means there is something else going on when you are loading the Loader. I added comments to some parts of the XML so you can understand what I am doing, it does not have to be similar to mine. For my setup the key parts to make it work was the USB 3.0 XHCI to boot from the USB, the SATA Controllers which I also had to edit the controller number and the unit number. But definitely start with a single SATA virtual disk for now and then make the rest work and finally I changed my virtual NIC to e1000 when I first started to try this on Unraid. Also, go and download the loader for the 3615xs or 3517xs (I am not sure about the models if I wrote them correct) the loader is 1.03b and 1.02 I believe and try Unraid on them also. They also worked for me on Unraid. Also on my XML I wrote in the comments that I am passing through my NIC because is compatible. This is not mandatory for you, you can create a virtual NIC with the model e1000 like the previous xml part that I pasted to you. I have a Test 918+ which is like that and it works fine. If nothing of this work, then if you want to know what is going on I think somewhere on the forum the community is saying that if you are installing XPEnology BareMetal and your board has a serial port, and you have the cable of course you can see what is going on with the loader. It's the only way I believe. I am not 100% sure about this info. I hope you get a different outcome. ds918+.xml
  9. I tried ESXI... but I found it complicate. Let me know if you succeed.
  10. No problem at all. I wish I could assist more...
  11. @mrme01 What kind of hardware do you have?
  12. It's really weird, I am out of ideas. I mean Unraid and OpenSuse use the Qemu/KVM I do not see any reason for them to have any difference. I wish I had a spare PC to test it somehow...
  13. So, seeing that image your are good. It means the loader is loading fine. I do not think you need to change anything there, no need to put it to USB I believe. As you said you need to find a way to make the network to work.
  14. But if you see this screen it means that your Synology is booting successfully. Your issue is the network card most probably.
  15. This is the GUI version of the unraid. The primary vdisk bus is set as USB and the USB Controller I put it as 3.0 (qemu XHCI). The other disks you must set them as SATA since again I think Synology cannot recognize them otherwise.